Page summary

Summary

Metric	Value
Page metrics
Performance Score	78
Total Page Transfer Size	2.3 MB
Requests	44
Timing metrics
TTFB [median]	235 ms
First Paint [median]	402 ms
Fully Loaded [median]	1.071 s
Google Web Vitals
TTFB [median]	235 ms
First Contentful Paint (FCP) [median]	402 ms
Largest Contentful Paint (LCP) [median]	689 ms
Cumulative Layout Shift (CLS) [median]	0.00
Total Blocking Time [median]	136 ms
Max Potential FID [median]	120 ms
CPU metrics
CPU long tasks [median]	4
CPU longest task duration	143 ms
CPU last long task happens at	836 ms
Visual Metrics
First Visual Change [median]	434 ms
Speed Index [median]	607 ms
Visual Complete 85% [median]	700 ms
Visual Complete 99% [median]	800 ms
Last Visual Change [median]	800 ms

Timings Summary

Waterfall

Run 2 SpeedIndex median

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.4 sCPU Long Task duration 54 ms

0.5 sFirst Contentful Paint 402 msFirst Visual Change 434 msLayout Shift 0.00076 470 msCPU Long Task duration 143 ms

0.7 sCPU Long Task duration 60 ms

0.8 sLayout Shift 0.00021 741 msCPU Long Task duration 68 msLCP <IMG> 764 msLast Visual Change 800 msVisual Complete 85% 800 msVisual Complete 95% 800 msVisual Complete 99% 800 msLargest Image 800 msHeading 800 ms

0.9 sCPU Long Task duration 76 ms

Coach

The coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices. Tested using Coach-core version 8.1.1.

Coach score

• Total score 82
• Performance score 78
• Privacy score 88
• Best practice score 86

Performance advice (78)

Show/hide details

Title	Advice	Score
Avoid slowing down the critical rendering path (avoidRenderBlocking)	The page has 10 blocking requests and 3 in body parser blocking (4 JavaScript and 9 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR	59
Description: The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS for really fast rendering and a short rendering path.
Offenders: https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js https://www.proantic.com/js/sweetalert2.js https://cdn.jsdelivr.net/npm/promise-polyfill@8/dist/polyfill.min.js
Don't scale images in the browser (avoidScalingImages)	The page has 5 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them.	50
Description: It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one.
Offenders: https://www.proantic.com/galerie/100-exceptions/3464-664a63d1d138a.jpg https://www.proantic.com/galerie/16-bis-antique/3165-647e33c56f985.jpg https://www.proantic.com/galerie/18-antiquites/2865-6634ddeb278d9.jpg https://www.proantic.com/galerie/1900/3918-68fb92f0ed1ba.jpg https://www.proantic.com/galerie/1900-by-sp/2829-623c18b8bdac7.jpg
Avoid using Google Tag Manager. (googleTagManager)	The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page.	0
Description: Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance.
Inline CSS for faster first render (inlineCss)	The page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens.	95
Description: In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded.
Have a fast largest contentful paint (largestContentfulPaint)	You can add fetchPriority="high" to the image to increase the load priority in Chrome. The image is lazy loaded using the lazy attribute, you should avoid that on the LCP image.	75
Description: Largest contentful paint is one of Google Web Vitals and reports the render time of the largest image or text block visible within the viewport, relative to when the page first started loading. To be fast according to Google, it needs to render before 2.5 seconds and results over 4 seconds is poor performance.
Avoid CPU Long Tasks (longTasks)	The page has 4 CPU long tasks with the total of 336 ms. The total blocking time is 136 ms . However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks.	20
Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler.
Offenders: self self self self
Avoid Frontend single point of failures (spof)	The page has 2 requests inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head.	90
Description: A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag.
Offenders: https://www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+fr.css https://www.google.com/cse/static/style/look/v6/minimalist.css
Avoid extra requests by setting cache headers (cacheHeaders)	The page has 1 request that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 4.3 kB the next access.	90
Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request.
Offenders: https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa
Long cache headers is good (cacheHeadersLong)	The page has 3 requests that have a shorter cache time than 30 days (but still a cache time).	97
Description: Setting a cache header is good. Setting a long cache header (at least 30 days) is even better beacause then it will stay long in the browser cache. But what do you do if that asset change? Rename it and the browser will pick up the new version.
Offenders: https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR https://cdn.jsdelivr.net/npm/promise-polyfill@8/dist/polyfill.min.js https://www.google.com/cse/static/style/look/v6/minimalist.css
Always compress text content (compressAssets)	The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.	90
Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.
Offenders: URL Transfer size Content size https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR 148.5 KB 429.7 KB
Avoid too many fonts (fewFonts)	The page has 10 font requests. Do you really need them? What value does the fonts give the user?	0
Description: How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive.
Offenders: https://www.proantic.com/webfonts/lato-v24-latin-regular.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-regular.woff2 https://www.proantic.com/webfonts/fa-thin-100.woff2 https://www.proantic.com/webfonts/lato-v24-latin-300.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-700.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-600.woff2 https://www.proantic.com/fonts/FontAwesome.otf https://www.proantic.com/webfonts/cinzel-v23-latin-regular.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-300.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-italic.woff2
Total image size shouldn't be too big (imageSize)	The page total image size is 1.2 MB. It's really big. Is the page using the right format for the images? Can they be lazy loaded? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/.	50
Description: Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user.
Total JavaScript size shouldn't be too big (javascriptSize)	The total JavaScript transfer size is 364.5 kB and the uncompressed size is 1.2 MB. This is totally crazy! There is really room for improvement here.	0
Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?
Offenders: URL Transfer size Content size https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js 30.9 KB 87.4 KB https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js 56.5 KB 247.7 KB https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR 148.5 KB 429.7 KB https://www.proantic.com/js/sweetalert2.js 15.0 KB 47.2 KB https://cdn.jsdelivr.net/npm/promise-polyfill@8/dist/polyfill.min.js 2.1 KB 4.3 KB https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa 4.2 KB 9.1 KB https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__fr.js?usqp=CAM%3D 98.6 KB 311.9 KB
Make each CSS response small (optimalCssSize)	https://www.proantic.com/css/A.fontawesome.min.css,,qtimestampcssproantic202602261142+regular.min.css,,qtimestampcssproantic202602261142,Mcc.wyifselPA4.css.pagespeed.cf.3EmdiLN2Bl.css size is 35.8 kB (35813) and that is bigger than the limit of 14.5 kB. https://www.proantic.com/css/A.main.css,qtimestampcssproantic2026022611421111222111111111111.pagespeed.cf.2QfeH0fI3J.css size is 15.4 kB (15393) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB.	80
Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier.
Offenders: URL Transfer size Content size https://www.proantic.com/css/A.fontawesome.min.css,,qtimestampcssproantic2026022...cf.3EmdiLN2Bl.css 35.0 KB 134.5 KB https://www.proantic.com/css/A.main.css,qtimestampcssproantic2026022611421111222...cf.2QfeH0fI3J.css 15.0 KB 84.3 KB
Total page size shouldn't be too big (pageSize)	The page total transfer size is 2.4 MB, which is more than the coach limit of 2 MB. That is really big and you need to make it smaller.	0
Description: Avoid having pages that have a transfer size over the wire of more than 2 MB (desktop) and 1 MB (mobile) because that is really big and will hurt performance and will make the page expensive for the user if she/he pays for the bandwidth.
Offenders: URL Transfer size Content size https://www.proantic.com/antiquaires.php 111.4 KB 1.1 MB https://www.proantic.com/css/A.googlefonts.css,,qtimestampcssproantic20260226114...cf.rEwHvHvTPS.css 1.9 KB 10.6 KB https://www.proantic.com/css/A.sweetalert2-v1-2.css,qtimestampcssproantic2026022...cf.cNqGP1Hykr.css 4.8 KB 27.0 KB https://www.proantic.com/css/A.carrousel-09.css,qtimestampcssproantic20260226114...cf.dnBqBpe3V7.css 1.9 KB 5.3 KB https://www.proantic.com/css/A.fontawesome.min.css,,qtimestampcssproantic2026022...cf.3EmdiLN2Bl.css 35.0 KB 134.5 KB https://www.proantic.com/css/A.thin.min.css,,qtimestampcssproantic202602261142+s...cf.n_K6ZlZCwr.css 587 B 799 B https://www.proantic.com/css/A.light.min.css,,qtimestampcssproantic202602261142+...cf.jkAuv2ZTBd.css 738 B 1.5 KB https://www.proantic.com/css/A.sharp-duotone-thin.min.css,,qtimestampcssproantic...cf.HyjkBCeIdY.css 745 B 1.7 KB https://www.proantic.com/css/A.proantic.webflow.024.css,qtimestampcssproantic202...cf.6WZHjCK3Jc.css 8.8 KB 39.2 KB https://www.proantic.com/css/A.main.css,qtimestampcssproantic2026022611421111222...cf.2QfeH0fI3J.css 15.0 KB 84.3 KB https://www.proantic.com/ico/logo_proantic_2024.png 11.9 KB 11.6 KB https://www.proantic.com/ico/englishflag.png 1.5 KB 1.1 KB https://www.proantic.com/ico/33flag20px.jpg 1.2 KB 869 B https://www.proantic.com/ico/44flag20px.png 2.8 KB 2.5 KB https://www.proantic.com/ico/39flag20px.jpg 1.2 KB 899 B https://www.proantic.com/webfonts/lato-v24-latin-regular.woff2 23.3 KB 23.0 KB https://www.proantic.com/webfonts/open-sans-v40-latin-regular.woff2 18.5 KB 18.2 KB https://www.proantic.com/webfonts/fa-thin-100.woff2 378.5 KB 377.8 KB https://www.proantic.com/webfonts/lato-v24-latin-300.woff2 23.0 KB 22.7 KB https://www.proantic.com/webfonts/open-sans-v40-latin-700.woff2 18.1 KB 17.8 KB https://www.proantic.com/webfonts/open-sans-v40-latin-600.woff2 18.5 KB 18.2 KB https://www.proantic.com/fonts/FontAwesome.otf 107.5 KB 107.1 KB https://www.proantic.com/ico/facebook_sm.png 10.4 KB 10.1 KB https://www.proantic.com/ico/INSTAGRAM-LOGO-SM.png 67.8 KB 67.4 KB https://www.proantic.com/ico/logo_proantic4a_sm_33.png 41.1 KB 40.8 KB https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js 30.9 KB 87.4 KB https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js 56.5 KB 247.7 KB https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR 148.5 KB 429.7 KB https://www.proantic.com/js/sweetalert2.js 15.0 KB 47.2 KB https://cdn.jsdelivr.net/npm/promise-polyfill@8/dist/polyfill.min.js 2.1 KB 4.3 KB https://www.proantic.com/galerie/100-exceptions/3464-664a63d1d138a.jpg 53.6 KB 53.3 KB https://www.proantic.com/galerie/16-bis-antique/3165-647e33c56f985.jpg 214.9 KB 214.4 KB https://www.proantic.com/galerie/18-antiquites/2865-6634ddeb278d9.jpg 208.8 KB 208.2 KB https://www.proantic.com/galerie/1900/3918-68fb92f0ed1ba.jpg 262.6 KB 262.0 KB https://www.proantic.com/galerie/1900-by-sp/2829-623c18b8bdac7.jpg 249.8 KB 249.2 KB https://www.proantic.com/webfonts/cinzel-v23-latin-regular.woff2 13.7 KB 13.4 KB https://www.proantic.com/webfonts/open-sans-v40-latin-300.woff2 18.6 KB 18.3 KB https://www.proantic.com/webfonts/open-sans-v40-latin-italic.woff2 19.1 KB 18.8 KB https://www.proantic.com/css/jquery-ui-1_10_3-minify.css 5.0 KB 24.3 KB https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa 4.2 KB 9.1 KB https://www.proantic.com/ico/proantic_ico_32_1.png 3.3 KB 3.0 KB https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__fr.js?usqp=CAM%3D 98.6 KB 311.9 KB https://www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+fr.css 9.7 KB 43.2 KB https://www.google.com/cse/static/style/look/v6/minimalist.css 1.3 KB 6.0 KB
Don't use private headers on static content (privateAssets)	The page has 3 requests with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.	70
Description: If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private.
Offenders: https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__fr.js?usqp=CAM%3D https://www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+fr.css

Best practice advice (86)

Show/hide details

Title	Advice	Score
Meta description (metaDescription)	The meta description is too long. It has 156 characters, the recommended max is 155	50
Description: Use a page description to make the page more relevant to search engines.
Do not send too long headers (longHeaders)	https://www.proantic.com/antiquaires.php has a header content-security-policy that is 2120 characters long.	99
Description: Do not send response headers that are too long.
Offenders: https://www.proantic.com/antiquaires.php
Avoid too many third party requests (thirdParty)	The page do 18% requests to third party domains (8 requests and 360.4 kB). First party is 36 requests and 2 MB. The regex .*proantic.* was used to calculate first/third party requests.	50
Description: Do not load most of your content from third party URLs.
Avoid unnecessary headers (unnecessaryHeaders)	There are 41 responses that sets both a max-age and expires header. There are 44 responses that sets a server header.	15
Description: Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.
Offenders: https://www.proantic.com/antiquaires.php https://www.proantic.com/css/A.googlefonts.css,,qtimestampcssproantic20260226114...cf.rEwHvHvTPS.css https://www.proantic.com/css/A.googlefonts.css,,qtimestampcssproantic20260226114...cf.rEwHvHvTPS.css https://www.proantic.com/css/A.sweetalert2-v1-2.css,qtimestampcssproantic2026022...cf.cNqGP1Hykr.css https://www.proantic.com/css/A.sweetalert2-v1-2.css,qtimestampcssproantic2026022...cf.cNqGP1Hykr.css https://www.proantic.com/css/A.carrousel-09.css,qtimestampcssproantic20260226114...cf.dnBqBpe3V7.css https://www.proantic.com/css/A.carrousel-09.css,qtimestampcssproantic20260226114...cf.dnBqBpe3V7.css https://www.proantic.com/css/A.fontawesome.min.css,,qtimestampcssproantic2026022...cf.3EmdiLN2Bl.css https://www.proantic.com/css/A.fontawesome.min.css,,qtimestampcssproantic2026022...cf.3EmdiLN2Bl.css https://www.proantic.com/css/A.thin.min.css,,qtimestampcssproantic202602261142+s...cf.n_K6ZlZCwr.css https://www.proantic.com/css/A.thin.min.css,,qtimestampcssproantic202602261142+s...cf.n_K6ZlZCwr.css https://www.proantic.com/css/A.light.min.css,,qtimestampcssproantic202602261142+...cf.jkAuv2ZTBd.css https://www.proantic.com/css/A.light.min.css,,qtimestampcssproantic202602261142+...cf.jkAuv2ZTBd.css https://www.proantic.com/css/A.sharp-duotone-thin.min.css,,qtimestampcssproantic...cf.HyjkBCeIdY.css https://www.proantic.com/css/A.sharp-duotone-thin.min.css,,qtimestampcssproantic...cf.HyjkBCeIdY.css https://www.proantic.com/css/A.proantic.webflow.024.css,qtimestampcssproantic202...cf.6WZHjCK3Jc.css https://www.proantic.com/css/A.proantic.webflow.024.css,qtimestampcssproantic202...cf.6WZHjCK3Jc.css https://www.proantic.com/css/A.main.css,qtimestampcssproantic2026022611421111222...cf.2QfeH0fI3J.css https://www.proantic.com/css/A.main.css,qtimestampcssproantic2026022611421111222...cf.2QfeH0fI3J.css https://www.proantic.com/ico/logo_proantic_2024.png https://www.proantic.com/ico/logo_proantic_2024.png https://www.proantic.com/ico/englishflag.png https://www.proantic.com/ico/englishflag.png https://www.proantic.com/ico/33flag20px.jpg https://www.proantic.com/ico/33flag20px.jpg https://www.proantic.com/ico/44flag20px.png https://www.proantic.com/ico/44flag20px.png https://www.proantic.com/ico/39flag20px.jpg https://www.proantic.com/ico/39flag20px.jpg https://www.proantic.com/webfonts/lato-v24-latin-regular.woff2 https://www.proantic.com/webfonts/lato-v24-latin-regular.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-regular.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-regular.woff2 https://www.proantic.com/webfonts/fa-thin-100.woff2 https://www.proantic.com/webfonts/fa-thin-100.woff2 https://www.proantic.com/webfonts/lato-v24-latin-300.woff2 https://www.proantic.com/webfonts/lato-v24-latin-300.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-700.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-700.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-600.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-600.woff2 https://www.proantic.com/fonts/FontAwesome.otf https://www.proantic.com/fonts/FontAwesome.otf https://www.proantic.com/ico/facebook_sm.png https://www.proantic.com/ico/facebook_sm.png https://www.proantic.com/ico/INSTAGRAM-LOGO-SM.png https://www.proantic.com/ico/INSTAGRAM-LOGO-SM.png https://www.proantic.com/ico/logo_proantic4a_sm_33.png https://www.proantic.com/ico/logo_proantic4a_sm_33.png https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR https://www.proantic.com/js/sweetalert2.js https://www.proantic.com/js/sweetalert2.js https://cdn.jsdelivr.net/npm/promise-polyfill@8/dist/polyfill.min.js https://www.proantic.com/galerie/100-exceptions/3464-664a63d1d138a.jpg https://www.proantic.com/galerie/100-exceptions/3464-664a63d1d138a.jpg https://www.proantic.com/galerie/16-bis-antique/3165-647e33c56f985.jpg https://www.proantic.com/galerie/16-bis-antique/3165-647e33c56f985.jpg https://www.proantic.com/galerie/18-antiquites/2865-6634ddeb278d9.jpg https://www.proantic.com/galerie/18-antiquites/2865-6634ddeb278d9.jpg https://www.proantic.com/galerie/1900/3918-68fb92f0ed1ba.jpg https://www.proantic.com/galerie/1900/3918-68fb92f0ed1ba.jpg https://www.proantic.com/galerie/1900-by-sp/2829-623c18b8bdac7.jpg https://www.proantic.com/galerie/1900-by-sp/2829-623c18b8bdac7.jpg https://www.proantic.com/webfonts/cinzel-v23-latin-regular.woff2 https://www.proantic.com/webfonts/cinzel-v23-latin-regular.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-300.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-300.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-italic.woff2 https://www.proantic.com/webfonts/open-sans-v40-latin-italic.woff2 https://www.proantic.com/css/jquery-ui-1_10_3-minify.css https://www.proantic.com/css/jquery-ui-1_10_3-minify.css https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa https://www.proantic.com/ico/proantic_ico_32_1.png https://www.proantic.com/ico/proantic_ico_32_1.png https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__fr.js?usqp=CAM%3D https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__fr.js?usqp=CAM%3D https://www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+fr.css https://www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+fr.css https://www.google.com/cse/static/style/look/v6/minimalist.css https://www.google.com/cse/static/style/look/v6/minimalist.css

Privacy advice (88)

Show/hide details

Title	Advice	Score
Set a referrer-policy header to make sure you do not leak user information. (referrerPolicyHeader)	Set a referrer-policy header to make sure you do not leak user information.	0
Description: Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. https://scotthelme.co.uk/a-new-security-header-referrer-policy/.
Offenders: https://www.proantic.com/antiquaires.php
Do not share user data with third parties. (thirdPartyPrivacy)	The page has 18% requests that are 3rd party (8 requests with a size of 360.4 kB). The page also have request to companies that harvest data from users and do not respect users privacy (see https://en.wikipedia.org/wiki/Surveillance_capitalism). The page do 6 survelliance requests and uses 3 survelliance tools. The page do 1 tag-manager request and uses 1 tag-manager tool. The page do 4 utility requests and uses 1 utility tool.	0
Description: Using third party requests shares user information with that third party. Please avoid that! The project https://github.com/patrickhulce/third-party-web is used to categorize first/third party requests.
Offenders: https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR https://cdn.jsdelivr.net/npm/promise-polyfill@8/dist/polyfill.min.js https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa https://www.google.com/cse/static/element/b33cba5881f68fbf/cse_element__fr.js?usqp=CAM%3D https://www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+fr.css https://www.google.com/cse/static/style/look/v6/minimalist.css

Page info

Page info
Title	Proantic: Tous les Antiquaires
Width	1350
Height	14393
DOM elements	6066
Avg DOM depth	9
Max DOM depth	12
Iframes	0
Script tags	16
Local storage	0 b
Session storage	0 b
Network Information API	4g

Resource Hints
dns-prefetch
https://cdn-images.mailchimp.com/
preconnect
https://cdn-images.mailchimp.com/

Technologies used to build the page.

Data collected using Wappalyzer version 6.10.66. With updated code from Webappanalyzer 2024-12-27. Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyzer find more information about technologies used.

Technology	Confidence	Category
HSTS	100	Security
Google PageSpeed 1.13.35.2	100	Caching Web server extensions Performance
Cloudflare	100	CDN
HTTP/3	100	Miscellaneous

Data collected using Third Party Web 0.26.2

Cdn
Google CDN
Cloudflare CDN
JSDelivr CDN
Survelliance
Google CDN
Google Tag Manager
Other Google APIs/SDKs
Tag-manager
Google Tag Manager
Utility
Other Google APIs/SDKs

Data from run 2

Visual Metrics

Browser Metrics

Largest Contentful Paint

When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.

Element type	IMG
Element/tag	<img loading="lazy" src="https://www.proantic.com/galerie/100-exceptions/3464-664a63d1d138a.jpg" alt="100 Exceptions">
Render time	764 ms
Element render delay	72 ms
TTFB	235 ms
Resource delay	442 ms
Resource load duration	16 ms
Elements that needed recalculate style before LCP	1592
Time spent in recalculate style before LCP	51.821 ms
Load time	724 ms
URL	https://www.proantic...664a63d1d138a.jpg
Size (width*height)	34848
DOM path
main#section-nouveautes > div#section-nouveautes > section#minheight > div#login_ajax_after1 > a:eq(0) > div:eq(1) > img> main#section-nouveautes > div#section-nouveautes > section#minheight > div#login_ajax_after1 > a:eq(0) > div:eq(1) > img>

The largest contentful paint is highlighted in the image. If no element is highlighted the element was removed before the screenshot or the LCP API couldn't find the element.

The Largest Contentful Paint API highlighted this image as a part of the LCP.

Detected Cumulative Layout Shift

0.00097 cumulative layout shift collected from the Cumulative Layout Shift API.

These HTML elements contribute most to the Cumulative Layout Shifts of the page. The higher score, the more layout shift.

Score	HTML Element
0.00076	<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta"></div>,<div class="nav-nouveau-curr-flag navbar-big-screen"></div>,<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" data-menu="antiquaire"></div>,<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta"></div>,<div class="w-dropdown-nav magazine nav-menu-hover nav-menu-hover-meta"></div>
body > nav#totop > div > div > nav > div:eq(6),body > nav#totop > div > div > div:eq(0) > div:eq(3),body > nav#totop > div > div > nav > div:eq(7),body > nav#totop > div > div > nav > div:eq(3),body > nav#totop > div > div > nav > div:eq(8)
0.00021	,
body > main#section-nouveautes > div#section-nouveautes > section#minheight > div:eq(0) > h1 > #text,body > main#section-nouveautes > div#section-nouveautes > section#minheight > div:eq(0) > div > #text

The elements that have shifted place is highlighted in the image (that have a higher value than 0.01). If the element shifted outside of the viewport, you will not see it there. It can be hard to understand what content that has shifted, if that's the case, checkout the video or the filmstrip of the run.

Long Animation Frames

Read more about the Long Animation Frames API here here.

The top 10 longest animation frames entries

Server timings

There are no Server Timings.

Custom metrics collected through JavaScript

There are no custom configured scripts.

Extra metrics collected using scripting

There are no custom extra metrics from scripting.

Visual Elements

PageXray

How the page is built.

Largest assets on the page (by transfer size)

Requests and sizes per content type

Data per domain

Expires and last modified statistics

Requests loaded after onLoad event

Included requests done after load event end.

Requests loaded after onContentLoad

Includes requests done after DOM content loaded.

Render blocking requests

Render blocking information directly from Chrome.

Render information

CPU

Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.

Long Tasks

Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.

CPU last long task happened at 836 ms

Individual Long Tasks

CPU time spent

Calculated using Tracium.

Time spent per request

CPU time spent

Third party

Third party requests categorised by Third party web version 0.26.2.

Third party requests and tools

First party requests and sizes per content type

Calculated using .*proantic.* (use --firstParty to configure).

Third party requests and sizes per content type

Axe

Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Tested using axe-core version 4.10.2. Read more about axe-core .

Violations

Median number of violations for all the runs. Check each individual run to see all the violations.