Page summary

Summary

Metric	Value
Page metrics
Performance Score	85
Total Page Transfer Size	644.9 KB
Requests	22
Timing metrics
TTFB [median]	42 ms
First Paint [median]	148 ms
Fully Loaded [median]	567 ms
Google Web Vitals
TTFB [median]	42 ms
First Contentful Paint (FCP) [median]	148 ms
Largest Contentful Paint (LCP) [median]	148 ms
Cumulative Layout Shift (CLS) [median]	0.04
Total Blocking Time [median]	75 ms
Max Potential FID [median]	88 ms
CPU metrics
CPU long tasks [median]	4
CPU longest task duration	108 ms
CPU last long task happens at	463 ms
Visual Metrics
First Visual Change [median]	167 ms
Speed Index [median]	174 ms
Visual Complete 85% [median]	167 ms
Visual Complete 99% [median]	234 ms
Last Visual Change [median]	234 ms

Timings Summary

Waterfall

Run 2 SpeedIndex median

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.2 sLayout Shift 0.03895 126 msCPU Long Task duration 55 msFirst Contentful Paint 148 msLCP <IMG> 148 msFirst Visual Change 167 msVisual Complete 85% 167 msDOM Content Loaded Time 189 msPage Load Time 197 msLayout Shift 0.00086 200 ms

0.3 sLast Visual Change 234 msVisual Complete 95% 234 msVisual Complete 99% 234 msLargest Image 234 msHeading 234 msCPU Long Task duration 74 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 85
• Privacy score 74
• Best practice score 85

Performance advice (85)

Show/hide details

Title	Advice	Score
Avoid slowing down the critical rendering path (avoidRenderBlocking)	The page has 1 blocking requests and 1 in body parser blocking (1 JavaScript and 1 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://www.googletagmanager.com/gtag/js?id=UA-96091873-1	89
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://www.anticstore.com/js/js-V2-min.js
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.	95
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 5 CPU long tasks with the total of 356 ms. The total blocking time is 72 ms and 2 long tasks before first contentful paint with total time of 134 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.	0
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 self self self self
Long cache headers is good (cacheHeadersLong)	The page has 14 requests that have a shorter cache time than 30 days (but still a cache time).	86
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.anticstore.com/css/css-V24-min.css https://www.googletagmanager.com/gtag/js?id=UA-96091873-1 https://www.anticstore.com/img/acc/objet-art-21.jpg https://www.anticstore.com/img/acc/mobilier-1.jpg https://www.anticstore.com/img/acc/peinture-1.jpg https://www.anticstore.com/img/acc/sculpture-3.jpg https://www.anticstore.com/img/acc/bijouterie-4.jpg https://www.anticstore.com/js/js-V2-min.js https://www.anticstore.com/img/charte/logo-anticstore.png https://www.anticstore.com/img/charte/logo_ASfooter.png https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&cx=c&gtm=4e5bi1 https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&cx=c&gtm=4e5bi1 https://www.anticstore.com/img/favicon.ico https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&cx=c&gtm=4e5bi1
Always compress text content (compressAssets)	The page has 4 requests that are served uncompressed. You could save a lot of bytes by sending them compressed instead.	60
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=UA-96091873-1 111.3 KB 311.5 KB https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&cx=c&gtm=4e5bi1 129.8 KB 366.2 KB https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&cx=c&gtm=4e5bi1 110.9 KB 311.0 KB https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&cx=c&gtm=4e5bi1 132.1 KB 375.5 KB
Avoid too many fonts (fewFonts)	The page has 4 font requests. Do you really need them? What value does the fonts give the user?	60
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.anticstore.com/css/robotocondensed-regular-webfont.woff2 https://www.anticstore.com/css/OpenSans-Regular-webfont.woff2 https://www.anticstore.com/css/OpenSans-Italic-webfont.woff2 https://www.anticstore.com/css/icomoon2.woff2
Total JavaScript size shouldn't be too big (javascriptSize)	The total JavaScript transfer size is 520.4 kB and the uncompressed size is 1.5 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://www.googletagmanager.com/gtag/js?id=UA-96091873-1 111.3 KB 311.5 KB https://www.anticstore.com/js/js-V2-min.js 3.3 KB 16.9 KB https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&cx=c&gtm=4e5bi1 129.8 KB 366.2 KB https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&cx=c&gtm=4e5bi1 110.9 KB 311.0 KB https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&cx=c&gtm=4e5bi1 132.1 KB 375.5 KB https://www.google-analytics.com/analytics.js 20.8 KB 51.1 KB
Don't use private headers on static content (privateAssets)	The page has 5 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.	50
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=UA-96091873-1 https://www.anticstore.com/js/js-V2-min.js https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&cx=c&gtm=4e5bi1 https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&cx=c&gtm=4e5bi1 https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&cx=c&gtm=4e5bi1
Avoid missing and error requests (responseOk)	The page has 1 error response. The page has 1 response with code 404.	90
Description: Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it.
Offenders: https://www.anticstore.com/i

Best practice advice (85)

Show/hide details

Title	Advice	Score
Avoid too many third party requests (thirdParty)	The page do 32% requests to third party domains (7 requests and 517 kB). First party is 15 requests and 143.4 kB. The page transfer more bytes from third party domains (517 kB) then first party (143.4 kB). The regex .*anticstore.* was used to calculate first/third party requests.	0
Description: Do not load most of your content from third party URLs.
Avoid unnecessary headers (unnecessaryHeaders)	There are 22 responses that sets both a max-age and expires header. There are 3 responses that sets a pragma no-cache header (that is a request header). There are 7 responses that sets a server header.	68
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.anticstore.com/i https://www.anticstore.com/i https://www.anticstore.com/css/css-V24-min.css https://www.googletagmanager.com/gtag/js?id=UA-96091873-1 https://www.googletagmanager.com/gtag/js?id=UA-96091873-1 https://www.anticstore.com/img/acc/objet-art-21.jpg https://www.anticstore.com/img/acc/mobilier-1.jpg https://www.anticstore.com/img/acc/peinture-1.jpg https://www.anticstore.com/img/acc/sculpture-3.jpg https://www.anticstore.com/img/acc/bijouterie-4.jpg https://www.anticstore.com/js/js-V2-min.js https://www.anticstore.com/img/charte/logo-anticstore.png https://www.anticstore.com/img/charte/logo_ASfooter.png https://www.anticstore.com/css/robotocondensed-regular-webfont.woff2 https://www.anticstore.com/css/OpenSans-Regular-webfont.woff2 https://www.anticstore.com/css/OpenSans-Italic-webfont.woff2 https://www.anticstore.com/css/icomoon2.woff2 https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&cx=c&gtm=4e5bi1 https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&cx=c&gtm=4e5bi1 https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&cx=c&gtm=4e5bi1 https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&cx=c&gtm=4e5bi1 https://www.anticstore.com/img/favicon.ico https://region1.google-analytics.com/g/collect...ics.com/g/collect https://region1.google-analytics.com/g/collect...ics.com/g/collect https://region1.google-analytics.com/g/collect...ics.com/g/collect https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&cx=c&gtm=4e5bi1 https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&cx=c&gtm=4e5bi1 https://www.google-analytics.com/analytics.js https://www.google-analytics.com/analytics.js https://region1.google-analytics.com/g/collect...ics.com/g/collect https://region1.google-analytics.com/g/collect...ics.com/g/collect https://region1.google-analytics.com/g/collect...ics.com/g/collect

Privacy advice (74)

Show/hide details

Title	Advice	Score
Avoid using Google Analytics (ga)	The page is using Google Analytics meaning you share your users private information with Google. You should use analytics that care about user privacy, something like https://matomo.org.	0
Description: Google Analytics share private user information with Google that your user hasn't agreed on sharing.
Use a good Content-Security-Policy header to make sure you you avoid Cross Site Scripting (XSS) attacks. (contentSecurityPolicyHeader)	Set a Content-Security-Policy header to make sure you are not open for Cross Site Scripting (XSS) attacks. You can start with setting a Content-Security-Policy-Report-Only header, that will only report the violation, not stop the download.	0
Description: Content Security Policy is delivered via a HTTP response header, and defines approved sources of content that the browser may load. It can be an effective countermeasure to Cross Site Scripting (XSS) attacks and is also widely supported and usually easily deployed. https://scotthelme.co.uk/content-security-policy-an-introduction/.
Offenders: https://www.anticstore.com/i
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.anticstore.com/i
Do not share user data with third parties. (thirdPartyPrivacy)	The page has 32% requests that are 3rd party (7 requests with a size of 517 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 4 tag-manager requests and uses 1 tag-manager tool. The page do 7 survelliance requests and uses 2 survelliance tools. The page do 3 analytics requests and uses 1 analytics 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://www.googletagmanager.com/gtag/js?id=UA-96091873-1 https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&cx=c&gtm=4e5bi1 https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&cx=c&gtm=4e5bi1 https://region1.google-analytics.com/g/collect...ics.com/g/collect https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&cx=c&gtm=4e5bi1 https://www.google-analytics.com/analytics.js https://region1.google-analytics.com/g/collect...ics.com/g/collect

Page info

Page info
Title	Erreur 404 : document non trouvé
Width	1350
Height	1211
DOM elements	184
Avg DOM depth	6
Max DOM depth	8
Iframes	0
Script tags	8
Local storage	0 b
Session storage	0 b
Network Information API	4g

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
PHP 7.2	100	Programming languages
HSTS	100	Security
HTTP/3	100	Miscellaneous

Data collected using Third Party Web 0.26.2

Tag-manager
Google Tag Manager
Survelliance
Google Tag Manager
Google Analytics
Analytics
Google Analytics

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 src="/img/acc/objet-art-23.jpg" width="230" alt="Objet d'art">
Render time	148 ms
Element render delay	76 ms
TTFB	42 ms
Resource delay	8 ms
Resource load duration	22 ms
Elements that needed recalculate style before LCP	218
Time spent in recalculate style before LCP	6.369 ms
Load time	87 ms
URL	https://www.anticsto.../objet-art-23.jpg
Size (width*height)	51076
DOM path
div#page > div:eq(1) > a > img> div#page > div:eq(1) > 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.03981 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.03895	<div class="vig-cat"></div>,<h2 class="titre"></h2>,<div class="vig-cat"></div>,<h2 class="titre"></h2>,<div class="vig-cat"></div>
body > div#page > div:eq(3),body > div#page > div:eq(3) > a > h2,body > div#page > div:eq(4),body > div#page > div:eq(4) > a > h2,body > div#page > div:eq(5)
0.00086	<div class="droite"></div>,<li></li>,<li></li>
body > header > div,body > header > nav > ul#menu > li:eq(1),body > header > nav > ul#menu > li:eq(2)

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 463 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 .*anticstore.* (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.