Page summary

https://www.proantic.com/magazine/

Tested 2024-10-08 01:34:41 using Chrome 116.0.5845.140 (runtime settings).

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

Summary

MetricValue
Page metrics
Performance Score94
Total Page Transfer Size458.1 KB
Requests23
Timing metrics
TTFB [median]318 ms
First Paint [median]469 ms
Fully Loaded [median]546 ms
Google Web Vitals
TTFB [median]318 ms
First Contentful Paint (FCP) [median]469 ms
Largest Contentful Paint (LCP) [median]469 ms
Cumulative Layout Shift (CLS) [median]0.01
CPU metrics
CPU long tasks [median]1
CPU longest task duration56 ms
CPU last long task happens at388 ms
Visual Metrics
First Visual Change [median]467 ms
Speed Index [median]493 ms
Visual Complete 85% [median]501 ms
Visual Complete 99% [median]534 ms
Last Visual Change [median]534 ms
Screenshot of run 1

Timings Summary

Metricminmedianmeanmax
Visual Metrics
FirstVisualChange400 ms467 ms456 ms501 ms
LastVisualChange533 ms534 ms567 ms634 ms
SpeedIndex432 ms493 ms494 ms556 ms
LargestImage533 ms534 ms567 ms634 ms
LargestContentfulPaint533 ms534 ms567 ms634 ms
LastMeaningfulPaint533 ms534 ms567 ms634 ms
VisualReadiness67 ms133 ms111 ms133 ms
VisualComplete85433 ms501 ms501 ms568 ms
VisualComplete95533 ms534 ms567 ms634 ms
VisualComplete99533 ms534 ms567 ms634 ms
Google Web Vitals
Time To First Byte (TTFB)291 ms318 ms316 ms338 ms
Largest Contentful Paint (LCP)404 ms469 ms463 ms515 ms
First Contentful Paint (FCP)404 ms469 ms455 ms493 ms
Cumulative Layout Shift (CLS)0.01010.01020.01020.0102
More metrics
firstPaint404 ms469 ms455 ms493 ms
loadEventEnd509 ms536 ms556 ms623 ms
CPU
Total Blocking Time0 ms0 ms0 ms0 ms
Max Potential FID0 ms0 ms0 ms0 ms
CPU long tasks 0112
CPU last long task happens at0 ms388 ms292 ms488 ms
| Waterfall | | Download HAR | 

Waterfall

Run 1 SpeedIndex median

| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
0.4 sCPU Long Task duration 55 ms
0.5 sFirst Visual Change 467 msFirst Contentful Paint 469 msLCP <IMG> 469 ms
0.6 sVisual Complete 85% 501 msLayout Shift 0.01015 511 msDOM Content Loaded Time 513 msLast Visual Change 534 msVisual Complete 95% 534 msVisual Complete 99% 534 msLargest Image 534 msPage Load Time 536 msFully Loaded 546 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.0.2.

I am the coach

Coach score

Performance advice (94)

TitleAdviceScore
Avoid slowing down the critical rendering path (avoidRenderBlocking)The page has 6 blocking requests and 2 in body parser blocking (2 JavaScript and 6 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:
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/js/scripts.js,qv....jm.YPk7tHUcXX.js
  • https://stats.wp.com/e-202441.js
  • 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 1 CPU long task with the total of 55 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 55 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.80
    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:
  • unknown
  • 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:
  • https://fonts.googleapis.com/css...oogleapis.com/css
  • 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:
  • https://pixel.wp.com/g.gif...ixel.wp.com/g.gif
  • Long cache headers is good (cacheHeadersLong)The page has 11 requests that have a shorter cache time than 30 days (but still a cache time).89
    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.proantic.com/magazine/wp-includes/css/dist/block-library/A.style.min...cf.wKYjcZoIuW.css
  • https://www.proantic.com/magazine/wp-includes/js/mediaelement/mediaelementplayer...er-legacy.min.css
  • https://www.proantic.com/magazine/wp-includes/js/mediaelement/wp-mediaelement.min.css?ver=6.6.2
  • https://fonts.googleapis.com/css...oogleapis.com/css
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/vendor/olsen-ico...cf.B48meyexaI.css
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/A.style.css,qver...cf.yHt3onmplW.css
  • https://www.proantic.com/magazine/wp-content/plugins/jetpack/css/jetpack.css?ver=13.8.1
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/js/scripts.js,qv....jm.YPk7tHUcXX.js
  • https://www.proantic.com/magazine/wp-content/uploads/2023/12/proantic_ico_256.png
  • https://www.proantic.com/magazine/wp-includes/js/wp-emoji-release.min.js?ver=6.6.2
  • https://www.proantic.com/favicon.ico
  • 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:
  • https://fonts.gstatic.com/s/lato/v24/S6uyw4BMUTPHjx4wXg.woff2
  • https://fonts.gstatic.com/s/lora/v35/0QIvMX1D_JOuMwr7Iw.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6u9w4BMUTPHh6UVSwiPGQ.woff2
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/vendor/olsen-ico...olsen-icons.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6u8w4BMUTPHjxsAXC-q.woff2
  • Make each CSS response small (optimalCssSize)https://www.proantic.com/magazine/wp-includes/css/dist/block-library/A.style.min.css,qver=6.6.2.pagespeed.cf.wKYjcZoIuW.css size is 15.6 kB (15566) and that is bigger than the limit of 14.5 kB. https://www.proantic.com/magazine/wp-content/plugins/jetpack/css/jetpack.css?ver=13.8.1 size is 20.3 kB (20264) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB.80
    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:
    URLTransfer sizeContent size
    https://www.proantic.com/magazine/wp-includes/css/dist/block-library/A.style.min...cf.wKYjcZoIuW.css 15.2 KB109.7 KB
    https://www.proantic.com/magazine/wp-content/plugins/jetpack/css/jetpack.css?ver=13.8.1 19.8 KB106.6 KB
    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:
  • https://fonts.googleapis.com/css...oogleapis.com/css
  • Best practice advice (85)

    TitleAdviceScore
    Avoid too many third party requests (thirdParty)The page do 48% requests to third party domains (11 requests and 338.4 kB). First party is 12 requests and 130.7 kB. The page transfer more bytes from third party domains (338.4 kB) then first party (130.7 kB). The regex .*proantic.* 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 21 responses that sets both a max-age and expires header. There are 23 responses that sets a server header. 56
    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.proantic.com/magazine/
  • https://www.proantic.com/magazine/wp-includes/css/dist/block-library/A.style.min...cf.wKYjcZoIuW.css
  • https://www.proantic.com/magazine/wp-includes/css/dist/block-library/A.style.min...cf.wKYjcZoIuW.css
  • https://www.proantic.com/magazine/wp-includes/js/mediaelement/mediaelementplayer...er-legacy.min.css
  • https://www.proantic.com/magazine/wp-includes/js/mediaelement/mediaelementplayer...er-legacy.min.css
  • https://www.proantic.com/magazine/wp-includes/js/mediaelement/wp-mediaelement.min.css?ver=6.6.2
  • https://www.proantic.com/magazine/wp-includes/js/mediaelement/wp-mediaelement.min.css?ver=6.6.2
  • https://fonts.googleapis.com/css...oogleapis.com/css
  • https://fonts.googleapis.com/css...oogleapis.com/css
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/vendor/olsen-ico...cf.B48meyexaI.css
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/vendor/olsen-ico...cf.B48meyexaI.css
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/A.style.css,qver...cf.yHt3onmplW.css
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/A.style.css,qver...cf.yHt3onmplW.css
  • https://www.proantic.com/magazine/wp-content/plugins/jetpack/css/jetpack.css?ver=13.8.1
  • https://www.proantic.com/magazine/wp-content/plugins/jetpack/css/jetpack.css?ver=13.8.1
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-6...66efefbaeaf03.jpg
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-6...66efefbaeaf03.jpg
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/js/scripts.js,qv....jm.YPk7tHUcXX.js
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/js/scripts.js,qv....jm.YPk7tHUcXX.js
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/b0434209_...4209_01043923.jpg
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/b0434209_...4209_01043923.jpg
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/Capture-d...-10-07-095700.png
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/Capture-d...-10-07-095700.png
  • https://www.proantic.com/magazine/wp-content/uploads/2023/12/proantic_ico_256.png
  • https://www.proantic.com/magazine/wp-content/uploads/2023/12/proantic_ico_256.png
  • https://stats.wp.com/e-202441.js
  • https://stats.wp.com/e-202441.js
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/09/1407731-m...66f666bbd3027.jpg
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/09/1407731-m...66f666bbd3027.jpg
  • https://fonts.gstatic.com/s/lato/v24/S6uyw4BMUTPHjx4wXg.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6uyw4BMUTPHjx4wXg.woff2
  • https://fonts.gstatic.com/s/lora/v35/0QIvMX1D_JOuMwr7Iw.woff2
  • https://fonts.gstatic.com/s/lora/v35/0QIvMX1D_JOuMwr7Iw.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6u9w4BMUTPHh6UVSwiPGQ.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6u9w4BMUTPHh6UVSwiPGQ.woff2
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/vendor/olsen-ico...olsen-icons.woff2
  • https://www.proantic.com/magazine/wp-content/themes/olsen-light/vendor/olsen-ico...olsen-icons.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6u8w4BMUTPHjxsAXC-q.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6u8w4BMUTPHjxsAXC-q.woff2
  • https://pixel.wp.com/g.gif...ixel.wp.com/g.gif
  • https://www.proantic.com/magazine/wp-includes/js/wp-emoji-release.min.js?ver=6.6.2
  • https://www.proantic.com/magazine/wp-includes/js/wp-emoji-release.min.js?ver=6.6.2
  • https://www.proantic.com/favicon.ico
  • https://www.proantic.com/favicon.ico
  • Privacy advice (83)

    TitleAdviceScore
    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.proantic.com/magazine/
  • 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.proantic.com/magazine/
  • Do not share user data with third parties. (thirdPartyPrivacy)The page has 48% requests that are 3rd party (11 requests with a size of 338.4 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:
  • https://fonts.googleapis.com/css...oogleapis.com/css
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-6...66efefbaeaf03.jpg
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/b0434209_...4209_01043923.jpg
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/Capture-d...-10-07-095700.png
  • https://stats.wp.com/e-202441.js
  • https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/09/1407731-m...66f666bbd3027.jpg
  • https://fonts.gstatic.com/s/lato/v24/S6uyw4BMUTPHjx4wXg.woff2
  • https://fonts.gstatic.com/s/lora/v35/0QIvMX1D_JOuMwr7Iw.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6u9w4BMUTPHh6UVSwiPGQ.woff2
  • https://fonts.gstatic.com/s/lato/v24/S6u8w4BMUTPHjxsAXC-q.woff2
  • https://pixel.wp.com/g.gif...ixel.wp.com/g.gif
  • Page info

    Page info
    TitleLe Magazine de Proantic - Magazine d'art et expositions
    GeneratorWordPress 6.6.2
    Width1350
    Height9002
    DOM elements473
    Avg DOM depth13
    Max DOM depth18
    Iframes0
    Script tags6
    Local storage0 b
    Session storage94 B
    Network Information API4g
    Resource Hints
    dns-prefetch
    https://stats.wp.com/
    https://v0.wordpress.com/
    https://i0.wp.com/

    Technologies used to build the page.

    Data collected using Wappalyzerversion 6.10.66.  Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyser find more information about technologies used.

    TechnologyConfidenceCategory
    WordPress 6.6.2100  CMS Blogs
    MySQL 100  Databases
    PHP 100  Programming languages
    Nginx 100  Web servers Reverse proxies
    HSTS 100  Security
    Google PageSpeed 1.13.35.2100  Caching Web server extensions Performance
    HTTP/3 100  Miscellaneous

    Data collected using Third Party Web 0.24.0

    Cdn
    Google Fonts
    Survelliance
    Google Fonts
    Hosting
    WordPress
    Analytics
    WordPress Site Stats
    | Browser metrics | Visual Metrics | Largest Contentful Paint | Cumulative Layout Shift | Visual Elements | 

    Data from run 1

    Visual Metrics

    Browser Metrics

    Google Web Vitals
    Time to first byte (TTFB)318 ms
    First Contentful Paint (FCP)469 ms
    Largest Contentful Paint (LCP)469 ms
    Cumulative Layout Shift (CLS)0.01
    Total Blocking Time (TBT)0 ms
    First Contentful Paint info
    Elements that needed recalculate style before FCP554
    Time spent in recalculate style before FCP28.924 ms
    Extra timings
    TTFB318 ms
    First Paint469 ms
    Load Event End536 ms
    Fully loaded546 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 width="720" height="471" src="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=720%2C471&amp;ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" itemprop="image" decoding="async" fetchpriority="high" srcset="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=300%2C197&amp;ssl=1 300w, https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=720%2C471&amp;ssl=1 720w" sizes="(max-width: 720px) 100vw, 720px" data-attachment-id="17118" data-permalink="https://www.proantic.com/magazine/plat-en-faience-paul-milet-a-sevres/1405037-66efefbaeaf03/" data-orig-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=1200%2C789&amp;ssl=1" data-orig-size="1200,789" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="1405037-66efefbaeaf03" data-image-description="" data-image-caption="" data-medium-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=300%2C197&amp;ssl=1" data-large-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=665%2C437&amp;ssl=1" tabindex="0" role="button">
    Render time 469 ms
    Elements that needed recalculate style before LCP554
    Time spent in recalculate style before LCP28.924 ms
    Load time406 ms
    URL https://i0.wp.com/ww...66efefbaeaf03.jpg
    Size (width*height)161772
    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-17114 > 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-17114 > div:eq(2) > 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.01015 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.01015,<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
    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.

    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 (1405037-66efefbaeaf03.jpg?resize=720%2C471&ssl=1)534 ms 170 392 663 434
    <img width="720" height="471" src="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=720%2C471&amp;ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" itemprop="image" decoding="async" fetchpriority="high" srcset="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=300%2C197&amp;ssl=1 300w, https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=720%2C471&amp;ssl=1 720w" sizes="(max-width: 720px) 100vw, 720px" data-attachment-id="17118" data-permalink="https://www.proantic.com/magazine/plat-en-faience-paul-milet-a-sevres/1405037-66efefbaeaf03/" data-orig-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=1200%2C789&amp;ssl=1" data-orig-size="1200,789" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="1405037-66efefbaeaf03" data-image-description="" data-image-caption="" data-medium-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=300%2C197&amp;ssl=1" data-large-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=665%2C437&amp;ssl=1" tabindex="0" role="button">
    LargestContentfulPaint (1405037-66efefbaeaf03.jpg?resize=720%2C471&ssl=1)534 ms 170 392 663 434
    <img width="720" height="471" src="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=720%2C471&amp;ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" itemprop="image" decoding="async" fetchpriority="high" srcset="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=300%2C197&amp;ssl=1 300w, https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?resize=720%2C471&amp;ssl=1 720w" sizes="(max-width: 720px) 100vw, 720px" data-attachment-id="17118" data-permalink="https://www.proantic.com/magazine/plat-en-faience-paul-milet-a-sevres/1405037-66efefbaeaf03/" data-orig-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=1200%2C789&amp;ssl=1" data-orig-size="1200,789" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="1405037-66efefbaeaf03" data-image-description="" data-image-caption="" data-medium-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=300%2C197&amp;ssl=1" data-large-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/10/1405037-66efefbaeaf03.jpg?fit=665%2C437&amp;ssl=1" tabindex="0" role="button">
    | 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 domains6
    Total transfer size458.1 KB
    Total content size791.8 KB
    Responses missing compression11
    Number of cookies0
    Third party cookies0
    Requests per response code
    20023

    Largest assets on the page (by transfer size)

    Requests and sizes per content type

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b13.0 KB71.8 KB1
    css0 b53.4 KB313.8 KB7
    javascript0 b9.4 KB27.9 KB3
    image0 b254.7 KB252.3 KB6
    font0 b126.1 KB124.9 KB5
    favicon0 b1.4 KB1.1 KB1
    Total0 b458.1 KB791.8 KB23

    Data per domain

    DomainTotal download timeTransfer SizeContent SizeRequests
    www.proantic.com601 ms127.6 KB441.6 KB12
    fonts.googleapis.com42 ms2.2 KB20.4 KB1
    i0.wp.com85 ms218.1 KB216.2 KB4
    stats.wp.com37 ms2.9 KB7.2 KB1
    fonts.gstatic.com42 ms107.2 KB106.2 KB4
    pixel.wp.com6 ms177 B50 B1

    Expires and last modified statistics

    typeminmedianmax
    Expires0 seconds1 week2 years
    Last modified44 minutes5 weeks4 years

    Requests loaded after onLoad event

    Included requests done after load event end.

    ContentTransfer SizeRequests
    html0 b0
    css0 b0
    javascript0 b0
    image0 b0
    font0 b0
    favicon1.4 KB1
    Total1.4 KB1

    Requests loaded after onContentLoad

    Includes requests done after DOM content loaded.

    ContentTransfer SizeRequests
    html0 b0
    css0 b0
    javascript0 b0
    image0 b0
    font0 b0
    favicon1.4 KB1
    Total1.4 KB1

    Render blocking requests

    Render blocking information directly from Chrome.

    BlockingIn body parser blockingPotentially blocking
    620

    Render information

    | CPU Long Tasks | First Input Delay | 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 0
    Max Potential First Input Delay 0
    Long Tasks before First Paint155
    Long Tasks before First Contentful Paint155
    Long Tasks before Largest Contentful Paint155
    Long Tasks after Load Event End00
    Total Long Tasks155

    CPU last long task happened at 388 ms

    Individual Long Tasks

    namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
    unknown38855window

    CPU time spent

    Calculated using Tracium.

    Categories (ms)
    parseHTML22
    styleLayout82
    paintCompositeRender4
    scriptParseCompile1
    scriptEvaluation27
    garbageCollection0
    other92
    Events (ms)
    RunTask69
    Layout53
    UpdateLayoutTree29
    v8.run17
    ParseAuthorStyleSheet15
    Commit11

    Time spent per request

    URLCPU time (ms)
    https://www.proantic.com/magazine/12

    CPU time spent

    Tool/domainTime (ms)
    www.proantic.com12.0
    | Categories | | Tools | | First vs third | 

    Third party

    Third party requests categorised by Third party web version 0.24.0.

    CategoryRequests
    cdn 5
    survelliance 5
    hosting 4
    analytics 2
    CategoryNumber of tools
    cdn 1
    survelliance 1
    hosting 1
    analytics 1

    Third party requests and tools

    cdn (5 requests)
    Google Fonts
    survelliance (5 requests)
    Google Fonts
    hosting (4 requests)
    WordPress
    analytics (2 requests)
    WordPress Site Stats

    First party requests and sizes per content type

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

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b13.0 KB71.8 KB1
    css0 b51.3 KB293.3 KB6
    javascript0 b6.5 KB20.7 KB2
    image0 b36.4 KB36.1 KB1
    font0 b18.9 KB18.6 KB1
    favicon0 b1.4 KB1.1 KB1
    TotalN/A127.6 KB441.6 KB12

    Third party requests and sizes per content type

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b0 b0 b0
    css0 b2.2 KB20.4 KB1
    javascript0 b2.9 KB7.2 KB1
    image0 b218.3 KB216.3 KB5
    font0 b107.2 KB106.2 KB4
    TotalN/A330.5 KB350.1 KB11

    Axe

    Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Tested using axe-core version 4.7.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 0
    Serious3
    Moderate3
    Minor2