Tested 2025-09-29 01:33:31 using Chrome 132.0.6834.83 (runtime settings).
| Metric | Value |
|---|---|
| Page metrics | |
| Performance Score | 76 |
| Total Page Transfer Size | 2.2 MB |
| Requests | 42 |
| Timing metrics | |
| TTFB [median] | 211 ms |
| First Paint [median] | 354 ms |
| Fully Loaded [median] | 1.205 s |
| Google Web Vitals | |
| TTFB [median] | 211 ms |
| First Contentful Paint (FCP) [median] | 354 ms |
| Largest Contentful Paint (LCP) [median] | 813 ms |
| Cumulative Layout Shift (CLS) [median] | 0.00 |
| Interaction To Next Paint (INP) [median] | 120 ms |
| Total Blocking Time [median] | 169 ms |
| Max Potential FID [median] | 142 ms |
| CPU metrics | |
| CPU long tasks [median] | 6 |
| CPU longest task duration | 371 ms |
| CPU last long task happens at | 996 ms |
| Visual Metrics | |
| First Visual Change [median] | 366 ms |
| Speed Index [median] | 437 ms |
| Visual Complete 85% [median] | 400 ms |
| Visual Complete 99% [median] | 966 ms |
| Last Visual Change [median] | 966 ms |
| Metric | min | median | mean | max |
|---|---|---|---|---|
| Visual Metrics | ||||
| FirstVisualChange | 333 ms | 366 ms | 511 ms | 833 ms |
| LastVisualChange | 833 ms | 966 ms | 1.100 s | 1.500 s |
| SpeedIndex | 401 ms | 437 ms | 565 ms | 858 ms |
| LargestImage | 333 ms | 366 ms | 511 ms | 833 ms |
| Heading | 833 ms | 966 ms | 1.055 s | 1.367 s |
| LargestContentfulPaint | 833 ms | 966 ms | 1.055 s | 1.367 s |
| LastMeaningfulPaint | 833 ms | 966 ms | 1.055 s | 1.367 s |
| VisualReadiness | 500 ms | 600 ms | 589 ms | 667 ms |
| VisualComplete85 | 366 ms | 400 ms | 533 ms | 833 ms |
| VisualComplete95 | 800 ms | 833 ms | 822 ms | 833 ms |
| VisualComplete99 | 833 ms | 966 ms | 1.055 s | 1.367 s |
| Google Web Vitals | ||||
| Time To First Byte (TTFB) | 183 ms | 211 ms | 203 ms | 216 ms |
| Largest Contentful Paint (LCP) | 794 ms | 813 ms | 809 ms | 819 ms |
| First Contentful Paint (FCP) | 329 ms | 354 ms | 501 ms | 819 ms |
| Cumulative Layout Shift (CLS) | 0.0014 | 0.0014 | 0.0019 | 0.0029 |
| More metrics | ||||
| firstPaint | 329 ms | 354 ms | 501 ms | 819 ms |
| loadEventEnd | 1.030 s | 1.093 s | 1.206 s | 1.494 s |
| CPU | ||||
| Total Blocking Time | 126 ms | 169 ms | 175 ms | 230 ms |
| Max Potential FID | 117 ms | 142 ms | 146 ms | 179 ms |
| CPU long tasks | 4 | 6 | 6 | 7 |
| CPU last long task happens at | 933 ms | 996 ms | 1.196 s | 1.660 s |
Run 3 SpeedIndex median
Use--filmstrip.showAll to show all filmstrips.
0 s0.3 sCPU Long Task duration 55 ms
0.4 sFirst Contentful Paint 354 msFirst Visual Change 366 msVisual Complete 85% 366 msLargest Image 366 ms
0.5 sCPU Long Task duration 59 msLayout Shift 0.00076 436 msLayout Shift 0.00004 487 ms
0.6 sCPU Long Task duration 179 ms0.7 sCPU Long Task duration 101 ms
0.9 sLCP <H1> 813 msVisual Complete 95% 833 msCPU Long Task duration 55 ms
1 sLayout Shift 0.00062 932 msCPU Long Task duration 59 msLast Visual Change 966 msVisual Complete 99% 966 msHeading 966 msCPU Long Task duration 77 msThe 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.
| Title | Advice | Score | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Avoid slowing down the critical rendering path (avoidRenderBlocking) | The page has 4 blocking requests and 4 in body parser blocking (4 JavaScript and 4 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR | 59 | ||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| Don't scale images in the browser (avoidScalingImages) | The page has 4 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. | 60 | ||||||||||||||||||||||||
| Description: 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. | ||||||||||||||||||||||||||
| Offenders: | ||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||
| Avoid CPU Long Tasks (longTasks) | The page has 6 CPU long tasks with the total of 906 ms. The total blocking time is 126 ms and 2 long tasks before first contentful paint with total time of 580 ms. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks. | 0 | ||||||||||||||||||||||||
| Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler. | ||||||||||||||||||||||||||
| Offenders: | ||||||||||||||||||||||||||
| Avoid Frontend single point of failures (spof) | The page has 2 requests inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head. | 90 | ||||||||||||||||||||||||
| Description: 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. | ||||||||||||||||||||||||||
| Offenders: | ||||||||||||||||||||||||||
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 2 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 5.3 kB the next access. | 80 | ||||||||||||||||||||||||
| Description: 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. | ||||||||||||||||||||||||||
| Offenders: | ||||||||||||||||||||||||||
| Long cache headers is good (cacheHeadersLong) | The page has 24 requests that have a shorter cache time than 30 days (but still a cache time). | 76 | ||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| Always compress text content (compressAssets) | The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead. | 90 | ||||||||||||||||||||||||
| Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith. | ||||||||||||||||||||||||||
Offenders:
| ||||||||||||||||||||||||||
| Avoid too many fonts (fewFonts) | The page has 11 font requests. Do you really need them? What value does the fonts give the user? | 0 | ||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| Total image size shouldn't be too big (imageSize) | The page total image size is 988.2 kB. 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/. | 50 | ||||||||||||||||||||||||
| Description: 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. | ||||||||||||||||||||||||||
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 346.6 kB and the uncompressed size is 1.1 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:
| ||||||||||||||||||||||||||
| Make each CSS response small (optimalCssSize) | https://www.proantic.com/css/A.sweetalert2-v1-2.css+carrousel-09.css,,q20250703135012+fontawesome.min.css+regular.min.css+thin.min.css+sharp-solid.min.css,Mcc.cM6W6IZUZX.css.pagespeed.cf.Rz1MDGzIXY.css size is 39.5 kB (39528) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 90 | ||||||||||||||||||||||||
| Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier. | ||||||||||||||||||||||||||
Offenders:
| ||||||||||||||||||||||||||
| Total page size shouldn't be too big (pageSize) | The page total transfer size is 2.3 MB, which is more than the coach limit of 2 MB. That is really big and you need to make it smaller. | 0 | ||||||||||||||||||||||||
| Description: Avoid having pages that have a transfer size over the wire of more than 2 MB (desktop) and 1 MB (mobile) because that is really big and will hurt performance and will make the page expensive for the user if she/he pays for the bandwidth. | ||||||||||||||||||||||||||
| Offenders: | ||||||||||||||||||||||||||
| Don't use private headers on static content (privateAssets) | The page has 3 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. | 70 | ||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| Title | Advice | Score |
|---|---|---|
| Set a referrer-policy header to make sure you do not leak user information. (referrerPolicyHeader) | Set a referrer-policy header to make sure you do not leak user information. | 0 |
| Description: Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. https://scotthelme.co.uk/a-new-security-header-referrer-policy/. | ||
| Offenders: | ||
| Do not share user data with third parties. (thirdPartyPrivacy) | The page has 21% requests that are 3rd party (9 requests with a size of 342.8 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 6 survelliance requests and uses 3 survelliance tools. The page do 1 tag-manager request and uses 1 tag-manager tool. The page do 1 marketing request and uses 1 marketing tool. The page do 4 utility requests and uses 1 utility 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: | ||
| Page info | |
|---|---|
| Title | Proantic: Tous les Antiquaires de Proantic |
| Width | 1350 |
| Height | 14638 |
| DOM elements | 7099 |
| Avg DOM depth | 8 |
| Max DOM depth | 12 |
| Iframes | 0 |
| Script tags | 15 |
| Local storage | 0 b |
| Session storage | 0 b |
| Network Information API | 4g |
| Resource Hints |
|---|
| dns-prefetch |
| https://cdn-images.mailchimp.com/ |
| preconnect |
| https://cdn-images.mailchimp.com/ |
Data collected using Wappalyzer version 6.10.66. With updated code from Webappanalyzer 2024-12-27. Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyzer find more information about technologies used.
| Technology | Confidence | Category |
|---|---|---|
| Nginx | 100 | Web servers Reverse proxies |
| Amazon Web Services | 100 | PaaS |
| HSTS | 100 | Security |
| Google PageSpeed 1.13.35.2 | 100 | Caching Web server extensions Performance |
| Cloudflare | 100 | CDN |
| Amazon CloudFront | 100 | CDN |
| HTTP/3 | 100 | Miscellaneous |
Data collected using Third Party Web 0.26.2
| Cdn |
|---|
| Google CDN |
| Cloudflare CDN |
| JSDelivr CDN |
| Survelliance |
| Google CDN |
| Google Tag Manager |
| Other Google APIs/SDKs |
| Tag-manager |
| Google Tag Manager |
| Marketing |
| Mailchimp |
| Utility |
| Other Google APIs/SDKs |
Data from run 3
| Visual Metrics | |
|---|---|
| First Visual Change | 366 ms |
| Speed Index | 437 ms |
| Largest Image | 366 ms |
| Heading | 966 ms |
| LargestContentfulPaint | 966 ms |
| Last Meaningful Paint | 966 ms |
| Largest Contentful Paint | 966 ms |
| Visual Complete 85% | 366 ms |
| Visual Complete 95% | 833 ms |
| Visual Complete 99% | 966 ms |
| Last Visual Change | 966 ms |
| Visual Readiness | 600 ms |
| Navigation Timing | |
|---|---|
| backEndTime | 211 ms |
| domContentLoadedTime | 1.080 s |
| domInteractiveTime | 1.079 s |
| domainLookupTime | 0 ms |
| frontEndTime | 862 ms |
| pageDownloadTime | 13 ms |
| pageLoadTime | 1.086 s |
| redirectionTime | 0 ms |
| serverConnectionTime | 16 ms |
| serverResponseTime | 203 ms |
| Google Web Vitals | |
|---|---|
| Time to first byte (TTFB) | 211 ms |
| First Contentful Paint (FCP) | 354 ms |
| Largest Contentful Paint (LCP) | 813 ms |
| Cumulative Layout Shift (CLS) | 0.00 |
| Interaction to next paint (INP) | 120 ms |
| Total Blocking Time (TBT) | 230 ms |
| First Contentful Paint info | |
|---|---|
| Elements that needed recalculate style before FCP | 354 |
| Time spent in recalculate style before FCP | 27.03 ms |
| Extra timings | |
|---|---|
| TTFB | 211 ms |
| First Paint | 354 ms |
| Load Event End | 1.093 s |
| Fully loaded | 1.205 s |
When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.
| Element type | H1 |
| Element/tag | <h1></h1> |
| Render time | 813 ms |
| Element render delay | 602 ms |
| TTFB | 211 ms |
| Resource delay | 0 ms |
| Resource load duration | 0 ms |
| Elements that needed recalculate style before LCP | 4198 |
| Time spent in recalculate style before LCP | 97.355 ms |
| Load time | 0 ms |
| Size (width*height) | 33528 |
| DOM path | |
| div#section-nouveautes > div:eq(1) > h1> div#section-nouveautes > div:eq(1) > h1> | |
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.
0.00141 cumulative layout shift collected from the Cumulative Layout Shift API.
These HTML elements contribute most to the Cumulative Layout Shifts of the page. The higher score, the more layout shift.
| Score | HTML Element |
|---|---|
| 0.00076 | <div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" onclick=""></div>,<div class="nouveau-curr-flag flex navbar-big-screen"></div>,<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" data-menu="antiquaire"></div>,<div class="w-dropdown-nav nav-menu-hover nav-menu-hover-meta" onclick=""></div>,<div class="w-dropdown-nav magazine nav-menu-hover nav-menu-hover-meta"></div> |
| body > div#totop > div > div#new-menu-top > nav > div:eq(6),body > div#totop > div > div#new-menu-top > div:eq(0) > div:eq(3),body > div#totop > div > div#new-menu-top > nav > div:eq(7),body > div#totop > div > div#new-menu-top > nav > div:eq(3),body > div#totop > div > div#new-menu-top > nav > div:eq(8) | |
| 0.00062 | ,, |
| body > div#section-nouveautes > div:eq(1) > div:eq(0) > #text,body > div#section-nouveautes > div:eq(1) > h1 > #text,body > div#section-nouveautes > div:eq(1) > div:eq(4) > div:eq(1) > h2 > a > #text | |
| 0.00004 | <button type="submit" style="border: none;background: none" aria-label="Que recherchez-vous ?"></button>,<div class="dropdown-arrow"></div>,<div class="dropdown-arrow"></div>,<div class="dropdown-arrow"></div>,<div class="dropdown-arrow"></div> |
| body > div#totop > div > div#new-menu-top > div:eq(0) > div:eq(2) > form > button,body > div#section-nouveautes > div:eq(0) > div > nav > div:eq(1) > div > div:eq(1),body > div#section-nouveautes > div:eq(0) > div > nav > div:eq(2) > div > div:eq(1),body > div#section-nouveautes > div:eq(0) > div > nav > div:eq(3) > div > div:eq(1),body > div#section-nouveautes > div:eq(0) > div > nav > div:eq(4) > div > div:eq(1) | |
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.
Interaction to Next Paint (INP) is a metric that try to measure responsiveness. It's useful if you are testing user journeys. Read more about Interaction to Next Paint.
The measured latency was 120 ms.
| Event type | pointerout |
| Element type | BODY |
| Element class name | body-nouv |
| Event target | html>body.body-nouv |
| Load state when the event happened | loading |
Read more about the Long Animation Frames API here here.
The top 10 longest animation frames entries
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 229 ms | 179.1 ms | 99.9 ms | 93.8 ms | 6.1 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 47 ms | 50.7 ms | 54.3 ms | 52.4 ms | 1.9 ms |
| https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js | ||||
Invoker: https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 40 ms | 138.5 ms | 3.5 ms | 1.7 ms | 1.8 ms |
| https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR | ||||
Invoker: https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 19 ms | 13 ms | 59 ms | 56.5 ms | 2.5 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 15 ms | 65.5 ms | 54.5 ms | 0.1 ms | 54.4 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 59.8 ms | 2.2 ms | 1.7 ms | 0.5 ms |
| https://www.googletagmanager.com/gtag/js?id=G-YP51KSLLWR | ||||
Invoker: TimerHandler:setTimeout | ||||
| https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js | ||||
Invoker: TimerHandler:setTimeout | ||||
There are no Server Timings.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
| Name | Display Time | X | Y | Width | Height |
|---|---|---|---|---|---|
| LargestImage (logo_proantic_2024.png) | 366 ms | 75 | 15 | 69 | 69 |
| <img alt="logo-proantic" src="https://www.proantic.com/ico/logo_proantic_2024.png" style="width: 69px;height: 100%;margin-right: 10px;"> | |||||
| Heading | 966 ms | 300 | 275 | 1050 | 44 |
| <h1></h1> | |||||
| LargestContentfulPaint | 966 ms | 300 | 275 | 1050 | 44 |
| <h1></h1> | |||||
How the page is built.
| Summary | |
|---|---|
| HTTP version | HTTP/2.0 |
| Total requests | 42 |
| Total domains | 8 |
| Total transfer size | 2.2 MB |
| Total content size | 4.0 MB |
| Responses missing compression | 15 |
| Number of cookies | 0 |
| Third party cookies | 0 |
| Requests per response code | |
|---|---|
| 200 | 42 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 119.0 KB | 905.5 KB | 1 |
| css | 0 b | 78.3 KB | 382.8 KB | 8 |
| javascript | 0 b | 338.5 KB | 1.1 MB | 7 |
| image | 0 b | 970.8 KB | 965.1 KB | 15 |
| font | 0 b | 770.8 KB | 766.6 KB | 11 |
| Total | 0 b | 2.2 MB | 4.0 MB | 42 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.proantic.com | 5.480 s | 1.9 MB | 2.9 MB | 33 |
| ajax.googleapis.com | 54 ms | 30.9 KB | 87.4 KB | 1 |
| cdnjs.cloudflare.com | 66 ms | 56.5 KB | 247.7 KB | 1 |
| cdn.jsdelivr.net | 36 ms | 1.9 KB | 4.3 KB | 1 |
| www.googletagmanager.com | 62 ms | 133.5 KB | 383.6 KB | 1 |
| cdn-images.mailchimp.com | 17 ms | 1.2 KB | 2.0 KB | 1 |
| cse.google.com | 50 ms | 4.0 KB | 8.9 KB | 1 |
| www.google.com | 361 ms | 106.8 KB | 341.9 KB | 3 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 week | 1 year |
| Last modified | 5 weeks | 13 weeks | 16 years |
Included requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 10.1 KB | 2 |
| javascript | 96.8 KB | 1 |
| image | 88.5 KB | 1 |
| font | 0 b | 0 |
| Total | 195.3 KB | 4 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 10.1 KB | 2 |
| javascript | 100.8 KB | 2 |
| image | 88.5 KB | 1 |
| font | 0 b | 0 |
| Total | 199.3 KB | 5 |
Render blocking information directly from Chrome.
| Blocking | In body parser blocking | Potentially blocking |
|---|---|---|
| 4 | 4 | 1 |
Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.
Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.
| Type | Quantity | Total duration (ms) |
|---|---|---|
| Total Blocking Time | 230 | |
| Max Potential First Input Delay | 179 | |
| Long Tasks before First Paint | 1 | 55 |
| Long Tasks before First Contentful Paint | 1 | 55 |
| Long Tasks before Largest Contentful Paint | 4 | 394 |
| Long Tasks after Load Event End | 0 | 0 |
| Total Long Tasks | 7 | 585 |
CPU last long task happened at 996 ms
| name | startTime | duration | containerId | containerName | containerSrc | containerType |
|---|---|---|---|---|---|---|
| unknown | 281 | 55 | window | |||
| unknown | 401 | 59 | window | |||
| self | 511 | 179 | window | |||
| self | 690 | 101 | window | |||
| unknown | 880 | 55 | window | |||
| self | 937 | 59 | window | |||
| self | 996 | 77 | window |
Calculated using Tracium.
| Categories (ms) | |
|---|---|
| parseHTML | 356 |
| styleLayout | 286 |
| paintCompositeRender | 17 |
| scriptParseCompile | 2 |
| scriptEvaluation | 217 |
| garbageCollection | 5 |
| other | 183 |
| Events (ms) | |
|---|---|
| ParseHTML | 188 |
| HTMLDocumentParser::MaybeFetchQueuedPreloads | 162 |
| UpdateLayoutTree | 156 |
| Layout | 128 |
| v8.run | 107 |
| RunTask | 107 |
| FunctionCall | 57 |
| PrePaint | 33 |
| EventDispatch | 23 |
| V8.StackGuard | 15 |
| Paint | 13 |
| Tool/domain | Time (ms) |
|---|---|
| Google Tag Manager | 91.4 |
| Google CDN | 54.2 |
| www.proantic.com | 39.1 |
| Cloudflare CDN | 32.0 |
| Other Google APIs/SDKs | 40.5 |
Third party requests categorised by Third party web version 0.26.2.
| Category | Requests |
|---|---|
| cdn | 3 |
| survelliance | 6 |
| tag-manager | 1 |
| marketing | 1 |
| utility | 4 |
| Category | Number of tools |
|---|---|
| cdn | 3 |
| survelliance | 3 |
| tag-manager | 1 |
| marketing | 1 |
| utility | 1 |
Calculated using .*proantic.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 119.0 KB | 905.5 KB | 1 |
| css | 0 b | 67.1 KB | 335.1 KB | 5 |
| javascript | 0 b | 15.0 KB | 47.2 KB | 1 |
| image | 0 b | 970.8 KB | 965.1 KB | 15 |
| font | 0 b | 770.8 KB | 766.6 KB | 11 |
| Total | N/A | 1.9 MB | 2.9 MB | 33 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 11.3 KB | 47.7 KB | 3 |
| javascript | 0 b | 323.5 KB | 1.0 MB | 6 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 0 b | 0 b | 0 |
| Total | N/A | 334.8 KB | 1.1 MB | 9 |
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 .
Median number of violations for all the runs. Check each individual run to see all the violations.
| Type | Violations (median) |
|---|---|
| Critical | 0 (0 issues) |
| Serious | 1 (9 issues) |
| Moderate | 3 (73 issues) |
| Minor | 0 (0 issues) |
