Run 3 summary

Summary

Metric	Value
Page metrics
Performance score	95
Total page size	52.2 KB
Requests	3
Timing metrics
TTFB	87 ms
First Paint	683 ms
Fully Loaded	1.186 s
Google Web Vitals
TTFB	87 ms
First Contentful Paint (FCP)	683 ms
Largest Contentful Paint (LCP)	1.259 s
Cumulative Layout Shift (CLS)	0.24
CPU metrics
CPU long tasks	1
CPU last long task happens at	202 ms

Waterfall

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 sFirst Visual Change 0 msLast Visual Change 0 msVisual Complete 85% 0 msVisual Complete 95% 0 msVisual Complete 99% 0 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 93
• Performance score 95
• Privacy score 94
• Best practice score 82

Performance advice (95)

Show/hide details

Title	Advice	Score
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 1 CPU long task with the total of 61 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 61 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.	80
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: unknown
Long cache headers is good (cacheHeadersLong)	The page has 2 requests that have a shorter cache time than 30 days (but still a cache time).	98
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/galerie/decorhome/img/small/1613195-main-68e77987ceff6.jpg https://www.proantic.com/galerie/antichita-castelbarco/img/small/1555512-main-68358e20c6c1e.jpg

Best practice advice (82)

Show/hide details

Title	Advice	Score
Cumulative Layout Shift (cumulativeLayoutShift)	You have a cumulative layout shift score (0.2368) that needs improvements. It is in the Google Web Vitals needs improvement range, shift higher than 0.1. You should manually check the filmstrip or video and check if it will affect the user.	50
Description: Cumulative Layout Shift measures the sum total of all individual layout shift scores for unexpected layout shift that occur. The metric is measuring visual stability by quantify how often users experience unexpected layout shifts. It is one of Google Web Vitals.
Meta description (metaDescription)	The meta description is too long. It has 208 characters, the recommended max is 155	50
Description: Use a page description to make the page more relevant to search engines.
Page title (pageTitle)	The title is too long by 10 characters. The recommended max is 60	50
Description: Use a title to make the page more relevant to search engines.
Do not send too long headers (longHeaders)	https://www.proantic.com/ has a header content-security-policy that is 1923 characters long.	99
Description: Do not send response headers that are too long.
Offenders: https://www.proantic.com/
Avoid unnecessary headers (unnecessaryHeaders)	There are 2 responses that sets both a max-age and expires header. There are 3 responses that sets a server header.	95
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/ https://www.proantic.com/galerie/decorhome/img/small/1613195-main-68e77987ceff6.jpg https://www.proantic.com/galerie/decorhome/img/small/1613195-main-68e77987ceff6.jpg https://www.proantic.com/galerie/antichita-castelbarco/img/small/1555512-main-68358e20c6c1e.jpg https://www.proantic.com/galerie/antichita-castelbarco/img/small/1555512-main-68358e20c6c1e.jpg

Privacy advice (94)

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/

Page info

Page info
Title	Proantic: Achetez des antiquités et objets d'art présentés par des ant
Width	1350
Height	8583
DOM elements	752
Avg DOM depth	8
Max DOM depth	13
Iframes	0
Script tags	9
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
PayPal	100	Payment processors
Nginx	100	Web servers Reverse proxies
HSTS	100	Security
Google PageSpeed 1.13.35.2	100	Caching Web server extensions Performance

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/postaire-sebastien/img/small/1618631-main-68ef889f6e9b4.jpg" alt="COMMODE TOMBEAU ÉPOQUE LOUIS XV ESTAMPILLÉE LEONARD BOUDIN 1735-1807, 18ÈME " class="img-selection">
Render time	1.259 s
Element render delay	70 ms
TTFB	87 ms
Resource delay	79 ms
Resource load duration	1.023 s
Elements that needed recalculate style before LCP	747
Time spent in recalculate style before LCP	43.305 ms
Load time	1.206 s
URL	https://www.proantic...68ef889f6e9b4.jpg
Size (width*height)	56280
DOM path
div#section-selection > div:eq(1) > div > div:eq(0) > div:eq(0) > div > a > img> div#section-selection > div:eq(1) > div > div:eq(0) > div:eq(0) > div > a > 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.23683 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.23682	<div class="w-container div-container-1200"></div>,,<div class="w-row row-selection" style="padding-top:0px;"></div>,<div class="overlay-selection nouveautes accueil"></div>,
body > div#section-selection > div:eq(1),body > div#section-selection > div:eq(0) > div > h1 > #text,body > div#section-selection > div:eq(1) > div > div:eq(0),body > div#section-selection > div:eq(1) > div > div:eq(0) > div:eq(0) > div > div,body > div#section-selection > div:eq(0) > div > h2 > #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

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.

CDP Performance

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

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

First party requests and sizes per content type

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

Third party requests and sizes per content type

Screenshots

afterPageCompleteCheck.png

layoutShift.png

largestContentfulPaint.png

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