Tested 2025-02-19 02:34:59 using Chrome 132.0.6834.83 (runtime settings).
| Metric | Value |
|---|---|
| Page metrics | |
| Performance Score | 94 |
| Total Page Transfer Size | 1.0 MB |
| Requests | 22 |
| Timing metrics | |
| TTFB [median] | 348 ms |
| First Paint [median] | 496 ms |
| Fully Loaded [median] | 609 ms |
| Google Web Vitals | |
| TTFB [median] | 348 ms |
| First Contentful Paint (FCP) [median] | 496 ms |
| Largest Contentful Paint (LCP) [median] | 496 ms |
| Cumulative Layout Shift (CLS) [median] | 0.01 |
| CPU metrics | |
| CPU long tasks [median] | 1 |
| CPU longest task duration | 55 ms |
| CPU last long task happens at | 395 ms |
| Visual Metrics | |
| First Visual Change [median] | 500 ms |
| Speed Index [median] | 541 ms |
| Visual Complete 85% [median] | 600 ms |
| Visual Complete 99% [median] | 600 ms |
| Last Visual Change [median] | 600 ms |
| Metric | min | median | mean | max |
|---|---|---|---|---|
| Visual Metrics | ||||
| FirstVisualChange | 500 ms | 500 ms | 567 ms | 700 ms |
| LastVisualChange | 600 ms | 600 ms | 678 ms | 834 ms |
| SpeedIndex | 528 ms | 541 ms | 606 ms | 748 ms |
| LargestImage | 600 ms | 600 ms | 678 ms | 834 ms |
| LargestContentfulPaint | 600 ms | 600 ms | 678 ms | 834 ms |
| LastMeaningfulPaint | 600 ms | 600 ms | 678 ms | 834 ms |
| VisualReadiness | 100 ms | 100 ms | 111 ms | 134 ms |
| VisualComplete85 | 533 ms | 600 ms | 656 ms | 834 ms |
| VisualComplete95 | 600 ms | 600 ms | 678 ms | 834 ms |
| VisualComplete99 | 600 ms | 600 ms | 678 ms | 834 ms |
| Google Web Vitals | ||||
| Time To First Byte (TTFB) | 332 ms | 348 ms | 421 ms | 582 ms |
| Largest Contentful Paint (LCP) | 478 ms | 496 ms | 560 ms | 707 ms |
| First Contentful Paint (FCP) | 478 ms | 496 ms | 560 ms | 707 ms |
| Cumulative Layout Shift (CLS) | 0.0103 | 0.0103 | 0.0103 | 0.0103 |
| More metrics | ||||
| firstPaint | 478 ms | 496 ms | 560 ms | 707 ms |
| loadEventEnd | 578 ms | 582 ms | 666 ms | 837 ms |
| CPU | ||||
| Total Blocking Time | 0 ms | 0 ms | 0 ms | 0 ms |
| Max Potential FID | 0 ms | 0 ms | 0 ms | 0 ms |
| CPU long tasks | 0 | 1 | 1 | 1 |
| CPU last long task happens at | 0 ms | 395 ms | 270 ms | 414 ms |
Run 3 SpeedIndex median
Use--filmstrip.showAll to show all filmstrips.
0 s0.4 sCPU Long Task duration 55 ms
0.6 sDOM Content Loaded Time 518 msLayout Shift 0.01030 574 msPage Load Time 578 msFully Loaded 598 msLast Visual Change 600 msVisual Complete 85% 600 msVisual Complete 95% 600 msVisual Complete 99% 600 msLargest Image 600 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 5 blocking requests and 2 in body parser blocking (2 JavaScript and 5 CSS). | 80 | ||||||
| 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: | ||||||||
| 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 Frontend single point of failures (spof) | The 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. | 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 1 request that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 177 B the next access. | 90 | ||||||
| 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 10 requests that have a shorter cache time than 30 days (but still a cache time). | 90 | ||||||
| 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: | ||||||||
| Avoid too many fonts (fewFonts) | The page has 5 font requests. Do you really need them? What value does the fonts give the user? | 50 | ||||||
| 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 866.8 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. | ||||||||
| Make each CSS response small (optimalCssSize) | https://www.proantic.com/magazine/wp-includes/css/dist/block-library/A.style.min.css,qver=6.7.pagespeed.cf.-GTKN38myC.css size is 15.9 kB (15897) 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:
| ||||||||
| Don't use private headers on static content (privateAssets) | The page has 1 request with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 90 | ||||||
| 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 |
|---|---|---|
| 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: | ||
| 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 50% requests that are 3rd party (11 requests with a size of 946.7 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 5 survelliance requests and uses 1 survelliance tool. The page do 4 hosting requests and uses 1 hosting tool. The page do 2 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: | ||
| Page info | |
|---|---|
| Title | Le Magazine de Proantic - Magazine d'art et expositions |
| Generator | WordPress 6.7 |
| Width | 1350 |
| Height | 8813 |
| DOM elements | 472 |
| Avg DOM depth | 13 |
| Max DOM depth | 18 |
| Iframes | 0 |
| Script tags | 6 |
| Local storage | 0 b |
| Session storage | 94 B |
| Network Information API | 4g |
| Resource Hints |
|---|
| dns-prefetch |
| https://stats.wp.com/ |
| https://v0.wordpress.com/ |
| https://i0.wp.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 |
|---|---|---|
| WordPress 6.7 | 100 | CMS Blogs |
| MySQL | 100 | Databases |
| PHP | 100 | Programming languages |
| Nginx | 100 | Web servers Reverse proxies |
| HSTS | 100 | Security |
| Google PageSpeed 1.13.35.2 | 100 | Caching Web server extensions Performance |
| HTTP/3 | 100 | Miscellaneous |
Data collected using Third Party Web 0.26.2
| Cdn |
|---|
| Google Fonts |
| Survelliance |
| Google Fonts |
| Hosting |
| WordPress |
| Analytics |
| WordPress Site Stats |
Data from run 3
| Visual Metrics | |
|---|---|
| First Visual Change | 500 ms |
| Speed Index | 541 ms |
| Largest Image | 600 ms |
| LargestContentfulPaint | 600 ms |
| Last Meaningful Paint | 600 ms |
| Largest Contentful Paint | 600 ms |
| Visual Complete 85% | 600 ms |
| Visual Complete 95% | 600 ms |
| Visual Complete 99% | 600 ms |
| Last Visual Change | 600 ms |
| Visual Readiness | 100 ms |
| Navigation Timing | |
|---|---|
| backEndTime | 348 ms |
| domContentLoadedTime | 518 ms |
| domInteractiveTime | 518 ms |
| domainLookupTime | 0 ms |
| frontEndTime | 229 ms |
| pageDownloadTime | 1 ms |
| pageLoadTime | 578 ms |
| redirectionTime | 0 ms |
| serverConnectionTime | 17 ms |
| serverResponseTime | 328 ms |
| Google Web Vitals | |
|---|---|
| Time to first byte (TTFB) | 348 ms |
| First Contentful Paint (FCP) | 478 ms |
| Largest Contentful Paint (LCP) | 478 ms |
| Cumulative Layout Shift (CLS) | 0.01 |
| Total Blocking Time (TBT) | 0 ms |
| First Contentful Paint info | |
|---|---|
| Elements that needed recalculate style before FCP | 338 |
| Time spent in recalculate style before FCP | 18.855 ms |
| Extra timings | |
|---|---|
| TTFB | 348 ms |
| First Paint | 478 ms |
| Load Event End | 578 ms |
| Fully loaded | 598 ms |
When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.
| Element type | IMG |
| Element/tag | <img width="720" height="471" src="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?resize=720%2C471&ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" itemprop="image" decoding="async" fetchpriority="high" data-attachment-id="17428" data-permalink="https://www.proantic.com/magazine/cabinet-anversois-du-xviieme-siecle/1487006-main-67a78a1a27b7b/" data-orig-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=1200%2C736&ssl=1" data-orig-size="1200,736" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="Cabinet Anversois du XVIIème siècle. c) Galerie Nicolas Lenté, Proantic" data-image-description="" data-image-caption="" data-medium-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=300%2C184&ssl=1" data-large-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=665%2C408&ssl=1"> |
| Render time | 478 ms |
| Element render delay | 92 ms |
| TTFB | 348 ms |
| Resource delay | 9 ms |
| Resource load duration | 29 ms |
| Elements that needed recalculate style before LCP | 338 |
| Time spent in recalculate style before LCP | 18.855 ms |
| Load time | 410 ms |
| URL | https://i0.wp.com/ww...67a78a1a27b7b.jpg |
| Size (width*height) | 155142 |
| DOM path | |
| div#page > div:eq(1) > div > div > div#site-content > div > div:eq(0) > main#content > div:eq(0) > div#inner-content > article#entry-17421 > div:eq(2) > a > img> div#page > div:eq(1) > div > div > div#site-content > div > div:eq(0) > main#content > div:eq(0) > div#inner-content > article#entry-17421 > div:eq(2) > a > img> | |
The largest contentful paint is highlighted in the image. If no element is highlighted the element was removed before the screenshot or the LCP API couldn't find the element.
The Largest Contentful Paint API highlighted this image as a part of the LCP.
0.01030 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.01030 | ,<p class="tagline"></p>,<div class="site-bar"></div>,<div id="site-content"></div> |
| body > div#page > div:eq(1) > div > div > header#masthead > div:eq(0) > div > a > #text,body > div#page > div:eq(1) > div > div > header#masthead > div:eq(0) > p,body > div#page > div:eq(1) > div > div > header#masthead > div:eq(1),body > div#page > div:eq(1) > div > div > div#site-content | |
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.
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 |
|---|---|---|---|---|
| 12 ms | 35 ms | 31 ms | 29.5 ms | 1.5 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 4 ms | 43.6 ms | 43.4 ms | 0 ms | 43.4 ms |
| https://www.proantic.com/magazine/ | ||||
Invoker: https://www.proantic.com/magazine/ | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 30.9 ms | 27.1 ms | 26.2 ms | 0.9 ms |
| No availible script information. | ||||
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 (1487006-main-67a78a1a27b7b.jpg?resize=720%2C471&ssl=1) | 600 ms | 170 | 392 | 663 | 434 |
| <img width="720" height="471" src="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?resize=720%2C471&ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" itemprop="image" decoding="async" fetchpriority="high" data-attachment-id="17428" data-permalink="https://www.proantic.com/magazine/cabinet-anversois-du-xviieme-siecle/1487006-main-67a78a1a27b7b/" data-orig-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=1200%2C736&ssl=1" data-orig-size="1200,736" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="Cabinet Anversois du XVIIème siècle. c) Galerie Nicolas Lenté, Proantic" data-image-description="" data-image-caption="" data-medium-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=300%2C184&ssl=1" data-large-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=665%2C408&ssl=1"> | |||||
| LargestContentfulPaint (1487006-main-67a78a1a27b7b.jpg?resize=720%2C471&ssl=1) | 600 ms | 170 | 392 | 663 | 434 |
| <img width="720" height="471" src="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?resize=720%2C471&ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" itemprop="image" decoding="async" fetchpriority="high" data-attachment-id="17428" data-permalink="https://www.proantic.com/magazine/cabinet-anversois-du-xviieme-siecle/1487006-main-67a78a1a27b7b/" data-orig-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=1200%2C736&ssl=1" data-orig-size="1200,736" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="Cabinet Anversois du XVIIème siècle. c) Galerie Nicolas Lenté, Proantic" data-image-description="" data-image-caption="" data-medium-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=300%2C184&ssl=1" data-large-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2025/02/1487006-main-67a78a1a27b7b.jpg?fit=665%2C408&ssl=1"> | |||||
How the page is built.
| Summary | |
|---|---|
| HTTP version | HTTP/2.0 |
| Total requests | 22 |
| Total domains | 6 |
| Total transfer size | 1.0 MB |
| Total content size | 1.3 MB |
| Responses missing compression | 10 |
| Number of cookies | 0 |
| Third party cookies | 0 |
| Requests per response code | |
|---|---|
| 200 | 22 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 12.8 KB | 70.0 KB | 1 |
| css | 0 b | 34.1 KB | 210.4 KB | 6 |
| javascript | 0 b | 9.4 KB | 27.9 KB | 3 |
| image | 0 b | 849.4 KB | 846.4 KB | 6 |
| font | 0 b | 125.3 KB | 124.9 KB | 5 |
| favicon | 0 b | 1.4 KB | 1.1 KB | 1 |
| Total | 0 b | 1.0 MB | 1.3 MB | 22 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.proantic.com | 814 ms | 107.9 KB | 335.5 KB | 11 |
| fonts.googleapis.com | 53 ms | 2.3 KB | 21.4 KB | 1 |
| i0.wp.com | 149 ms | 812.8 KB | 810.3 KB | 4 |
| stats.wp.com | 29 ms | 2.9 KB | 7.2 KB | 1 |
| fonts.gstatic.com | 57 ms | 106.4 KB | 106.2 KB | 4 |
| pixel.wp.com | 5 ms | 177 B | 50 B | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 week | 2 years |
| Last modified | 0 seconds | 22 weeks | 5 years |
Included requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 1.4 KB | 1 |
| Total | 1.4 KB | 1 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 5.3 KB | 1 |
| image | 177 B | 1 |
| font | 0 b | 0 |
| favicon | 1.4 KB | 1 |
| Total | 6.9 KB | 3 |
Render blocking information directly from Chrome.
| Blocking | In body parser blocking | Potentially blocking |
|---|---|---|
| 5 | 2 | 0 |
| URL | Type |
|---|---|
| https://fonts.gstati...D_JOuMwr7Iw.woff2 | non_blocking |
| https://fonts.gstati...TPHjxsAXC-q.woff2 | non_blocking |
| https://fonts.gstati...MUTPHjx4wXg.woff2 | non_blocking |
| https://fonts.gstati...Hh6UVSwiPGQ.woff2 | non_blocking |
| https://www.proantic...olsen-icons.woff2 | non_blocking |
| https://www.proantic...cf.-GTKN38myC.css | blocking |
| https://www.proantic...cf.yHt3onmplW.css | blocking |
| https://www.proantic...ji-release.min.js | non_blocking |
| https://stats.wp.com/e-202508.js | in_body_parser_blocking |
| https://www.proantic...er-legacy.min.css | blocking |
| https://fonts.google...oogleapis.com/css | non_blocking |
| https://www.proantic...cf.B48meyexaI.css | blocking |
| https://www.proantic...iaelement.min.css | blocking |
| https://www.proantic....jm.YPk7tHUcXX.js | in_body_parser_blocking |
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 | 0 | |
| Max Potential First Input Delay | 0 | |
| Long Tasks before First Paint | 1 | 55 |
| Long Tasks before First Contentful Paint | 1 | 55 |
| Long Tasks before Largest Contentful Paint | 1 | 55 |
| Long Tasks after Load Event End | 0 | 0 |
| Total Long Tasks | 1 | 55 |
CPU last long task happened at 395 ms
| name | startTime | duration | containerId | containerName | containerSrc | containerType |
|---|---|---|---|---|---|---|
| unknown | 395 | 55 | window |
Calculated using Tracium.
| Categories (ms) | |
|---|---|
| parseHTML | 32 |
| styleLayout | 115 |
| paintCompositeRender | 4 |
| scriptParseCompile | 1 |
| scriptEvaluation | 32 |
| garbageCollection | 0 |
| other | 88 |
| Events (ms) | |
|---|---|
| Layout | 79 |
| RunTask | 74 |
| UpdateLayoutTree | 36 |
| ParseHTML | 19 |
| RunMicrotasks | 15 |
| v8.run | 13 |
| HTMLDocumentParser::MaybeFetchQueuedPreloads | 11 |
Third party requests categorised by Third party web version 0.26.2.
| Category | Requests |
|---|---|
| cdn | 5 |
| survelliance | 5 |
| hosting | 4 |
| analytics | 2 |
| Category | Number of tools |
|---|---|
| cdn | 1 |
| survelliance | 1 |
| hosting | 1 |
| analytics | 1 |
Calculated using .*proantic.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 12.8 KB | 70.0 KB | 1 |
| css | 0 b | 31.8 KB | 189.0 KB | 5 |
| javascript | 0 b | 6.5 KB | 20.7 KB | 2 |
| image | 0 b | 36.4 KB | 36.1 KB | 1 |
| font | 0 b | 18.9 KB | 18.6 KB | 1 |
| favicon | 0 b | 1.4 KB | 1.1 KB | 1 |
| Total | N/A | 107.9 KB | 335.5 KB | 11 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 2.3 KB | 21.4 KB | 1 |
| javascript | 0 b | 2.9 KB | 7.2 KB | 1 |
| image | 0 b | 813.0 KB | 810.4 KB | 5 |
| font | 0 b | 106.4 KB | 106.2 KB | 4 |
| Total | N/A | 924.6 KB | 945.2 KB | 11 |
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 | 3 (75 issues) |
| Moderate | 3 (7 issues) |
| Minor | 0 (0 issues) |
