https://www.antiquites-en-france.com/
Tested 2026-10-13 01:40:56 using Chrome 152.0.7977.64 (runtime settings)
This page is fast to paint, snappy to interact with and accessible, but prone to layout shifts, loose on best practices and weak on user privacy.
Visual metrics
Google Web Vitals
Accessibility · axe-core
The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page.
The page has 6 CPU long tasks with the total of 507 ms. The total blocking time is 189 ms and 2 long tasks before first contentful paint with total time of 118 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.
The page has 12 font requests. Do you really need them? What value does the fonts give the user?
Timings summary
| Metric | Min | Median | Mean | Max | Runs agree? |
|---|---|---|---|---|---|
| First visual change | 33 ms | 200 ms | 156 ms | 234 ms | runs disagree ±50% |
| Last visual change | 1.267 s | 1.302 s | 2.490 s | 4.900 s | runs disagree ±140% |
| Speed index | 453 ms | 520 ms | 1.005 s | 2.042 s | runs disagree ±153% |
| Largest image | 167 ms | 234 ms | 234 ms | 300 ms | runs disagree ±28% |
| Heading | 1.202 s | 1.267 s | 1.701 s | 2.633 s | runs disagree ±56% |
| Largest contentful paint | 167 ms | 1.202 s | 879 ms | 1.267 s | runs disagree ±46% |
| Last meaningful paint | 1.202 s | 1.267 s | 1.701 s | 2.633 s | runs disagree ±56% |
| Visual readiness | 1.067 s | 1.068 s | 2.334 s | 4.867 s | runs disagree ±178% |
| Visual complete 85 | 668 ms | 733 ms | 1.511 s | 3.133 s | runs disagree ±168% |
| Visual complete 95 | 1.168 s | 1.267 s | 2.178 s | 4.100 s | runs disagree ±116% |
| Visual complete 99 | 1.267 s | 1.302 s | 2.434 s | 4.733 s | runs disagree ±133% |
Run 1 SpeedIndex median
The red band on the timeline marks when the main thread was busy with long tasks: moments when the page could not paint or respond, however the video looks.
Download videoUse --filmstrip.showAll to show all filmstrips.
Click a frame to seek the video to that moment. The dot marks frames where the page changed visually.
How smoothly Chrome delivered frames to the screen during the test. Dropped counts only frames Chrome flags as affecting smoothness. On mostly-static pages the longest gap includes idle time where there was simply nothing to draw.
Rendering was not meaningfully delayed. First paint landed at 228 ms on a 77 ms first byte; the 1 render-blocking request was done by 111 ms and the remaining ~117 ms is style and layout work (15 ms of it measured style recalculation). The largest paint followed at 504 ms.
Style the browser had to recalculate before it could paint: many elements or a lot of time spent here points at expensive CSS on the critical rendering path. The recalculation count and the largest single one tell the two problems apart: one massive style change touching most of the page (few recalculations, the largest close to the total) needs different medicine than thousands of tiny ones (many recalculations, each tiny).
One large recalculation dominates. Restyling 369 elements cost 15 ms before the page painted (6.4 % of the time to First Contentful Paint), and a single recalculation of 369 elements accounts for 14 ms of it. Look for one class or inline-style change on a large container near the top of the DOM that restyles the whole subtree at once. The changes driving it are listed under Style invalidations below.
The recalculation work before first paint is 6.4 % of the time to First Contentful Paint.
JavaScript read a layout value (offsetTop, getBoundingClientRect, …) while the page was mid-change, so the browser had to re-layout synchronously, work that blocks rendering. Reflows before First Contentful Paint delayed the first pixels; reflows before Largest Contentful Paint delayed the main content.
That is 6.6 % of the time to Largest Contentful Paint. The number of reflows matters more than the milliseconds: layout thrashing multiplies on slower devices.
See every forced reflow for the whole page load on the CPU tab
Blocking requests delay both paints: the browser renders nothing until they arrive, so they push First Contentful Paint and everything after it, including the largest paint (LCP). Requests that block the parser inside the body stall everything after them in the document. Load JavaScript with defer or async, and keep non-critical CSS off the critical path with media attributes. Bars show when each request loaded on a clock that runs to the last paint (the dashed line is FCP, the clock ends at LCP); the gap after the bars is style and layout work. Web fonts are context, not blockers: text renders invisible or in a fallback face while they load, so a font finishing after a paint is the classic reason text changed late.
| Request | When it loaded | Transfer | Download |
|---|---|---|---|
document | 113 ms | 19.2 KB | 112 ms |
971.6a739711.cssblocking | 22 ms | 18.8 KB | 22 ms |
71 ms | 23.2 KB | 71 ms | |
110 ms · past LCP | 22.4 KB | 110 ms | |
10 ms | 23.3 KB | 10 ms | |
0126 ms378 msFCP 228 msLCP 504 ms |
Why the browser had to recalculate style and layout: every DOM/style change invalidates some set of nodes, and the same class or attribute churning over and over is the pattern to hunt. Counts, not milliseconds: the time is in the style recalculation numbers above.
Chase what keeps changing after the page is up. 955 style recalculations and 2 007 layout invalidations fired after first paint, on a page the user was already looking at. The biggest driver is attribute class (25×). Start with the script under "Scripts causing invalidations" that keeps triggering it.
attribute: class25×attribute: data-aos-easing1×attribute: data-aos-duration1×attribute: data-aos-delay1×Invalidations while the largest paint was still pending, so these delayed it.
| Reason | Style recalculations | Layout |
|---|---|---|
| An animation updated stylesAnimate transform and opacity so the compositor can run it off the main thread. | 2 | – |
| A stylesheet rule changed | 225 | – |
| An @keyframes rule changed | 220 | – |
| A node was inserted into the page | 46 | – |
| Related style rule | 45 | – |
| Frame | 2 | – |
| Control | 1 | – |
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 1 363 |
| An element entered layout | – | 387 |
| An element left layout | – | 43 |
| An element's size changed | – | 11 |
| Scrollbar changed | – | 4 |
Churn on the fully rendered page: wasted work and possible jank, but no paint delay.
| Reason | Style recalculations | Layout |
|---|---|---|
| An animation updated stylesAnimate transform and opacity so the compositor can run it off the main thread. | 410 | – |
| Related style rule | 3 | – |
| JavaScript changed an inline styleSet a class instead of writing element.style, so the browser can batch the work. | 1 | – |
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 12 |
| An element entered layout | – | 39 |
| A style change forced layout | – | 147 |
| An element's size changed | – | 1 |
The page being constructed and styled for the first render. Expected work, shown for scale.
| Reason | Style recalculations | Layout |
|---|---|---|
| A stylesheet rule changed | 1 | – |
| A node was inserted into the page | 9 | – |
| Frame | 1 | – |
| An element entered layout | – | 592 |
| An element left layout | – | 3 |
| An element's size changed | – | 2 |
171 animations run on the main thread instead of on the browser's fast path that animates without blocking other page work (the compositor); they can make the rendering you see above janky. See them on the CPU tab.
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 9.2.1.
googleTagManagerThe page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page.
Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance.
longTasksThe page has 6 CPU long tasks with the total of 507 ms. The total blocking time is 189 ms and 2 long tasks before first contentful paint with total time of 118 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.
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.
fewFontsThe page has 12 font requests. Do you really need them? What value does the fonts give the user?
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.
javascriptSizeThe total JavaScript transfer size is 421 kB and the uncompressed size is 1.3 MB. This is totally crazy! There is really room for improvement here.
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?
privateAssetsThe page has 2 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.
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.
decodingAsyncThe page has 2 images (out of 14) without a decoding hint. Add decoding="async" to non-critical images so the browser can decode them off the main thread.
Setting decoding="async" on an <img> tells the browser it can decode the image off the main thread, which keeps the page responsive to user interactions while images are being processed. The default ("auto") leaves the choice to the browser. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#decoding
modernImageFormatsThe page ships 2 images (out of 14) in JPEG/PNG/GIF without a modern alternative. Wrap them in a <picture> with a <source type="image/avif"> or "image/webp" before the legacy <img>, or serve modern formats from your image pipeline directly. AVIF and WebP usually deliver 25–50% smaller files at the same quality.
AVIF and WebP routinely deliver 25–50% smaller files than JPEG and PNG at the same perceived quality, and every browser version still under support understands at least one of them. Ship modern formats either through a <picture> element with <source type="image/avif"> / "image/webp" entries in front of the legacy <img>, or directly from a content-negotiating image pipeline that returns AVIF / WebP when the client accepts it. https://web.dev/articles/serve-images-webp
assetsRedirectsThe page has 1 redirect. 1 of the redirects are from the base domain, please fix them!
A redirect is one extra step for the user to download the asset. Avoid that if you want to be fast. Redirects are even more of a showstopper on mobile.
cacheHeadersThe 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 18 B the next access.
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.
compressAssetsThe page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.
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.
| URL | Transfer | Content |
|---|---|---|
| https://www.antiquites-en-france.com/cdn-cgi/challenge-platform/h/g/scripts/jsd/...4a60fa397/main.js | 12.2 KB | 23.5 KB |
lazyLoadingImagesThe page has 1 below-the-fold image without loading="lazy". Add loading="lazy" so the browser defers downloading and decoding them until the user scrolls them into view.
Adding loading="lazy" to an <img> tells the browser not to download or decode it until it is close to the viewport. For images that the user may never see (deep in the page, behind a tab, in a footer carousel), this saves bandwidth and main-thread time during initial render. The LCP image and any image in the initial viewport should NOT be lazy-loaded — that delays the first paint. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#loading
inlineCssThe 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.
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.
cacheHeadersLongThe page has 4 requests that have a shorter cache time than one year (but still a cache time).
Setting a cache header is good. Setting a long cache header (a year) is even better because the asset will stay in the browser cache across visits. For content-hashed URLs (e.g. app.4af2.css) you can safely use Cache-Control: max-age=31536000, immutable. For unversioned URLs that may change, use a revalidating strategy instead.
cumulativeLayoutShiftYou have a poor cumulative layout shift score (0.2883). It is in the Google Web Vitals poor range, with a shift higher than 0.25. You should manually check the filmstrip or video and check if it will affect the user.
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.
thirdPartyThe page do 40% requests to third party domains (17 requests and 402.2 kB). First party is 26 requests and 368.5 kB. The page transfer more bytes from third party domains (402.2 kB) then first party (368.5 kB). The regex .*antiquites-en-france.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
unnecessaryHeadersThere are 24 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 31 responses that sets a server header.
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.
longHeadershttps://www.antiquites-en-france.com/ has a header content-security-policy-report-only that is 1031 characters long. https://www.antiquit.../a49aa3a42ab92a33 has a header cf-chl-out-s that is 2265 characters long.
Do not send response headers that are too long.
referrerPolicyNo <meta name="referrer"> tag was found on the page. Set a Referrer-Policy response header (preferred) or add a meta tag, for example <meta name="referrer" content="strict-origin-when-cross-origin">.
Without an explicit referrer policy the browser falls back to the user-agent default and may leak the full URL of the previous page (including query strings) to every cross-origin request. Set a Referrer-Policy response header (preferred) or a <meta name="referrer"> tag in the document. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
surveillanceThe page embeds 2 resources from companies that profit from user surveillance. Consider privacy-respecting alternatives.
Embedding scripts or iframes from companies whose business model is surveillance capitalism (Google, Facebook, etc.) leaks detailed user data on every page view, often before the user has had a chance to consent. See https://en.wikipedia.org/wiki/Surveillance_capitalism for background. Prefer privacy-respecting alternatives where possible.
crossOriginEmbedderPolicyHeaderSet a Cross-Origin-Embedder-Policy header (typically require-corp or credentialless) on the document response to control cross-origin embedding.
Cross-Origin-Embedder-Policy (COEP) makes the page refuse to load cross-origin subresources unless they explicitly opt in via CORP or CORS. Together with Cross-Origin-Opener-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy
crossOriginOpenerPolicyHeaderSet a Cross-Origin-Opener-Policy header (typically same-origin) on the document response to isolate the page from cross-origin windows.
Cross-Origin-Opener-Policy (COOP) lets a page sever its window-group ties to cross-origin documents that opened it or that it opens. Together with Cross-Origin-Embedder-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy
crossOriginResourcePolicyHeaderSet a Cross-Origin-Resource-Policy header (same-origin, same-site or cross-origin) on the document response to limit who may embed it.
Cross-Origin-Resource-Policy (CORP) is a per-response opt-in that tells the browser which origins are allowed to embed the resource. It blocks cross-origin or cross-site no-cors embedding (img, script, iframe, etc.) and is one of the building blocks of cross-origin isolation. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Resource-Policy
permissionsPolicyHeaderSet a Permissions-Policy header to control which browser features the page can use.
The Permissions-Policy response header (the successor to Feature-Policy) lets a site explicitly opt in or out of powerful browser features such as camera, microphone, geolocation, payment and clipboard. Setting a strict policy reduces the attack surface and limits what embedded third parties can do. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
thirdPartyPrivacyThe page has 12% requests that are 3rd party (5 requests with a size of 310.3 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 3 tag-manager requests and uses 1 tag-manager tool. The page do 3 survelliance requests and uses 1 survelliance tool. The page do 5 surveillance requests and uses 2 surveillance tools. The page do 2 analytics requests and uses 1 analytics tool.
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.
contentSecurityPolicyHeaderThe policy declares no default-src or script-src directive, which means scripts can be loaded from anywhere. Add at least default-src so unknown directive types fall back to a safe value. Set object-src 'none' (or a default-src 'none' fallback) so the page cannot load Flash, plugins or other legacy embeddable content.
A Content-Security-Policy response header tells the browser which sources of script, style, and other content are allowed. The most effective form is a strict CSP using nonces or hashes together with strict-dynamic; the worst is a missing header, with unsafe-inline and unsafe-eval close behind. https://web.dev/articles/strict-csp
A snapshot of what the browser actually built for this page: the document, how big and deep the DOM tree is and what it kept in storage. Big, deep trees are slower to style and lay out, so the counts Chrome warns about carry a flag.
Document
What the page says it is and how large it rendered.
DOM structure
How much markup the browser has to build, style and lay out.
What the page stored on the client, and the network it was tested on.
Data collected using
Coach-core version 9.2.1. With updated code from
Webappanalyzer 2026-05-04. Use
--browsertime.firefox.includeResponseBodies html or
--browsertime.chrome.includeResponseBodies html to help Wappalyzer find more information about technologies used.
Data collected using Third Party Web version 0.29.2.
Data from run 1
0.0s0.3s0.4s0.6s0.8s1.0s1.1s1.3sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > main > section:eq(0) > div:eq(1) > div > h1
The LCP element is highlighted in the screenshot. If nothing is highlighted the element was removed before the screenshot or the LCP API couldn't find it.
How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.
One shift is 85% of your 0.288 CLS. section:eq(1) moved at 415 ms. Reserve space for whatever renders into that spot, a fixed height or an aspect-ratio box, so later content stops pushing the page around.
Worst first, showing shifts of 0.01 and up. Each percentage is that shift's exact share of the score.
body > main > section:eq(1)body > main > section:eq(2)body > header > div:eq(0) > div > navbody > header > div:eq(0) > div > divbody > header > div:eq(1) > div > div > form > divbody > main > section:eq(0) > div:eq(1) > divbody > main > section:eq(0) > div:eq(1) > div > div:eq(1) > div:eq(2)body > main > section:eq(0) > div:eq(1) > div > div:eq(1) > div:eq(1)body > main > section:eq(0) > div:eq(1) > div > p:eq(0) > #textbody > main > section:eq(0) > div:eq(1) > div > div:eq(1) > div:eq(0)body > main > section:eq(0) > div:eq(0)body > main > section:eq(0) > div:eq(1) > div > div:eq(1)body > main > section:eq(0) > div:eq(1) > div > div:eq(0) > a:eq(0)body > main > section:eq(0) > div:eq(1) > div > div:eq(0) > a:eq(1) > svg
Elements that shifted by more than 0.01 are highlighted in the screenshot. If an element shifted outside the viewport, it won't appear here. Check the video or filmstrip to see the shift.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
https://www.antiquites-en-france.com/
| Header | Value |
|---|---|
age | 0 |
alt-svc | h3=":443"; ma=86400 |
cache-control | max-age=180, public, s-maxage=180 |
cf-cache-status | DYNAMIC |
cf-ray | a49aa3a42ab92a33-CDG |
content-encoding | zstd |
content-security-policy | frame-ancestors 'self' |
content-security-policy-report-only | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://ssl.google-analytics.com https://js.stripe.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://*.clarity.ms https://connect.facebook.net https://*.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://www.gstatic.com; img-src 'self' data: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://api.stripe.com https://maps.googleapis.com https://*.clarity.ms https://*.posthog.com https://connect.facebook.net https://*.s3.amazonaws.com https://*.s3.eu-west-3.amazonaws.com https://*.io.cloud.ovh.net; frame-src 'self' https://js.stripe.com https://checkout.stripe.com https://www.google.com https://www.googletagmanager.com https://recaptcha.google.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none' |
content-type | text/html; charset=UTF-8 |
date | Tue, 13 Oct 2026 01:40:57 GMT |
nel | {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800} |
referrer-policy | strict-origin-when-cross-origin |
report-to | {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=ETKO8D0hpOVKPThwyJq8pda00rrLFm2tqCvg6f7YmexnZzjTsQj7XE2XN8wUcMlQxGU%2FWa9xnWuXTVFCG3MzZwso8AHPKZ2wam4CJ%2FnvA6zNKEuxhoM6mItUrbYtn6nMOYHMejz8Cpl9Rs3Afsz9"}]} |
server | cloudflare |
strict-transport-security | max-age=31536000; includeSubDomains |
vary | Accept-Encoding |
x-aef-cache | STALE |
x-content-digest | enadd8d1e779b01e24888d1914f045bf06 |
x-content-type-options | nosniff |
x-frame-options | SAMEORIGIN |
x-powered-by | PHP/8.5.11 |
x-symfony-cache | stale/invalid/store |
Transfer size752.7 KB
Content size1.7 MB
Requests42
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 19.2 KB | 111.4 KB | 1 |
| css | 0 b | 24.8 KB | 131.2 KB | 2 |
| javascript | 0 b | 411.1 KB | 1.2 MB | 9 |
| image | 5.5 KB | 94.3 KB | 93.6 KB | 14 |
| font | 0 b | 200.8 KB | 194.7 KB | 12 |
| plain | 0 b | 2.4 KB | 0 b | 4 |
| Total | 5.5 KB | 752.7 KB | 1.7 MB | 42 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.antiquites-en-france.com | 717 ms | 359.8 KB | 788.1 KB | 26 |
| www.googletagmanager.com | 339 ms | 303.0 KB | 894.7 KB | 3 |
| aef-storage.s3.sbg.io.cloud.ovh.net | 1.749 s | 89.8 KB | 89.8 KB | 12 |
| region1.google-analytics.com | 49 ms | N/A | 0 b | 2 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 year | 1 year |
| Last modified | 1 hour | 5 weeks | 10 weeks |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 1.5 KB | 1 |
| font | 0 b | 0 |
| favicon | 0 b | 0 |
| plain | 0 b | 1 |
| Total | 1.5 KB | 2 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 190.2 KB | 2 |
| image | 7.7 KB | 2 |
| font | 45.7 KB | 2 |
| favicon | 0 b | 0 |
| plain | 2.4 KB | 4 |
| Total | 246.0 KB | 11 |
Tasks ≥ 50 ms blocking the main thread, collected via the Long Task API.
A long animation frame (LOAF) is a frame that took ≥ 50 ms from input to the next paint. The part beyond the threshold is blocking time, the number that hurts Interaction to Next Paint and Total Blocking Time. Break long tasks up (scheduler.yield(), smaller chunks) or move the work off the main thread. Read more about the Long Animation Frames API.
| Script | Frames | Time running | Blocking (share by run time) | Forced style & layout | Triggered by |
|---|---|---|---|---|---|
| js3rd party | 1 | 156.3 ms | 105.4 ms | – | script tag |
| main.js | 1 | 109.8 ms | 61.5 ms | 0.9 ms | script tag |
| gtm.js3rd party | 1 | 73.5 ms | 28.2 ms | – | script tag |
| app.183e975c.js | 1 | 57 ms | 13.3 ms | 1.2 ms | script tag |
| 686.1d5dc2ba.js | 1 | 48.9 ms | 8.2 ms | 25.9 ms | timer or animation callback |
| inline script in the document | 1 | 8.6 ms | 2 ms | – | script tag |
A frame's blocking time is split between its scripts by their share of the frame's work, capped at each script's own run time — blocking from work no script owns (HTML parsing, browser internals) stays unattributed. The per-script blocking view below uses the same attribution.
The browser did not report which script was responsible for this frame — typically its own style/layout work, or a cross-origin script it will not name.
The browser did not report which script was responsible for this frame — typically its own style/layout work, or a cross-origin script it will not name.
The browser did not report which script was responsible for this frame — typically its own style/layout work, or a cross-origin script it will not name.
1 more long frame carried no blocking time (nothing ran past the 50 ms threshold) — long, but harmless to INP and TBT.
How much each script blocked the main thread, derived from the Long Animation Frame API. Each frame's blocking time is split between its scripts by their share of the frame's work, capped at each script's own run time — blocking from work no script owns (HTML parsing, browser internals) is not attributed (older data credits the script that started the frame). The closest answer to "which script should I fix to improve TBT" the platform exposes.
Total Blocking Time attributed per script from the Chrome trace: every main-thread task longer than 50 ms blocks input for the remainder, and each blocking task is credited to the script whose own code ran the longest during that task.
All main-thread work during the full page load, not just the share that blocked input. Calculated from the Chrome trace.
parseHTMLstyleLayoutscriptParseCompilescriptEvaluationpaintCompositeRendergarbageCollectionotherHow much setTimeout/setInterval work the page runs, credited to the script that scheduled each timer. Many zero-delay timers mean work sliced into a machine-gun of tiny tasks; repeating timers are polling.
| Set by | Delay | Type | Times set | Times fired | Fire time |
|---|---|---|---|---|---|
watch in https://www.antiquites-en-france.com/build/686.1d5dc2ba.js:25 | 0 ms | once | 1 | 1 | 40.4 ms |
kd in https://www.googletagmanager.com/gtm.js?id=GTM-PXVP329K:169 | 0 ms | once | 12 | 12 | 36.6 ms |
run in https://www.antiquites-en-france.com/:2214 | 120 ms | once | 1 | 1 | 9.5 ms |
kd in https://www.googletagmanager.com/gtag/js?id=G-58XGFJWZ1E&cx=c>m=4e6a91:347 | 0 ms | once | 28 | 28 | 1.9 ms |
l.Yg in https://www.googletagmanager.com/gtag/js?id=G-58XGFJWZ1E&cx=c>m=4e6a91:1082 | 5000 ms | once | 1 | 1 | 1.5 ms |
Hm in https://www.googletagmanager.com/gtm.js?id=GTM-PXVP329K:332 | 500 ms | once | 12 | 12 | 0.8 ms |
openCookieBanner in https://www.antiquites-en-france.com/:2208 | 200 ms | once | 1 | 1 | 0.3 ms |
| https://www.antiquites-en-france.com/build/971.c0d484bd.js:1 | 5000 ms | once | 1 | 1 | 0.3 ms |
ld in https://www.googletagmanager.com/gtag/js?id=G-58XGFJWZ1E&cx=c>m=4e6a91:347 | 86400000 ms | recurring | 2 | 0 | 0.0 ms |
r.l in https://www.antiquites-en-france.com/build/runtime.882d785a.js:1 | 120000 ms | once | 1 | 0 | 0.0 ms |
A forced reflow happens when JavaScript reads a layout-triggering property (offsetTop, getBoundingClientRect, …) inside a handler, forcing the browser to synchronously recompute layout. The scripts below caused most of the page's reflows. Fix them in priority order.
Each long animation frame reports how much time each script spent forcing synchronous style and layout, i.e. JavaScript reading layout-triggering properties mid-execution. Same actionable answer as forced reflows above but measured directly by the browser instead of inferred from the trace.
Main-thread CPU time from the Chrome trace split by domain. First party is antiquites-en-france.com.
Animations that fell back from the compositor to the main thread, blocking each frame instead of running on the GPU.
Each chip below is a CSS property the page tried to animate that Chrome couldn't hand to the compositor. Swap it for a transform or opacity equivalent where you can.
border-top-left-radius18×border-top-right-radius18×border-bottom-left-radius18×border-bottom-right-radius18×box-shadow12×border-left-color6×border-left-width6×border-right-color6×border-right-width6×color6×border-top-color6×border-top-width6×padding-bottom6×font-weight6×padding-left6×padding-right6×padding-top6×border-bottom-color6×border-bottom-width6×font-size3×Want to dig deeper? Download the Chrome trace and drag-and-drop it into Performance in DevTools.
Third party requests categorised by Third party web version 0.29.2.
Requests by category10
Domains that didn't match any tool in Third party web. If you are sure they are third party domains, please do a PR to that project. You can also fine tune the list using --firstParty.
Transfer size752.7 KB
Content size1.7 MB
Requests43
Calculated using .*antiquites-en-france.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 19.2 KB | 111.4 KB | 1 |
| css | 0 b | 24.8 KB | 131.2 KB | 2 |
| javascript | 0 b | 108.1 KB | 347.0 KB | 7 |
| image | 0 b | 4.6 KB | 3.8 KB | 2 |
| font | 0 b | 200.8 KB | 194.7 KB | 12 |
| favicon | 0 b | 0 b | 0 b | 0 |
| plain | 0 b | 2.4 KB | 0 b | 1 |
| Total | N/A | 359.8 KB | 788.1 KB | 26 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 0 b | 0 b | 0 |
| javascript | 0 b | 303.0 KB | 894.7 KB | 2 |
| image | 5.5 KB | 89.8 KB | 89.8 KB | 12 |
| font | 0 b | 0 b | 0 b | 0 |
| favicon | 0 b | 0 b | 0 b | 0 |
| plain | 0 b | 18 B | 0 b | 3 |
| Total | 5.5 KB | 392.8 KB | 984.5 KB | 17 |
Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Tested using axe-core version 4.11.4. Read more about axe-core.
✓ No accessibility violations across the runs.