Page summary

https://www.anticstore.com/i

Tested 2025-02-25 02:40:48 using Chrome 132.0.6834.83 (runtime settings).

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

Summary

MetricValue
Page metrics
Performance Score88
Total Page Transfer Size548.2 KB
Requests23
Timing metrics
TTFB [median]34 ms
First Paint [median]147 ms
Fully Loaded [median]511 ms
Google Web Vitals
TTFB [median]34 ms
First Contentful Paint (FCP) [median]147 ms
Largest Contentful Paint (LCP) [median]147 ms
Cumulative Layout Shift (CLS) [median]0.03
Total Blocking Time [median]58 ms
Max Potential FID [median]81 ms
CPU metrics
CPU long tasks [median]3
CPU longest task duration85 ms
CPU last long task happens at429 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
Screenshot of run 2

Timings Summary

Metricminmedianmeanmax
Visual Metrics
FirstVisualChange167 ms167 ms256 ms434 ms
LastVisualChange233 ms234 ms322 ms500 ms
SpeedIndex174 ms174 ms263 ms441 ms
LargestImage233 ms234 ms322 ms500 ms
Heading233 ms234 ms322 ms500 ms
LargestContentfulPaint233 ms234 ms322 ms500 ms
LastMeaningfulPaint233 ms234 ms322 ms500 ms
VisualReadiness66 ms66 ms66 ms67 ms
VisualComplete85167 ms167 ms256 ms434 ms
VisualComplete95233 ms234 ms322 ms500 ms
VisualComplete99233 ms234 ms322 ms500 ms
Google Web Vitals
Time To First Byte (TTFB)33 ms34 ms122 ms300 ms
Largest Contentful Paint (LCP)144 ms147 ms234 ms410 ms
First Contentful Paint (FCP)144 ms147 ms234 ms410 ms
Cumulative Layout Shift (CLS)0.01380.02680.02680.0398
More metrics
firstPaint144 ms147 ms234 ms410 ms
loadEventEnd175 ms176 ms265 ms443 ms
CPU
Total Blocking Time47 ms58 ms55 ms59 ms
Max Potential FID77 ms81 ms81 ms85 ms
CPU long tasks 3333
CPU last long task happens at413 ms429 ms513 ms697 ms
| Waterfall | | Download HAR | 

Waterfall

Run 2 SpeedIndex median

| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
0.2 sLayout Shift 0.03895 120 msFirst Contentful Paint 144 msLCP <IMG> 144 msDOM Content Loaded Time 164 msFirst Visual Change 167 msVisual Complete 85% 167 msPage Load Time 174 msLayout Shift 0.00086 177 ms
0.3 sLast Visual Change 234 msVisual Complete 95% 234 msVisual Complete 99% 234 msLargest Image 234 msHeading 234 msCPU Long Task duration 56 ms
| Performance advice | Best practice advice | Privacy advice | Page info | Technologies | 

Coach

The coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices. Tested using Coach-core version 8.1.1.

I am the coach

Coach score

Performance advice (88)

TitleAdviceScore
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-189
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 3 CPU long tasks with the total of 197 ms. The total blocking time is 47 ms . However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks.40
    Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler.
    Offenders:
  • self
  • self
  • self
  • 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-29.jpg
  • https://www.anticstore.com/img/acc/mobilier-1.jpg
  • https://www.anticstore.com/img/acc/peinture-4.jpg
  • https://www.anticstore.com/img/acc/sculpture-2.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&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.anticstore.com/img/favicon.ico
  • https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&l=dataLayer&cx=c&gtm=457e52o0za200
  • 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 414.2 kB and the uncompressed size is 1.2 MB. This is totally crazy! There is really room for improvement here. 0
    Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?
    Offenders:
    URLTransfer sizeContent size
    https://www.googletagmanager.com/gtag/js?id=UA-96091873-1 88.3 KB247.6 KB
    https://www.anticstore.com/js/js-V2-min.js 3.3 KB16.9 KB
    https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&l=dataLayer&cx=c&gtm=457e52o0za200 100.9 KB288.4 KB
    https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za200 87.6 KB247.1 KB
    https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&l=dataLayer&cx=c&gtm=457e52o0za200 103.3 KB298.8 KB
    https://www.google-analytics.com/analytics.js 21.1 KB51.7 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&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&l=dataLayer&cx=c&gtm=457e52o0za200
  • 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)

    TitleAdviceScore
    Avoid too many third party requests (thirdParty)The page do 35% requests to third party domains (8 requests and 411.3 kB). First party is 15 requests and 150.1 kB. The page transfer more bytes from third party domains (411.3 kB) then first party (150.1 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 23 responses that sets both a max-age and expires header. There are 4 responses that sets a pragma no-cache header (that is a request header). There are 8 responses that sets a server header. 65
    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-29.jpg
  • https://www.anticstore.com/img/acc/mobilier-1.jpg
  • https://www.anticstore.com/img/acc/peinture-4.jpg
  • https://www.anticstore.com/img/acc/sculpture-2.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&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za200
  • 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&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.google-analytics.com/analytics.js
  • https://www.google-analytics.com/analytics.js
  • https://www.google-analytics.com/j/collect...ics.com/j/collect
  • https://www.google-analytics.com/j/collect...ics.com/j/collect
  • https://www.google-analytics.com/j/collect...ics.com/j/collect
  • 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)

    TitleAdviceScore
    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 35% requests that are 3rd party (8 requests with a size of 411.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 4 tag-manager requests and uses 1 tag-manager tool. The page do 8 survelliance requests and uses 2 survelliance tools. The page do 4 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&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://region1.google-analytics.com/g/collect...ics.com/g/collect
  • https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&l=dataLayer&cx=c&gtm=457e52o0za200
  • https://www.google-analytics.com/analytics.js
  • https://www.google-analytics.com/j/collect...ics.com/j/collect
  • https://region1.google-analytics.com/g/collect...ics.com/g/collect
  • Page info

    Page info
    TitleErreur 404 : document non trouvé
    Width1350
    Height1211
    DOM elements184
    Avg DOM depth6
    Max DOM depth8
    Iframes0
    Script tags8
    Local storage0 b
    Session storage0 b
    Network Information API4g

    Technologies used to build the page.

    Data collected using Wappalyzer version 6.10.66. With updated code from Webappanalyzer 2024-12-27. Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyzer find more information about technologies used.

    TechnologyConfidenceCategory
    PHP 7.2100  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
    | Browser metrics | Visual Metrics | Largest Contentful Paint | Cumulative Layout Shift | Long Aninimation Frames | Visual Elements | 

    Data from run 2

    Visual Metrics

    Browser Metrics

    Google Web Vitals
    Time to first byte (TTFB)34 ms
    First Contentful Paint (FCP)144 ms
    Largest Contentful Paint (LCP)144 ms
    Cumulative Layout Shift (CLS)0.04
    Total Blocking Time (TBT)58 ms
    First Contentful Paint info
    Elements that needed recalculate style before FCP218
    Time spent in recalculate style before FCP9.917 ms
    Extra timings
    TTFB34 ms
    First Paint144 ms
    Load Event End176 ms
    Fully loaded507 ms

    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 typeIMG
    Element/tag<img src="/img/acc/objet-art-28.jpg" width="230" alt="Objet d'art">
    Render time 144 ms
    Element render delay83 ms
    TTFB34 ms
    Resource delay9 ms
    Resource load duration18 ms
    Elements that needed recalculate style before LCP218
    Time spent in recalculate style before LCP9.917 ms
    Load time79 ms
    URL https://www.anticsto.../objet-art-28.jpg
    Size (width*height)51076
    DOM path
    div#page > div:eq(1) > a > img> div#page > div:eq(1) > a > img>
    LCP

    The largest contentful paint is highlighted in the image. If no element is highlighted the element was removed before the screenshot or the LCP API couldn't find the element.

    The Largest Contentful Paint API highlighted this image as a part of the LCP.

    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.

    ScoreHTML 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)
    Layout shift

    The elements that have shifted place is highlighted in the image (that have a higher value than 0.01). If the element shifted outside of the viewport, you will not see it there. It can be hard to understand what content that has shifted, if that's the case, checkout the video or the filmstrip of the run.

    Long Animation Frames

    Read more about the Long Animation Frames API here here.

    The top 10 longest animation frames entries

    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    35 ms85 ms0 ms0 ms0 ms
    https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&l=dataLayer&cx=c&gtm=457e52o0za200

    Invoker:  https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&l=dataLayer&cx=c&gtm=457e52o0za200
    Invoker Type: classic-script
    Window attribution: self

    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    17 ms67 ms0 ms0 ms0 ms
    https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&l=dataLayer&cx=c&gtm=457e52o0za200

    Invoker:  https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&l=dataLayer&cx=c&gtm=457e52o0za200
    Invoker Type: classic-script
    Window attribution: self

    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    6 ms56 ms0 ms0 ms0 ms
    https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za200

    Invoker:  https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za200
    Invoker Type: classic-script
    Window attribution: self

    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    0 ms35.5 ms38.5 ms0 ms38.5 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    0 ms56.2 ms2.8 ms0.7 ms2.1 ms
    https://www.googletagmanager.com/gtag/js?id=UA-96091873-1

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

    Server timings

    There are no Server Timings.

    Custom metrics collected through JavaScript

    There are no custom configured scripts.

    Extra metrics collected using scripting

    There are no custom extra metrics from scripting.

    Visual Elements

    NameDisplay TimeX YWidthHeight
    LargestImage (objet-art-28.jpg)234 ms 76 302 226 226
    <img src="/img/acc/objet-art-28.jpg" width="230" alt="Objet d'art">
    Heading234 ms 75 170 1200 35
    <h1></h1>
    LargestContentfulPaint (objet-art-28.jpg)234 ms 76 302 226 226
    <img src="/img/acc/objet-art-28.jpg" width="230" alt="Objet d'art">
    | Summary  | Largest responses  | Requests and sizes per content type  | Data per domain | Expires and last modified statistics  | Requests loaded after onLoad event  | Render blocking requests  | 

    PageXray

    How the page is built.

    Summary
    HTTP versionHTTP/2.0
    Total requests23
    Total domains4
    Total transfer size548.2 KB
    Total content size1.3 MB
    Responses missing compression8
    Number of cookies1
    Third party cookies0
    Requests per response code
    20020
    2042
    4041

    Largest assets on the page (by transfer size)

    Requests and sizes per content type

    ContentHeader SizeTransfer SizeContent SizeRequests
    css0 b8.7 KB41.7 KB1
    javascript0 b404.5 KB1.1 MB6
    image0 b68.1 KB67.0 KB7
    font0 b62.6 KB61.2 KB4
    favicon0 b632 B1.1 KB1
    plain0 b452 B1 B3
    Total0 b545.0 KB1.3 MB22

    Data per domain

    DomainTotal download timeTransfer SizeContent SizeRequests
    www.anticstore.com526 ms146.6 KB198.6 KB15
    www.googletagmanager.com124 ms380.1 KB1.1 MB4
    region1.google-analytics.com83 msN/A0 b2
    www.google-analytics.com41 ms21.5 KB51.7 KB2

    Expires and last modified statistics

    typeminmedianmax
    Expires0 seconds1 week1 year
    Last modified2 hours7 years27 years

    Requests loaded after onLoad event

    Included requests done after load event end.

    ContentTransfer SizeRequests
    html0 b0
    css0 b0
    javascript312.9 KB4
    image0 b0
    font0 b0
    favicon632 B1
    plain452 B3
    Total314.0 KB8

    Requests loaded after onContentLoad

    Includes requests done after DOM content loaded.

    ContentTransfer SizeRequests
    html0 b0
    css0 b0
    javascript312.9 KB4
    image0 b0
    font0 b0
    favicon632 B1
    plain452 B3
    Total314.0 KB8

    Render blocking requests

    Render blocking information directly from Chrome.

    BlockingIn body parser blockingPotentially blocking
    111

    Render information

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

    CPU

    Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.

    Long Tasks

    Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.

    TypeQuantityTotal duration (ms)
    Total Blocking Time 58
    Max Potential First Input Delay 85
    Long Tasks before First Paint00
    Long Tasks before First Contentful Paint00
    Long Tasks before Largest Contentful Paint00
    Long Tasks after Load Event End3208
    Total Long Tasks3208

    CPU last long task happened at 413 ms

    Individual Long Tasks

    namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
    self24456window
    self30667window
    self41385window

    CPU time spent

    Calculated using Tracium.

    Categories (ms)
    parseHTML10
    styleLayout46
    paintCompositeRender3
    scriptParseCompile0
    scriptEvaluation327
    garbageCollection4
    other68
    Events (ms)
    v8.run260
    RunTask55
    FunctionCall34
    Layout33
    RunMicrotasks18
    UpdateLayoutTree11

    Time spent per request

    URLCPU time (ms)
    https://www.googletagmanager.com/gtag/js?id=G-VQNNWGZM60&l=dataLayer&cx=c&gtm=457e52o0za20087
    https://www.googletagmanager.com/gtag/js?id=UA-96091873-171
    https://www.googletagmanager.com/gtag/js?id=G-W9PRST2HXV&l=dataLayer&cx=c&gtm=457e52o0za20069
    https://www.googletagmanager.com/gtag/js?id=UA-17384304-1&l=dataLayer&cx=c&gtm=457e52o0za20059
    https://www.google-analytics.com/analytics.js21

    CPU time spent

    Tool/domainTime (ms)
    Google Tag Manager285.7
    Google Analytics20.8
    | Categories | | Tools | | First vs third | 

    Third party

    Third party requests categorised by Third party web version 0.26.2.

    CategoryRequests
    tag-manager 4
    survelliance 8
    analytics 4
    CategoryNumber of tools
    tag-manager 1
    survelliance 2
    analytics 1

    Third party requests and tools

    tag-manager (4 requests)
    Google Tag Manager
    survelliance (8 requests)
    Google Tag Manager
    Google Analytics
    analytics (4 requests)
    Google Analytics

    First party requests and sizes per content type

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

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b0 b0 b0
    css0 b8.7 KB41.7 KB1
    javascript0 b3.3 KB16.9 KB1
    image0 b68.1 KB67.0 KB7
    font0 b62.6 KB61.2 KB4
    favicon0 b632 B1.1 KB1
    TotalN/A146.6 KB198.6 KB15

    Third party requests and sizes per content type

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b0 b0 b0
    css0 b0 b0 b0
    javascript0 b401.2 KB1.1 MB5
    image0 b0 b0 b0
    font0 b0 b0 b0
    plain0 b452 B1 B3
    TotalN/A401.7 KB1.1 MB8

    Axe

    Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Tested using axe-core version 4.10.2. Read more about axe-core .

    Violations

    Median number of violations for all the runs. Check each individual run to see all the violations.

    TypeViolations (median)
    Critical 1 (1 issues)
    Serious2 (17 issues)
    Moderate2 (11 issues)
    Minor1 (2 issues)