Page summary

https://www.proantic.com/antiquaires.php

Tested 2025-03-10 02:32:27 using Chrome 132.0.6834.83 (runtime settings).

SummaryWaterfall MetricsVideoFilmstrip CoachPageXrayCPU Third party axe
| Summary | | Download Video | Download Timeline Log | Download HAR | 

Summary

MetricValue
Page metrics
Performance Score79
Total Page Transfer Size2.2 MB
Requests41
Timing metrics
TTFB [median]226 ms
First Paint [median]339 ms
Fully Loaded [median]1.153 s
Google Web Vitals
TTFB [median]226 ms
First Contentful Paint (FCP) [median]339 ms
Largest Contentful Paint (LCP) [median]778 ms
Cumulative Layout Shift (CLS) [median]0.01
Interaction To Next Paint (INP) [median]128 ms
Total Blocking Time [median]198 ms
Max Potential FID [median]164 ms
CPU metrics
CPU long tasks [median]3
CPU longest task duration169 ms
CPU last long task happens at940 ms
Visual Metrics
First Visual Change [median]335 ms
Speed Index [median]404 ms
Visual Complete 85% [median]401 ms
Visual Complete 99% [median]900 ms
Last Visual Change [median]900 ms
Screenshot of run 2

Timings Summary

Metricminmedianmeanmax
Visual Metrics
FirstVisualChange334 ms335 ms390 ms500 ms
LastVisualChange836 ms900 ms934 ms1.067 s
SpeedIndex401 ms404 ms459 ms571 ms
LargestImage334 ms335 ms390 ms500 ms
Heading836 ms900 ms934 ms1.067 s
LargestContentfulPaint836 ms900 ms934 ms1.067 s
LastMeaningfulPaint836 ms900 ms934 ms1.067 s
VisualReadiness501 ms566 ms545 ms567 ms
VisualComplete85367 ms401 ms445 ms567 ms
VisualComplete95769 ms800 ms845 ms967 ms
VisualComplete99836 ms900 ms934 ms1.067 s
Google Web Vitals
Time To First Byte (TTFB)191 ms226 ms280 ms423 ms
Largest Contentful Paint (LCP)772 ms778 ms836 ms958 ms
First Contentful Paint (FCP)319 ms339 ms393 ms521 ms
Cumulative Layout Shift (CLS)0.00140.00750.00550.0075
More metrics
firstPaint319 ms339 ms393 ms521 ms
loadEventEnd1.026 s1.064 s1.093 s1.188 s
CPU
Total Blocking Time186 ms198 ms197 ms206 ms
Max Potential FID151 ms164 ms161 ms169 ms
CPU long tasks 3334
CPU last long task happens at928 ms940 ms988 ms1.096 s
| Waterfall | | Download HAR | 

Waterfall

Run 2 SpeedIndex median

| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
0.4 sFirst Contentful Paint 319 msFirst Visual Change 334 msLargest Image 334 msLayout Shift 0.00609 343 msVisual Complete 85% 367 ms
0.5 sLayout Shift 0.00081 412 msLayout Shift 0.00001 457 ms
0.6 sCPU Long Task duration 164 ms
0.7 sCPU Long Task duration 90 ms
0.8 sLCP <H1> 778 msVisual Complete 95% 800 ms
0.9 sLayout Shift 0.00062 856 msLast Visual Change 900 msVisual Complete 99% 900 msHeading 900 ms
1 sCPU Long Task duration 102 ms
| Performance advice | Best practice advice | Privacy advice | Page info | Technologies | 

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.

I am the coach

Coach score

Performance advice (79)

TitleAdviceScore
Avoid slowing down the critical rendering path (avoidRenderBlocking)The page has 4 blocking requests and 3 in body parser blocking (4 JavaScript and 3 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-YP51KSLLWR59
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 4 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.60
    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-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.
    Avoid CPU Long Tasks (longTasks)The page has 3 CPU long tasks with the total of 348 ms. The total blocking time is 198 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.40
    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
  • 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/5c8d58cbdc1332a7/default+fr.css
  • https://www.google.com/cse/static/style/look/v4/minimalist.css
  • Avoid extra requests by setting cache headers (cacheHeaders)The page has 2 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 5.3 kB the next access.80
    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://cdn-images.mailchimp.com/embedcode/horizontal-slim-10_7.css
  • https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa
  • Long cache headers is good (cacheHeadersLong)The page has 23 requests that have a shorter cache time than 30 days (but still a cache time).77
    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.proantic.com/css/A.googlefonts.css,,qtimestampcssproantic+normalize_...cf.argL22mL8H.css
  • https://www.proantic.com/css/A.sweetalert2-v1-2.css+carrousel-09.css+fontawesome...cf.pOHLdeuq91.css
  • https://www.proantic.com/css/A.proantic.webflow.024.css,qtimestampcssproantic.pa...cf.nyRFwobMv8.css
  • https://www.proantic.com/ico/logo_proantic_2024.png
  • https://www.proantic.com/ico/englishflag.png
  • https://www.proantic.com/ico/33flag20px.jpg
  • https://www.proantic.com/ico/44flag20px.png
  • https://www.proantic.com/ico/39flag20px.jpg
  • https://www.proantic.com/ico/line.png
  • https://www.proantic.com/ico/facebook_sm.png
  • https://www.proantic.com/ico/pinterest_sm.png
  • https://www.proantic.com/ico/INSTAGRAM-LOGO-SM.png
  • https://www.proantic.com/ico/logo_proantic4a_sm_33.png
  • https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR
  • 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/16-bis-antique/3165-647e33c56f985.jpg
  • https://www.proantic.com/galerie/18-antiquites/2865-6634ddeb278d9.jpg
  • https://www.proantic.com/galerie/1900-by-sp/2829-623c18b8bdac7.jpg
  • https://www.proantic.com/css/jquery-ui-1_10_3-minify.css
  • https://www.google.com/cse/static/style/look/v4/minimalist.css
  • https://www.proantic.com/ico/proantic_ico_new_6.png
  • Avoid too many fonts (fewFonts)The page has 11 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-700.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-regular.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-600.woff2
  • https://www.proantic.com/webfonts/open-sans-v40-latin-500.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 988.2 kB. 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 324.9 kB and the uncompressed size is 1 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:
    URLTransfer sizeContent size
    https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js 30.9 KB87.4 KB
    https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js 56.5 KB247.7 KB
    https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR 112.8 KB329.2 KB
    https://www.proantic.com/js/sweetalert2.js 15.0 KB47.2 KB
    https://cdn.jsdelivr.net/npm/promise-polyfill@8/dist/polyfill.min.js 2.3 KB4.3 KB
    https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa 4.0 KB8.9 KB
    https://www.google.com/cse/static/element/5c8d58cbdc1332a7/cse_element__fr.js?usqp=CAI%3D 95.8 KB291.4 KB
    Make each CSS response small (optimalCssSize)https://www.proantic.com/css/A.sweetalert2-v1-2.css+carrousel-09.css+fontawesome.min.css+regular.min.css+thin.min.css+sharp-solid.min.css+light.min.css,Mcc.oKPVERJshr.css.pagespeed.cf.pOHLdeuq91.css size is 39.6 kB (39568) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB.90
    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:
    URLTransfer sizeContent size
    https://www.proantic.com/css/A.sweetalert2-v1-2.css+carrousel-09.css+fontawesome...cf.pOHLdeuq91.css 38.6 KB204.6 KB
    Total page size shouldn't be too big (pageSize)The page total transfer size is 2.3 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:
    URLTransfer sizeContent size
    https://www.proantic.com/antiquaires.php 117.0 KB892.3 KB
    https://www.proantic.com/css/A.googlefonts.css,,qtimestampcssproantic+normalize_...cf.argL22mL8H.css 9.3 KB41.4 KB
    https://www.proantic.com/css/A.sweetalert2-v1-2.css+carrousel-09.css+fontawesome...cf.pOHLdeuq91.css 38.6 KB204.6 KB
    https://www.proantic.com/css/A.proantic.webflow.024.css,qtimestampcssproantic.pa...cf.nyRFwobMv8.css 13.6 KB64.3 KB
    https://www.proantic.com/ico/logo_proantic_2024.png 11.9 KB11.6 KB
    https://www.proantic.com/ico/englishflag.png 1.5 KB1.1 KB
    https://www.proantic.com/ico/33flag20px.jpg 1.2 KB869 B
    https://www.proantic.com/ico/44flag20px.png 2.8 KB2.5 KB
    https://www.proantic.com/ico/39flag20px.jpg 1.2 KB899 B
    https://www.proantic.com/ico/line.png 536 B218 B
    https://www.proantic.com/webfonts/lato-v24-latin-regular.woff2 23.4 KB23.0 KB
    https://www.proantic.com/webfonts/open-sans-v40-latin-700.woff2 18.2 KB17.8 KB
    https://www.proantic.com/webfonts/fa-thin-100.woff2 491.6 KB490.8 KB
    https://www.proantic.com/webfonts/lato-v24-latin-300.woff2 23.0 KB22.7 KB
    https://www.proantic.com/webfonts/open-sans-v40-latin-regular.woff2 18.6 KB18.2 KB
    https://www.proantic.com/fonts/FontAwesome.otf 107.5 KB107.1 KB
    https://www.proantic.com/ico/facebook_sm.png 10.4 KB10.1 KB
    https://www.proantic.com/ico/pinterest_sm.png 16.8 KB16.4 KB
    https://www.proantic.com/ico/INSTAGRAM-LOGO-SM.png 67.8 KB67.4 KB
    https://www.proantic.com/ico/logo_proantic4a_sm_33.png 41.1 KB40.8 KB
    https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js 30.9 KB87.4 KB
    https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js 56.5 KB247.7 KB
    https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR 112.8 KB329.2 KB
    https://www.proantic.com/js/sweetalert2.js 15.0 KB47.2 KB
    https://cdn.jsdelivr.net/npm/promise-polyfill@8/dist/polyfill.min.js 2.3 KB4.3 KB
    https://www.proantic.com/galerie/100-exceptions/3464-664a63d1d138a.jpg 53.6 KB53.3 KB
    https://www.proantic.com/galerie/16-bis-antique/3165-647e33c56f985.jpg 214.9 KB214.4 KB
    https://www.proantic.com/galerie/18-antiquites/2865-6634ddeb278d9.jpg 208.8 KB208.2 KB
    https://www.proantic.com/galerie/1900-by-sp/2829-623c18b8bdac7.jpg 249.8 KB249.2 KB
    https://www.proantic.com/webfonts/cinzel-v23-latin-regular.woff2 13.7 KB13.4 KB
    https://www.proantic.com/webfonts/open-sans-v40-latin-300.woff2 18.6 KB18.3 KB
    https://www.proantic.com/webfonts/open-sans-v40-latin-600.woff2 18.5 KB18.2 KB
    https://www.proantic.com/webfonts/open-sans-v40-latin-500.woff2 18.6 KB18.3 KB
    https://www.proantic.com/webfonts/open-sans-v40-latin-italic.woff2 19.2 KB18.8 KB
    https://www.proantic.com/css/jquery-ui-1_10_3-minify.css 4.9 KB24.3 KB
    https://cdn-images.mailchimp.com/embedcode/horizontal-slim-10_7.css 1.2 KB2.0 KB
    https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa 4.0 KB8.9 KB
    https://www.google.com/cse/static/element/5c8d58cbdc1332a7/cse_element__fr.js?usqp=CAI%3D 95.8 KB291.4 KB
    https://www.google.com/cse/static/element/5c8d58cbdc1332a7/default+fr.css 8.9 KB40.7 KB
    https://www.google.com/cse/static/style/look/v4/minimalist.css 1.4 KB5.0 KB
    https://www.proantic.com/ico/proantic_ico_new_6.png 88.5 KB88.1 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/5c8d58cbdc1332a7/cse_element__fr.js?usqp=CAI%3D
  • https://www.google.com/cse/static/element/5c8d58cbdc1332a7/default+fr.css
  • Best practice advice (86)

    TitleAdviceScore
    Meta description (metaDescription)The meta description is too long. It has 156 characters, the recommended max is 15550
    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 1861 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 22% requests to third party domains (9 requests and 321.4 kB). First party is 32 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 37 responses that sets both a max-age and expires header. There are 41 responses that sets a server header. 22
    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,,qtimestampcssproantic+normalize_...cf.argL22mL8H.css
  • https://www.proantic.com/css/A.googlefonts.css,,qtimestampcssproantic+normalize_...cf.argL22mL8H.css
  • https://www.proantic.com/css/A.sweetalert2-v1-2.css+carrousel-09.css+fontawesome...cf.pOHLdeuq91.css
  • https://www.proantic.com/css/A.sweetalert2-v1-2.css+carrousel-09.css+fontawesome...cf.pOHLdeuq91.css
  • https://www.proantic.com/css/A.proantic.webflow.024.css,qtimestampcssproantic.pa...cf.nyRFwobMv8.css
  • https://www.proantic.com/css/A.proantic.webflow.024.css,qtimestampcssproantic.pa...cf.nyRFwobMv8.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/ico/line.png
  • https://www.proantic.com/ico/line.png
  • 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-700.woff2
  • https://www.proantic.com/webfonts/open-sans-v40-latin-700.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-regular.woff2
  • https://www.proantic.com/webfonts/open-sans-v40-latin-regular.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/pinterest_sm.png
  • https://www.proantic.com/ico/pinterest_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-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-600.woff2
  • https://www.proantic.com/webfonts/open-sans-v40-latin-600.woff2
  • https://www.proantic.com/webfonts/open-sans-v40-latin-500.woff2
  • https://www.proantic.com/webfonts/open-sans-v40-latin-500.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://cdn-images.mailchimp.com/embedcode/horizontal-slim-10_7.css
  • https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa
  • https://www.google.com/cse/static/element/5c8d58cbdc1332a7/cse_element__fr.js?usqp=CAI%3D
  • https://www.google.com/cse/static/element/5c8d58cbdc1332a7/cse_element__fr.js?usqp=CAI%3D
  • https://www.google.com/cse/static/element/5c8d58cbdc1332a7/default+fr.css
  • https://www.google.com/cse/static/element/5c8d58cbdc1332a7/default+fr.css
  • https://www.google.com/cse/static/style/look/v4/minimalist.css
  • https://www.google.com/cse/static/style/look/v4/minimalist.css
  • https://www.proantic.com/ico/proantic_ico_new_6.png
  • https://www.proantic.com/ico/proantic_ico_new_6.png
  • Privacy advice (88)

    TitleAdviceScore
    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 22% requests that are 3rd party (9 requests with a size of 321.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 1 marketing request and uses 1 marketing 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://cdn-images.mailchimp.com/embedcode/horizontal-slim-10_7.css
  • https://cse.google.com/cse/cse.js?cx=000444099054209463199:hh5kqqsn4oa
  • https://www.google.com/cse/static/element/5c8d58cbdc1332a7/cse_element__fr.js?usqp=CAI%3D
  • https://www.google.com/cse/static/element/5c8d58cbdc1332a7/default+fr.css
  • https://www.google.com/cse/static/style/look/v4/minimalist.css
  • Page info

    Page info
    TitleProantic: Tous les Antiquaires de Proantic
    Width1350
    Height14598
    DOM elements6996
    Avg DOM depth8
    Max DOM depth12
    Iframes0
    Script tags15
    Local storage0 b
    Session storage0 b
    Network Information API4g
    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.

    TechnologyConfidenceCategory
    Nginx 100  Web servers Reverse proxies
    Amazon Web Services 100  PaaS
    HSTS 100  Security
    Google PageSpeed 1.13.35.2100  Caching Web server extensions Performance
    Cloudflare 100  CDN
    Amazon CloudFront 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
    Marketing
    Mailchimp
    Utility
    Other Google APIs/SDKs
    | Browser metrics | Visual Metrics | Largest Contentful Paint | Cumulative Layout Shift | Interaction To Next Paint | Long Aninimation Frames | Visual Elements | 

    Data from run 2

    Visual Metrics

    Browser Metrics

    Google Web Vitals
    Time to first byte (TTFB)191 ms
    First Contentful Paint (FCP)319 ms
    Largest Contentful Paint (LCP)778 ms
    Cumulative Layout Shift (CLS)0.01
    Interaction to next paint (INP)112 ms
    Total Blocking Time (TBT)206 ms
    First Contentful Paint info
    Elements that needed recalculate style before FCP225
    Time spent in recalculate style before FCP33.512 ms
    Extra timings
    TTFB191 ms
    First Paint319 ms
    Load Event End1.064 s
    Fully loaded1.153 s

    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 typeH1
    Element/tag<h1></h1>
    Render time 778 ms
    Element render delay587 ms
    TTFB191 ms
    Resource delay0 ms
    Resource load duration0 ms
    Elements that needed recalculate style before LCP4147
    Time spent in recalculate style before LCP95.664 ms
    Load time0 ms
    Size (width*height)33528
    DOM path
    div#section-nouveautes > div:eq(1) > h1> div#section-nouveautes > div:eq(1) > h1>
    LCP

    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.

    Detected Cumulative Layout Shift

    0.00753 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.

    ScoreHTML Element
    0.00609<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" onclick=""></div>,<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" onclick=""></div>,<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" onclick=""></div>,<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" onclick=""></div>,<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" onclick=""></div>
    body > div#totop > div > div#new-menu-top > nav > div:eq(1),body > div#totop > div > div#new-menu-top > nav > div:eq(6),body > div#totop > div > div#new-menu-top > nav > div:eq(3),body > div#totop > div > div#new-menu-top > nav > div:eq(4),body > div#totop > div > div#new-menu-top > nav > div:eq(5)
    0.00081<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" onclick=""></div>,<div class="nouveau-curr-flag flex 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" onclick=""></div>,<div class="w-dropdown-nav magazine nav-menu-hover nav-menu-hover-meta"></div>
    body > div#totop > div > div#new-menu-top > nav > div:eq(6),body > div#totop > div > div#new-menu-top > div:eq(0) > div:eq(3),body > div#totop > div > div#new-menu-top > nav > div:eq(7),body > div#totop > div > div#new-menu-top > nav > div:eq(3),body > div#totop > div > div#new-menu-top > nav > div:eq(8)
    0.00062,,
    body > div#section-nouveautes > div:eq(1) > div:eq(0) > #text,body > div#section-nouveautes > div:eq(1) > h1 > #text,body > div#section-nouveautes > div:eq(1) > div:eq(4) > div:eq(1) > h2 > a > #text
    0.00001<button type="submit" style="border: none;background: none" aria-label="Que recherchez-vous ?"></button>
    body > div#totop > div > div#new-menu-top > div:eq(0) > div:eq(2) > form > button
    Layout shift

    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.

    Interaction to Next Paint

    Interaction to Next Paint (INP) is a metric that try to measure responsiveness. It's useful if you are testing user journeys. Read more about Interaction to Next Paint.

    The measured latency was 112 ms.

    Event typemouseout
    Element typeBODY
    Element class namebody-nouv
    Event targethtml>body.body-nouv
    Load state when the event happenedloading

    Long Animation Frames

    Read more about the Long Animation Frames API here here.

    The top 10 longest animation frames entries

    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    202 ms164.3 ms88.7 ms81.9 ms6.8 ms
    https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js

    Invoker:  https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js
    Invoker Type: classic-script
    Window attribution: self

    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    58 ms102.6 ms5.4 ms4.3 ms1.1 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    0 ms75.3 ms32.7 ms1.6 ms31.1 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    0 ms17.9 ms40.1 ms19.8 ms20.3 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    0 ms58.9 ms2.1 ms1.7 ms0.4 ms
    https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR

    Invoker:  https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR
    Invoker Type: classic-script
    Window attribution: self

    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

    NameDisplay TimeX YWidthHeight
    LargestImage (logo_proantic_2024.png)334 ms 75 15 69 69
    <img alt="logo-proantic" src="https://www.proantic.com/ico/logo_proantic_2024.png" style="width: 69px;height: 100%;margin-right: 10px;">
    Heading900 ms 300 275 1050 44
    <h1></h1>
    LargestContentfulPaint900 ms 300 275 1050 44
    <h1></h1>
    | Summary  | Largest responses  | Requests and sizes per content type  | Data per domain | Expires and last modified statistics  | Requests loaded after onLoad event  | Render blocking requests  | 

    PageXray

    How the page is built.

    Summary
    HTTP versionHTTP/2.0
    Total requests41
    Total domains8
    Total transfer size2.2 MB
    Total content size3.9 MB
    Responses missing compression15
    Number of cookies0
    Third party cookies0
    Requests per response code
    20041

    Largest assets on the page (by transfer size)

    Requests and sizes per content type

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b117.0 KB892.3 KB1
    css0 b77.9 KB382.2 KB7
    javascript0 b317.3 KB1016.1 KB7
    image0 b970.8 KB965.1 KB15
    font0 b770.8 KB766.6 KB11
    Total0 b2.2 MB3.9 MB41

    Data per domain

    DomainTotal download timeTransfer SizeContent SizeRequests
    www.proantic.com1.382 s1.9 MB2.9 MB32
    ajax.googleapis.com40 ms30.9 KB87.4 KB1
    cdnjs.cloudflare.com57 ms56.5 KB247.7 KB1
    www.googletagmanager.com64 ms112.8 KB329.2 KB1
    cdn.jsdelivr.net50 ms2.3 KB4.3 KB1
    cdn-images.mailchimp.com10 ms1.2 KB2.0 KB1
    cse.google.com49 ms4.0 KB8.9 KB1
    www.google.com75 ms106.2 KB337.1 KB3

    Expires and last modified statistics

    typeminmedianmax
    Expires0 seconds1 week1 year
    Last modified3 weeks30 weeks15 years

    Requests loaded after onLoad event

    Included requests done after load event end.

    ContentTransfer SizeRequests
    html0 b0
    css10.3 KB2
    javascript95.8 KB1
    image88.5 KB1
    font0 b0
    Total194.6 KB4

    Requests loaded after onContentLoad

    Includes requests done after DOM content loaded.

    ContentTransfer SizeRequests
    html0 b0
    css10.3 KB2
    javascript99.8 KB2
    image88.5 KB1
    font0 b0
    Total198.6 KB5

    Render blocking requests

    Render blocking information directly from Chrome.

    BlockingIn body parser blockingPotentially blocking
    431

    Render information

    CPU Long Tasks | CPU Time Spent | CPU Time Spent Per Request | CPU Time Per Tool/Domain | 

    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.

    TypeQuantityTotal duration (ms)
    Total Blocking Time 206
    Max Potential First Input Delay 164
    Long Tasks before First Paint00
    Long Tasks before First Contentful Paint00
    Long Tasks before Largest Contentful Paint2254
    Long Tasks after Load Event End00
    Total Long Tasks3356

    CPU last long task happened at 940 ms

    Individual Long Tasks

    namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
    self503164window
    self66790window
    self940102window

    CPU time spent

    Calculated using Tracium.

    Categories (ms)
    parseHTML357
    styleLayout236
    paintCompositeRender42
    scriptParseCompile2
    scriptEvaluation181
    garbageCollection4
    other191
    Events (ms)
    ParseHTML193
    HTMLDocumentParser::MaybeFetchQueuedPreloads166
    Layout118
    UpdateLayoutTree117
    RunTask113
    v8.run87
    FunctionCall57
    Paint33
    EventDispatch23
    DocumentLoader::BodyLoadingFinished17
    PrePaint16

    Time spent per request

    URLCPU time (ms)
    https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR81
    https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js35
    https://www.google.com/cse/static/element/5c8d58cbdc1332a7/cse_element__fr.js?usqp=CAI%3D30
    https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js28
    https://www.proantic.com/antiquaires.php23

    CPU time spent

    Tool/domainTime (ms)
    Google Tag Manager80.9
    Google CDN34.7
    Other Google APIs/SDKs30.0
    Cloudflare CDN27.7
    www.proantic.com23.5
    | Categories | | Tools | | First vs third | 

    Third party

    Third party requests categorised by Third party web version 0.26.2.

    CategoryRequests
    cdn 3
    survelliance 6
    tag-manager 1
    marketing 1
    utility 4
    CategoryNumber of tools
    cdn 3
    survelliance 3
    tag-manager 1
    marketing 1
    utility 1

    Third party requests and tools

    cdn (3 requests)
    Google CDN
    Cloudflare CDN
    JSDelivr CDN
    survelliance (6 requests)
    Google CDN
    Google Tag Manager
    Other Google APIs/SDKs
    tag-manager (1 requests)
    Google Tag Manager
    marketing (1 requests)
    Mailchimp
    utility (4 requests)
    Other Google APIs/SDKs

    First party requests and sizes per content type

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

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b117.0 KB892.3 KB1
    css0 b66.4 KB334.6 KB4
    javascript0 b15.0 KB47.2 KB1
    image0 b970.8 KB965.1 KB15
    font0 b770.8 KB766.6 KB11
    TotalN/A1.9 MB2.9 MB32

    Third party requests and sizes per content type

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b0 b0 b0
    css0 b11.5 KB47.7 KB3
    javascript0 b302.3 KB968.9 KB6
    image0 b0 b0 b0
    font0 b0 b0 b0
    TotalN/A313.8 KB1016.6 KB9

    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.

    TypeViolations (median)
    Critical 0 (0 issues)
    Serious1 (9 issues)
    Moderate3 (73 issues)
    Minor0 (0 issues)