Page summary

Summary

Metric	Value
Page metrics
Performance Score	100
Total Page Transfer Size	75.0 KB
Requests	8
Timing metrics
TTFB [median]	498 ms
First Paint [median]	848 ms
Fully Loaded [median]	958 ms
Google Web Vitals
TTFB [median]	498 ms
First Contentful Paint (FCP) [median]	830 ms
Largest Contentful Paint (LCP) [median]	849 ms
Interaction To Next Paint (INP) [median]	176 ms
Visual Metrics
First Visual Change [median]	933 ms
Speed Index [median]	1.226 s
Visual Complete 85% [median]	933 ms
Visual Complete 99% [median]	9.266 s
Last Visual Change [median]	10.333 s

Timings Summary

Waterfall

Run 3 SpeedIndex median

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.9 sFirst Contentful Paint 864 msLCP <IMG> 873 msDOM Content Loaded Time 887 msPage Load Time 895 ms

1 sFirst Visual Change 966 msVisual Complete 85% 966 msVisual Complete 95% 966 msLargest Image 966 msHeading 966 msFully Loaded 988 ms

1.1 s

2 s

2.1 s

2.2 s

2.3 s

3.1 s

3.2 s

4.3 s

5.6 s

5.7 s

6.8 s

8 s

8.1 s

9.2 s

9.3 sVisual Complete 99% 9.300 s

9.5 s

10.4 sLast Visual Change 10.333 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 94
• Performance score 100
• Privacy score 88
• Best practice score 84

Performance advice (100)

You have a perfect Performance score!

Best practice advice (84)

Show/hide details

Title	Advice	Score
Cumulative Layout Shift (cumulativeLayoutShift)	Layout Shift is not supported in this browser	0
Description: Cumulative Layout Shift measures the sum total of all individual layout shift scores for unexpected layout shift that occur. The metric is measuring visual stability by quantify how often users experience unexpected layout shifts. It is one of Google Web Vitals.
Avoid unnecessary headers (unnecessaryHeaders)	There are 5 responses that sets both a max-age and expires header. There are 8 responses that sets a server header.	87
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.wikipedia.org/ https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png 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/sprite-de847d1a.svg https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister.png https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister.png https://www.wikipedia.org/static/apple-touch/wikipedia.png https://www.wikipedia.org/static/apple-touch/wikipedia.png https://www.wikipedia.org/static/favicon/wikipedia.ico https://www.wikipedia.org/static/favicon/wikipedia.ico

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	1920
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	unknown

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.6	100	Web servers
HSTS	100	Security
HTTP/2	100	Miscellaneous

Data from run 3

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	873 ms
Element render delay	135 ms
TTFB	524 ms
Resource delay	75 ms
Resource load duration	138 ms
Load time	811 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.

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

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

CPU