Tested 2026-10-01 01:39:05 using Chrome 152.0.7977.64 (runtime settings)
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 388 ms on a 172 ms first byte; the 3 render-blocking requests were done by 241 ms and the remaining ~147 ms is style and layout work (15 ms of it measured style recalculation and forced reflows). The largest paint followed at 608 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).
Style recalculation is not holding up your paint. 14 ms of restyling before the page painted, 3.6 % of the time to First Contentful Paint. Nothing here needs attention.
The recalculation work before first paint is 3.6 % 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 12 % 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 | 177 ms | 52.9 KB | 176 ms |
jquery-3.7.1.min.jsblocking | 50 ms | 29.1 KB | 50 ms |
hku6yoe.cssblocking | 39 ms | 1.2 KB | 39 ms |
css2blocking | loaded after LCP, at 841 ms | 960 B | 34 ms |
bayoux.min.cssblocking | 28 ms | 787 B | 28 ms |
plugins-1.6.jsblocks parser in body | 479 ms · past LCP | 58.9 KB | 479 ms |
jquery.expander.min.jsblocks parser in body | 185 ms | 2.9 KB | 185 ms |
popper.min.jsblocks parser in body | 101 ms | 7.2 KB | 101 ms |
bootstrap.min.jsblocks parser in body | 101 ms | 14.5 KB | 101 ms |
| 3 more requests | all done by 434 ms | 29.7 KB | |
LCP resource | 298 ms | 153.1 KB | 298 ms |
loaded after LCP, at 2.666 s | 16.5 KB | 32 ms | |
loaded after LCP, at 2.667 s | 16.2 KB | 29 ms | |
loaded after LCP, at 2.667 s | 16.6 KB | 26 ms | |
0152 ms304 ms456 msFCP 388 msLCP 608 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. 829 style recalculations and 3 392 layout invalidations fired after first paint, on a page the user was already looking at. The biggest driver is pseudo valid (52×). Start with the script under "Scripts causing invalidations" that keeps triggering it.
pseudo: valid52×pseudo: invalid52×attribute: class34×attribute: data-original-title16×attribute: title16×attribute: tabindex8×class: lazyloading8×attribute: src7×pseudo: disabled4×pseudo: enabled4×class: lazyload4×class: lazyloaded4×pseudo: hover2×class: slick-arrow2×class: slick-hidden2×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. | 4 | – |
| A node was inserted into the page | 54 | – |
| Related style rule | 2 | – |
| JavaScript changed an inline styleSet a class instead of writing element.style, so the browser can batch the work. | 17 | – |
| A stylesheet rule changed | 33 | – |
| A pseudo-class state changed (:hover, :focus, …) | 1 | – |
| An element entered layout | – | 1 139 |
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 995 |
| A style change forced layout | – | 20 |
| An element left layout | – | 22 |
| An element's size changed | – | 14 |
| Unknown | – | 14 |
| An SVG element changed | – | 4 |
| Scrollbar changed | – | 1 |
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. | 333 | – |
| A node was inserted into the page | 66 | – |
| Related style rule | 128 | – |
| An @keyframes rule changed | 99 | – |
| JavaScript changed an inline styleSet a class instead of writing element.style, so the browser can batch the work. | 75 | – |
| A stylesheet rule changed | 5 | – |
| Frame | 9 | – |
| A pseudo-class state changed (:hover, :focus, …) | 1 | – |
| Attribute | 2 | – |
| An element entered layout | – | 383 |
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 179 |
| A style change forced layout | – | 526 |
| An element left layout | – | 75 |
| An element's size changed | – | 7 |
| Unknown | – | 5 |
| An SVG element changed | – | 4 |
| Scrollbar changed | – | 3 |
| Child anonymous block changed | – | 1 |
The page being constructed and styled for the first render. Expected work, shown for scale.
| Reason | Style recalculations | Layout |
|---|---|---|
| A node was inserted into the page | 41 | – |
| A stylesheet rule changed | 1 | – |
| An element entered layout | – | 125 |
| An element left layout | – | 3 |
| An element's size changed | – | 1 |
| Unknown | – | 1 |
| An SVG element changed | – | 3 |
| Scrollbar changed | – | 1 |
42 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.
avoidScalingImagesThe page has 10 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.
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.
decodingAsyncThe page has 65 images (out of 65) 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
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.
lazyLoadingImagesThe page has 45 below-the-fold images 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
longTasksThe page has 9 CPU long tasks with the total of 786 ms. The total blocking time is 336 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.
modernImageFormatsThe page ships 7 images (out of 7) 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
cacheHeadersThe page has 14 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 52.5 kB 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.
fewFontsThe page has 13 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 1.5 MB and the uncompressed size is 4.8 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?
pageSizeThe page total transfer size is 3.2 MB, which is more than the coach limit of 3 MB. That is really big and you need to make it smaller.
Avoid having pages that have a transfer size over the wire of more than 3 MB (desktop) and 2 MB (mobile) because heavy pages hurt performance and are expensive for users on metered connections. Reference: HTTP Archive median page weight in 2024 was around 2.7 MB desktop / 2.4 MB mobile, so this rule fires when a page is above the modern median.
privateAssetsThe page has 11 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.
avoidRenderBlockingThe page has 4 blocking requests and 6 in body parser blocking (6 JavaScript and 4 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://apis.google.com/js/platform.js
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.
faviconThe favicon size is 15.3 kB bytes. That's quite big, can you make it smaller?
It is easy to make the favicon big but please avoid doing that, because every browser will then perform an unnecessarily large download. And make sure the cache headers are set for a long time for the favicon. It is easy to miss since it's another content type.
imageSizeThe page total image size is 1.1 MB. It's really big. Is the page using the right format for the images? Can they be lazy loaded? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/.
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.
cacheHeadersLongThe page has 48 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.
spofThe page has 1 request inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head.
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.
assetsRedirectsThe page has 1 redirect. 1 request are from other domains, it could be 3rd-party assets doing unnecessary redirects. :(
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.
optimalCssSizehttps://www.antikeo.com/assets/css/style-1.6.min.css?185 size is 43.8 kB (43758) and that is bigger than the limit of 25 kB. Try to keep each CSS response under 25 kB.
Render-blocking CSS holds up the first paint until it has fully downloaded, parsed and applied, so smaller CSS files mean a faster start. Split your CSS into a small critical bundle inlined or eagerly loaded, with the rest lazy-loaded.
| URL | Transfer | Content |
|---|---|---|
| https://www.antikeo.com/assets/css/style-1.6.min.css?185 | 42.7 KB | 172.2 KB |
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.
mimeTypesThe page has 1 misconfigured mime type.
It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk.
thirdPartyThe page do more requests to third party domains (51 requests and 1.8 MB) then first party (31 requests and 1.5 MB). The page transfer more bytes from third party domains (1.8 MB) then first party (1.5 MB). The regex .*antikeo.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
unnecessaryHeadersThere are 2 responses that sets a p3p header. There are 58 responses that sets both a max-age and expires header. There are 13 responses that sets a pragma no-cache header (that is a request header). There are 3 responses that sets a x-frame-options:sameorigin header. There are 64 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.
metaDescriptionThe meta description is too long. It has 171 characters, the recommended max is 160
Use a page description to make the page more relevant to search engines.
pageTitleThe title is too long by 2 characters. The recommended max is 60
Use a title to make the page more relevant to search engines.
viewportThe viewport meta tag sets maximum-scale to 1 or less, which prevents the user from zooming in. Remove it.
The viewport meta tag tells the browser how to lay out the page on small screens. Without it (or without width=device-width) the page is rendered at a desktop fallback width and scaled down, which makes text unreadable on mobile. Disabling zoom (user-scalable=no, maximum-scale<=1) is also an accessibility regression. https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag
longHeadershttps://www.google.c...ng/merchantverse/ has a header content-security-policy that is 1349 characters long. https://connect.face...en_US/fbevents.js has a header content-security-policy that is 1410 characters long. https://connect.face...en_US/fbevents.js has a header permissions-policy that is 874 characters long. https://connect.face...g/781787612411430 has a header content-security-policy that is 1344 characters long. https://connect.face...g/781787612411430 has a header permissions-policy that is 874 characters long.
Do not send response headers that are too long.
iframeSandboxThe page embeds 2 cross-origin iframes without a sandbox attribute. Add sandbox="" with the minimum set of allow-* tokens the embed actually needs.
Adding a sandbox attribute to a cross-origin iframe restricts what the embedded page can do (script execution, form submission, top-level navigation, popups, etc.) and is one of the cheapest ways to limit the blast radius of a third-party embed. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#sandbox
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
sessionReplayThe page loads 2 session-replay scripts. Confirm input redaction is enabled, that you have explicit user consent before recording starts, and that the data-retention and storage location of the recordings match your privacy policy.
Session-replay tools (Hotjar, FullStory, Microsoft Clarity, LogRocket, Smartlook, Mouseflow and similar) record user behaviour on the page in detail. They have legitimate uses but they have also been shown to capture personally-identifiable information from form fields when not configured with redaction. If you use one of these, make sure input redaction is on, that you have explicit user consent under the relevant regulation (GDPR, CCPA, etc.) before recording starts, and that you know where the recordings are stored and for how long. https://www.princeton.edu/~jmayer/papers/Acar2018.pdf
surveillanceThe page embeds 10 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
nelHeaderSet a NEL header (paired with Reporting-Endpoints) to collect connection-level error reports from the field.
The NEL (Network Error Logging) response header tells the browser to record connection-level failures (DNS, TLS, HTTP errors) and ship them to a reporting endpoint. NEL pairs with the Reporting-Endpoints / Report-To header — the page declares the endpoint group and NEL points at it. Together they give you visibility into errors that never reach your origin server. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/NEL
reportingEndpointsHeaderSet a Reporting-Endpoints header (or the legacy Report-To header) so CSP reports, NEL data and other Reporting-API events have an endpoint to land at.
The Reporting-Endpoints response header (the successor to Report-To) names the URLs that browsers should POST reports to. Without it, CSP report-to directives, Cross-Origin-Opener-Policy reports, NEL data and other Reporting-API events have nowhere to go. The legacy Report-To header is still accepted for older Chromium versions. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Reporting-Endpoints
strictTransportSecurityHeaderSet a strict transport header to make sure the user always use HTTPS.
The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security.
thirdPartyPrivacyThe page has 56% requests that are 3rd party (46 requests with a size of 1.8 MB). 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 24 survelliance requests and uses 4 survelliance tools. The page do 26 surveillance requests and uses 5 surveillance tools. The page do 16 utility requests and uses 3 utility tools. The page do 4 tag-manager requests and uses 1 tag-manager tool. The page do 10 social requests and uses 2 social tools. The page do 2 ad requests and uses 1 ad 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.
thirdPartyCookiesThe page sets 3 third party cookies.
Third party cookies are used to track the user. They are automatically blocked in Safari and Firefox.
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.
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.
0.0s0.7s1.0s1.4s1.8s2.2s2.5s2.9sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div:eq(4) > div > div > div > div#main-slider > div > div > div > a > div > div > div:eq(1)
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.
The Largest Contentful Paint API matched this image:
How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.
One shift is 85% of your 0.041 CLS. div:eq(0) moved at 556 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 > div:eq(4) > div > div > div > div#main-slider > div > div > div > a > div > div > div:eq(0)body > header#header > div:eq(1) > div > div:eq(0) > div:eq(0) > div > div > div > div > div:eq(2)body > div:eq(4) > div > div > div > div#main-slider > div > div > div > a > div > div > div:eq(0) > div > buttonbody > header#header > div:eq(1) > div > div:eq(0) > div:eq(0) > div > div > div > div > div:eq(1) > form#form_validate_search > div > button
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.
| Header | Value |
|---|---|
access-control-allow-origin | * |
cache-control | public, max-age=60, s-maxage=60 |
content-encoding | gzip |
content-security-policy | frame-ancestors 'self' https://www.antikeo.de; object-src 'none'; |
content-type | text/html; charset=UTF-8 |
date | Thu, 01 Oct 2026 01:39:06 GMT |
expires | Thu, 19 Nov 1981 08:52:00 GMT |
permissions-policy | microphone=(), camera=(), fullscreen=(self) |
pragma | no-cache |
referrer-policy | no-referrer-when-downgrade |
server | nginx |
vary | Accept-Encoding |
x-content-type-options | nosniff |
x-frame-options | sameorigin |
Transfer size3.1 MB
Content size7.0 MB
Requests81
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 63.6 KB | 447.7 KB | 5 |
| css | 0 b | 87.6 KB | 481.7 KB | 11 |
| javascript | 273 B | 1.4 MB | 4.6 MB | 28 |
| image | 0 b | 1.0 MB | 1.0 MB | 12 |
| font | 0 b | 482.8 KB | 481.0 KB | 13 |
| favicon | 0 b | 14.9 KB | 14.7 KB | 1 |
| other | 0 b | 896 B | 461 B | 1 |
| json | 0 b | 1.0 KB | 651 B | 2 |
| plain | 837 B | 825 B | 0 b | 8 |
| Total | 1.1 KB | 3.1 MB | 7.0 MB | 81 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.antikeo.com | 4.360 s | 1.4 MB | 2.3 MB | 31 |
| fonts.googleapis.com | 72 ms | 2.1 KB | 10.7 KB | 2 |
| cdnjs.cloudflare.com | 194 ms | 2.9 KB | 5.9 KB | 1 |
| apis.google.com | 792 ms | 161.1 KB | 463.7 KB | 6 |
| www.googletagmanager.com | 2.668 s | 537.3 KB | 1.6 MB | 4 |
| use.typekit.net | 86 ms | 73.0 KB | 72.3 KB | 3 |
| fonts.gstatic.com | 759 ms | 329.7 KB | 329.5 KB | 5 |
| www.google.com | 235 ms | 10.2 KB | 61.1 KB | 3 |
| www.gstatic.com | 734 ms | 289.8 KB | 887.5 KB | 3 |
| accounts.google.com | 26 ms | N/A | 0 b | 1 |
| cdn.cookie-script.com | 407 ms | 38.5 KB | 228.0 KB | 1 |
| s.pinimg.com | 217 ms | 39.7 KB | 162.7 KB | 2 |
| ct.pinterest.com | 1.581 s | 4.4 KB | 5.2 KB | 6 |
| bat.bing.com | 788 ms | 17.6 KB | 59.4 KB | 2 |
| connect.facebook.net | 1.654 s | 203.0 KB | 794.4 KB | 2 |
| www.clarity.ms | 69 ms | 1.1 KB | 1.1 KB | 1 |
| bat.bing.net | 187 ms | 825 B | 0 b | 5 |
| scripts.clarity.ms | 24 ms | 25.4 KB | 73.3 KB | 1 |
| z.clarity.ms | 947 ms | 0 b | 0 b | 3 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 4 weeks | 1 year |
| Last modified | 0 seconds | 26 weeks | 7 years |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 705 B | 2 |
| css | 0 b | 0 |
| javascript | 247.0 KB | 6 |
| image | 107.5 KB | 4 |
| font | 49.3 KB | 3 |
| favicon | 14.9 KB | 1 |
| plain | 825 B | 8 |
| Total | 420.1 KB | 24 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 705 B | 3 |
| css | 0 b | 0 |
| javascript | 774.6 KB | 15 |
| image | 266.0 KB | 7 |
| font | 298.9 KB | 5 |
| favicon | 14.9 KB | 1 |
| json | 1.0 KB | 2 |
| plain | 825 B | 8 |
| Total | 1.3 MB | 41 |
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 |
|---|---|---|---|---|---|
| fbevents.js | 1 | 111.4 ms | 61.5 ms | – | script tag |
| js | 1 | 112.5 ms | 56.6 ms | – | script tag |
| js | 1 | 96.4 ms | 47.8 ms | – | script tag |
| www.antikeo.com | 1 | 85.1 ms | 41 ms | 66.7 ms | script tag |
| clarity.js | 1 | 71.4 ms | 21.9 ms | 0.8 ms | script tag |
| gtm.js | 1 | 70.1 ms | 21 ms | – | script tag |
| cb=gapi.loaded_0 | 1 | 53.1 ms | 7.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.
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 |
|---|---|---|---|---|---|
od in https://www.googletagmanager.com/gtm.js?id=GTM-PGPNSX6:276 | 0 ms | once | 66 | 66 | 88.0 ms |
e in https://www.gstatic.com/_/mss/boq-shopping-merchant-standards/_/js/k=boq-shoppin...ebZ3mb/dti=1/m=_b:184 | 0 ms | once | 7 | 13 | 76.1 ms |
| https://www.antikeo.com/assets/js/plugins-1.6.js?v=20260908a:8 | 0 ms | once | 20 | 19 | 26.2 ms |
| https://www.googletagmanager.com/gtm.js?id=GTM-PGPNSX6:1011 | 2500 ms | once | 1 | 1 | 26.2 ms |
yi in https://cdn.cookie-script.com/s/a4f242d5bd003c3c50738127f3f6c4c6.js:73 | 0 ms | once | 1 | 1 | 19.1 ms |
| https://www.antikeo.com/assets/js/jquery-3.7.1.min.js:2 | 0 ms | once | 32 | 25 | 18.7 ms |
Gn in https://scripts.clarity.ms/0.8.70/clarity.js:2 | 100 ms | once | 2 | 2 | 12.5 ms |
od in https://www.googletagmanager.com/gtag/js?id=G-2NB4BK7JZ8&cx=c>m=4e69t1:331 | 0 ms | once | 36 | 36 | 10.0 ms |
e in https://www.gstatic.com/_/mss/boq-shopping-merchant-standards/_/js/k=boq-shoppin...ebZ3mb/dti=1/m=_b:184 | 2500 ms | once | 1 | 2 | 7.8 ms |
UET.checkuetHostdocumentload in https://bat.bing.com/bat.js:1 | 500 ms | once | 1 | 1 | 7.6 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 antikeo.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.
color6×font-weight4×padding-left4×padding-right4×padding-top4×font-size4×border-bottom-left-radius4×border-bottom-right-radius4×padding-bottom4×visibility1×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 category72
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 size3.1 MB
Content size7.0 MB
Requests82
Calculated using .*antikeo.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 52.9 KB | 386.3 KB | 1 |
| css | 0 b | 85.5 KB | 471.0 KB | 9 |
| javascript | 0 b | 116.4 KB | 371.8 KB | 6 |
| image | 0 b | 1.0 MB | 1.0 MB | 8 |
| font | 0 b | 80.1 KB | 79.2 KB | 5 |
| favicon | 0 b | 14.9 KB | 14.7 KB | 1 |
| other | 0 b | 896 B | 461 B | 1 |
| Total | N/A | 1.4 MB | 2.3 MB | 31 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 10.7 KB | 61.4 KB | 4 |
| css | 0 b | 2.1 KB | 10.7 KB | 2 |
| javascript | 273 B | 1.3 MB | 4.2 MB | 22 |
| image | 0 b | 583 B | 148 B | 4 |
| font | 0 b | 402.7 KB | 401.8 KB | 8 |
| favicon | 0 b | 0 b | 0 b | 0 |
| json | 0 b | 1.0 KB | 651 B | 2 |
| plain | 837 B | 825 B | 0 b | 8 |
| Total | 1.0 KB | 1.7 MB | 4.7 MB | 51 |
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.
6 accessibility rules failed, affecting 66 elements.
Start with the 2 serious issues.
color-contrastEnsure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds
Read the axe-core docs for this rule →
Fix any of the following: Element has insufficient color contrast of 2.31 (foreground color: #ffffff, background color: #cfa364, font size: 48.0pt (64px), font weight: normal). Expected contrast ratio of 3:1
<p class="title-slider_114 title" data-animation="fadeInUp" data-delay="0.1s" style="margin-bottom: 0px; color: rgb(255, 255, 255); animation-delay: 0.1s;">Couleurs d'automne</p><button class="btn btn-slider" data-animation="fadeInUp" data-delay="0.9s" style="margin-top: 20px; background-color: rgb(207, 163, 100); border-color: rgb(255, 255, 255); color: rgb(255, 255, 255); animation-delay: 0.9s;" tabindex="0">DÉCOUVREZ NOTRE SÉLECTION</button><div class="category-highlight-text">Explorez nos catégories plébiscitées par nos internautes</div><h3 class="featured-category-title">Mobilier</h3><h3 class="featured-category-title">Peinture</h3><h3 class="featured-category-title">Sculptures</h3><h3 class="featured-category-title">Objets de collection</h3><p class="title-exp">Les objets sélectionnés par nos experts</p><a href="https://www.antikeo.com/galerie/maison-bananas">
Galerie MAISON BANANAS </a><a href="https://www.antikeo.com/galerie/galerie-lauretta">
Galerie GALERIE LAURETTA </a><a href="https://www.antikeo.com/galerie/galerie-terrain-vague">
Galerie Terrain Vague </a><a href="https://www.antikeo.com/galerie/artisan-du-bois">
Galerie Stephane Cailteux </a><a href="https://www.antikeo.com/galerie/jean-luc-ferrand-antiquites">
Galerie Jean-Luc Ferrand Antiquités </a><a href="https://www.antikeo.com/galerie/galerie-pellat-de-villedon">
Galerie Pellat de Villedon </a><a href="https://www.antikeo.com/galerie/galerie-nicolas-vanneste">
Galerie Nicolas Vanneste </a><a href="https://www.antikeo.com/galerie/galerie-cerca-trova">
Galerie GALERIE CERCA TROVA </a><a href="https://www.antikeo.com/galerie/atypique">
Galerie Atypique </a><a href="https://www.antikeo.com/galerie/nando-antiques">
Galerie Nando Antiques </a><a href="https://www.antikeo.com/galerie/joaillerie-landauer">
Galerie JOAILLERIE LANDAUER </a><del class="discount-original-price">
5.500 <span>€</span> </del><a href="https://www.antikeo.com/galerie/chastelain-butes">
Galerie Chastelain & Butes </a><a href="https://www.antikeo.com/galerie/une-autre-epoque">
Galerie Une Autre Epoque </a><a href="https://www.antikeo.com/galerie/maison-mohs">
Galerie Maison Mohs - Bijoux anciens et vintage </a><a href="https://www.antikeo.com/galerie/miroir-du-temps">
Galerie Miroir du temps </a><a href="https://www.antikeo.com/galerie/alain-michel-antiquite">
Galerie Alain Michel Antiquité </a><p class="title-exp">Notre galerie à l'honneur cette semaine</p><p class="title-exp">Actualités et reportages sur les Beaux Arts et les Arts Décoratifs</p>frame-titleEnsure <iframe> and <frame> elements have an accessible name
Read the axe-core docs for this rule →
Fix any of the following: Element has no title attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element's default semantics were not overridden with role="none" or role="presentation"
<iframe ng-non-bindable="" frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" style="position: static; to..." tabindex="0" vspace="0" width="100%" id="I0_1790818747366" name="I0_1790818747366" src="https://www.google.c..." allowfullscreen="" data-gapiattached="true">heading-orderEnsure the order of headings is semantically correct
Read the axe-core docs for this rule →
Fix any of the following: Heading order invalid
<h3 class="featured-category-title">Mobilier</h3>meta-viewportEnsure <meta name="viewport"> does not disable text scaling and zooming
Read the axe-core docs for this rule →
Fix any of the following: maximum-scale on <meta> tag disables zooming on mobile devices
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, shrink-to-fit=no">regionEnsure all page content is contained by landmarks
Read the axe-core docs for this rule →
Fix any of the following: Some page content is not contained by landmarks
<p class="title-slider_114 title" data-animation="fadeInUp" data-delay="0.1s" style="margin-bottom: 0px; color: rgb(255, 255, 255); animation-delay: 0.1s;">Couleurs d'automne</p><p class="description" data-animation="fadeInUp" data-delay="0.5s" style="color: rgb(255, 255, 255); animation-delay: 0.5s;">Antikeo célèbre l’automne en palette de bruns, ocres et ors, pour un art de vivre raffiné et inspirant.</p><div class="row justify-content-between"><div class="index-wrapper" style="background-color: #f3f6f9"><h2 class="title">Explorer par</h2><p class="title-exp">Navigation et découverte par thématique</p><div class="row featured-filters justify-content-between"><h2 class="title">Galerie à la une</h2><p class="title-exp">Notre galerie à l'honneur cette semaine</p><div class="col-xs-12 col-md-6 order-0" style="background-image: url('https://www.antikeo.com//uploads/profile/img_623deec82bdb10-28427596-90920670.jpg'); background-size: cover"><a href="https://www.antikeo.com/catalogue/peinture/peintures-marines/marine-dun-port-corse-signee-francois-corbellini-1863-1943-81769"><img src="data:image/svg+xml,%..." data-src="https://www.antikeo...." alt="Marine d’un port cor..." class="lazyload img-fluid i..." style="border-radius: 2px"><a href="https://www.antikeo.com/catalogue/argenterie-et-orfevrerie/pieces-de-forme-argenterie-et-orfevrerie/paire-daiguieres-en-argent-massif-xixe-siecle-78732"><img src="data:image/svg+xml,%..." data-src="https://www.antikeo...." alt="Paire d’aiguières en..." class="lazyload img-fluid i..." style="border-radius: 2px"><a href="https://www.antikeo.com/catalogue/peinture/peintures-paysages/hubert-aicardi-1922-1991-les-falaises-de-piana-huile-sur-toile-datee-de-1964-78161"><img src="data:image/svg+xml,%..." data-src="https://www.antikeo...." alt="Hubert Aicardi (1922..." class="lazyload img-fluid i..." style="border-radius: 2px"><a href="https://www.antikeo.com/catalogue/sculptures/sculptures-bronzes/paire-de-musiciens-en-bronze-sur-un-socle-en-lapis-lazuli-xixe-siecle-78671"><img src="data:image/svg+xml,%..." data-src="https://www.antikeo...." alt="Paire de musiciens e..." class="lazyload img-fluid i..." style="border-radius: 2px"><div class="col-12 col-md-6 mt-3 mt-md-4 p-3 p-md-0 justify-content-center order-1 order-md-2"><div class="col-12 col-md-5 mt-4 mt-md-4 justify-content-center order-3 d-flex align-items-center">
<a onclick="window.location.href='https://www.antikeo.com/galerie/pipat-antiquites'" class="btn btn-outline-gray btn-vendor-ad cursor-pointer bg-white">Voir la Galerie</a>
</div><div class="index-wrapper"><a href="/magazine"><h2 class="title">Le magazine Antikeo</h2></a><p class="title-exp">Actualités et reportages sur les Beaux Arts et les Arts Décoratifs</p><div id="blog-slider" class="blog-slider"><div class="title">La garantie Acheteur sur Antikeo</div><p class="title-exp">4 engagements pour acheter en toute confiance</p><div class="row marg-top-60"><div class="container section who-are-we text-justify mt-5">image-redundant-altEnsure image alternative is not repeated as text
Read the axe-core docs for this rule →
Fix all of the following: Element contains <img> element with alt text that duplicates existing text
<img src="data:image/svg+xml;b..." class="flag" alt="Français"><img class="featured-category-image lazyloaded" src="https://www.antikeo.com/uploads/category/mobilier_school.png" data-src="https://www.antikeo.com/uploads/category/mobilier_school.png" alt="Mobilier"><img class="featured-category-image lazyloaded" src="https://www.antikeo.com/uploads/category/peinture_school.png" data-src="https://www.antikeo.com/uploads/category/peinture_school.png" alt="Peinture"><img class="featured-category-image lazyloaded" src="https://www.antikeo.com/uploads/category/sculpture_school.png" data-src="https://www.antikeo.com/uploads/category/sculpture_school.png" alt="Sculptures"><img class="featured-category-image lazyloaded" src="https://www.antikeo.com/uploads/category/objet_decoration_school.png" data-src="https://www.antikeo.com/uploads/category/objet_decoration_school.png" alt="Objets de collection"><img class="lazyload" src="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 200 200'%3E%3C/svg%3E" data-src="https://www.antikeo.com/uploads/homepage/img_6a9af78ba97a79-96337585-99700125.jpg" alt="Matériaux"><img class="lazyload" src="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 200 200'%3E%3C/svg%3E" data-src="https://www.antikeo.com/assets/img/shopby/style4.jpg" alt="Style"><img class="lazyload" src="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 200 200'%3E%3C/svg%3E" data-src="https://www.antikeo.com/assets/img/shopby/origine4.jpg" alt="Pays d'origine">