Run 4 summary

Summary

Metric	Value
Page metrics
Performance score	98
Total page size	71.7 KB
Requests	7
Timing metrics
TTFB	489 ms
First Paint	904 ms
Fully Loaded	953 ms
Google Web Vitals
TTFB	489 ms
First Contentful Paint (FCP)	904 ms
Largest Contentful Paint (LCP)	904 ms
Cumulative Layout Shift (CLS)	0.00
CPU metrics
CPU long tasks	1
CPU last long task happens at	508 ms
Visual Metrics
First Visual Change	900 ms
Speed Index	1.167 s
Visual Complete 85%	900 ms
Visual Complete 99%	9.233 s
Last Visual Change	11.033 s

Waterfall

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.6 sCPU Long Task duration 313 ms

0.9 sDOM Content Loaded Time 843 msPage Load Time 852 msFirst Visual Change 900 msVisual Complete 85% 900 msVisual Complete 95% 900 msLargest Image 900 msHeading 900 ms

1 sFirst Contentful Paint 904 msLCP <IMG> 904 msFully Loaded 953 ms

1.5 s

2.1 s

2.7 s

3.3 s

3.9 s

4.5 s

5.1 s

5.7 s

6.3 s

6.9 s

7.5 s

8.1 s

8.7 s

9.3 sVisual Complete 99% 9.233 s

9.4 s

9.9 s

10.5 s

11.1 sLast Visual Change 11.033 s

Coach

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

Coach score

• Total score 95
• Performance score 98
• Privacy score 88
• Best practice score 100

Performance advice (98)

Show/hide details

Title	Advice	Score
Avoid slowing down the critical rendering path (avoidRenderBlocking)	The page has 1 blocking requests and 1 in body parser blocking (2 JavaScript and 0 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.wikipedia.org/portal/wikipedia.org/assets/js/index-6bf78c58fd.js https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-ce3fe8e88d.js
Have a fast largest contentful paint (largestContentfulPaint)	You can add fetchPriority="high" to the image to increase the load priority in Chrome.	95
Description: Largest contentful paint is one of Google Web Vitals and reports the render time of the largest image or text block visible within the viewport, relative to when the page first started loading. To be fast according to Google, it needs to render before 2.5 seconds and results over 4 seconds is poor performance.
Avoid CPU Long Tasks (longTasks)	The page has 1 CPU long task with the total of 313 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 313 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
Long cache headers is good (cacheHeadersLong)	The page has 5 requests that have a shorter cache time than 30 days (but still a cache time).	95
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.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-6bf78c58fd.js https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-ce3fe8e88d.js https://www.wikipedia.org/portal/wikipedia.org/assets/img/sprite-de847d1a.svg https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister.png

Best practice advice (100)

Your best practice score is perfect!

Privacy advice (88)

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.wikipedia.org/
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.wikipedia.org/

Page info

Page info
Title	Wikipedia
Width	1904
Height	1193
DOM elements	1046
Avg DOM depth	9
Max DOM depth	12
Iframes	0
Script tags	4
Local storage	94 B
Session storage	0 b
Network Information API	4g

Resource Hints
preconnect
https://upload.wikimedia.org/
https://en.wikipedia.org/

Technologies used to build the page.

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

Technology	Confidence	Category
Apache Traffic Server 9.2.9	100	Web servers
HSTS	100	Security

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 class="central-featured-logo" src="portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png" srcset="portal/wikipedia.org/assets/img/Wikipedia-logo-v2@1.5x.png 1.5x, portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.png 2x" width="200" height="183" alt="">
Render time	904 ms
Element render delay	285 ms
TTFB	489 ms
Resource delay	8 ms
Resource load duration	123 ms
Elements that needed recalculate style before LCP	1899
Time spent in recalculate style before LCP	25.173 ms
Load time	822 ms
URL	https://www.wikipedi...pedia-logo-v2.png
Size (width*height)	36600
DOM path
main > div:eq(0) > img> main > div:eq(0) > 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

No layout shift detected.

Long Animation Frames

Read more about the Long Animation Frames API here here.

The top 10 longest animation frames entries

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

Console log

No console log messages.

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.

CPU last long task happened at 508 ms

Individual Long Tasks

CPU time spent

Calculated using Tracium.

Screenshots

afterPageCompleteCheck.jpg

layoutShift.jpg

largestContentfulPaint.jpg