Run 3 summary

Summary

Metric	Value
Page metrics
Performance score	97
Total page size	752.6 KB
Requests	16
Timing metrics
TTFB	285 ms
First Paint	411 ms
Fully Loaded	459 ms
Google Web Vitals
TTFB	285 ms
First Contentful Paint (FCP)	411 ms
Largest Contentful Paint (LCP)	411 ms
Cumulative Layout Shift (CLS)	0.00
Visual Metrics
First Visual Change	400 ms
Speed Index	444 ms
Visual Complete 85%	467 ms
Visual Complete 99%	467 ms
Last Visual Change	467 ms

Waterfall

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.4 sFirst Visual Change 400 ms

0.5 sDOM Content Loaded Time 406 msFirst Contentful Paint 411 msLCP <IMG> 411 msPage Load Time 413 msLayout Shift 0.00001 418 msFully Loaded 459 msLast Visual Change 467 msVisual Complete 85% 467 msVisual Complete 95% 467 msVisual Complete 99% 467 msLargest Image 467 ms

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.

Coach score

• Total score 92
• Performance score 97
• Privacy score 87
• Best practice score 85

Performance advice (97)

Show/hide details

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: https://www.proantic.com/magazine/wp-content/themes/olsen-light/js/scripts.js,qv....jm.YPk7tHUcXX.js https://stats.wp.com/e-202450.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 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 9 requests that have a shorter cache time than 30 days (but still a cache time).	91
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.-GTKN38myC.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.7 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/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/favicon.ico https://www.proantic.com/magazine/wp-includes/js/wp-emoji-release.min.js?ver=6.7
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: URL Transfer size Content size https://www.proantic.com/magazine/wp-includes/css/dist/block-library/A.style.min...cf.-GTKN38myC.css 15.5 KB 111.9 KB

Best practice advice (85)

Show/hide details

Title	Advice	Score
Avoid too many third party requests (thirdParty)	The page do 31% requests to third party domains (5 requests and 660 kB). First party is 11 requests and 110.7 kB. The page transfer more bytes from third party domains (660 kB) then first party (110.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 14 responses that sets both a max-age and expires header. There are 16 responses that sets a server header.	70
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.-GTKN38myC.css https://www.proantic.com/magazine/wp-includes/css/dist/block-library/A.style.min...cf.-GTKN38myC.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.7 https://www.proantic.com/magazine/wp-includes/js/mediaelement/wp-mediaelement.min.css?ver=6.7 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://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-104643.png https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-104643.png 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://stats.wp.com/e-202450.js https://stats.wp.com/e-202450.js https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-110436.png https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-110436.png https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-115208.png https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-115208.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://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://pixel.wp.com/g.gif...ixel.wp.com/g.gif https://www.proantic.com/favicon.ico https://www.proantic.com/favicon.ico https://www.proantic.com/magazine/wp-includes/js/wp-emoji-release.min.js?ver=6.7 https://www.proantic.com/magazine/wp-includes/js/wp-emoji-release.min.js?ver=6.7

Privacy advice (87)

Show/hide details

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: 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 31% requests that are 3rd party (5 requests with a size of 660 kB). The page do 3 hosting requests and uses 1 hosting tool. The page do 2 analytics requests and uses 1 analytics tool.	69
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://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-104643.png https://stats.wp.com/e-202450.js https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-110436.png https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-d...-12-07-115208.png https://pixel.wp.com/g.gif...ixel.wp.com/g.gif

Page info

Page info
Title	Le Magazine de Proantic - Magazine d'art et expositions
Generator	WordPress 6.7
Width	1350
Height	8943
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/

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.

Technology	Confidence	Category
WordPress 6.7	100	CMS Blogs
MySQL	100	Databases
PHP	100	Programming languages
Nginx	100	Web servers Reverse proxies
Google PageSpeed 1.13.35.2	100	Caching Web server extensions Performance
HTTP/3	100	Miscellaneous

Data collected using Third Party Web 0.24.0

Hosting
WordPress
Analytics
WordPress Site Stats

Visual Metrics

Browser Metrics

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 type	IMG
Element/tag	<img width="720" height="471" src="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-decran-2024-12-07-104643.png?resize=720%2C471&amp;ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" itemprop="image" decoding="async" fetchpriority="high" data-attachment-id="17275" data-permalink="https://www.proantic.com/magazine/paire-de-porte-torcheres-retour-degypte/capture-decran-2024-12-07-104643/" data-orig-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-decran-2024-12-07-104643.png?fit=728%2C516&amp;ssl=1" data-orig-size="728,516" 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="https://www.proantic.com/galerie/uwe-dobler-interiors/" data-image-description="" data-image-caption="" data-medium-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-decran-2024-12-07-104643.png?fit=300%2C213&amp;ssl=1" data-large-file="https://i0.wp.com/www.proantic.com/magazine/wp-content/uploads/2024/12/Capture-decran-2024-12-07-104643.png?fit=665%2C471&amp;ssl=1">
Render time	411 ms
Elements that needed recalculate style before LCP	559
Time spent in recalculate style before LCP	16.402 ms
Load time	355 ms
URL	https://i0.wp.com/ww...-12-07-104643.png
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-17270 > 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-17270 > 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.

Detected Cumulative Layout Shift

0.00001 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.00001	<button class="searchsubmit" type="submit"></button>
body > div#page > div:eq(1) > div > div > div#site-content > div > div:eq(1) > div > aside#search-4 > form > div > button

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.

CDP Performance

Visual Elements

PageXray

How the page is built.

Largest assets on the page (by transfer size)

Requests and sizes per content type

Data per domain

Expires and last modified statistics

Requests loaded after onLoad event

Included requests done after load event end.

Requests loaded after onContentLoad

Includes requests done after DOM content loaded.

Render blocking requests

Render blocking information directly from Chrome.

Render information

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.

No long tasks on the page!

CPU time spent

Calculated using Tracium.

Third party

Third party requests categorised by Third party web version 0.24.0.

Third party requests and tools

First party requests and sizes per content type

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

Third party requests and sizes per content type

Screenshots

afterPageCompleteCheck.png

layoutShift.png

largestContentfulPaint.png

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