Run 4 summary

Summary

Metric	Value
Page metrics
Performance score	97
Total page size	10.1 KB
Requests	3
Timing metrics
TTFB	689 ms
First Paint	748 ms
Fully Loaded	1.285 s
Google Web Vitals
TTFB	689 ms
First Contentful Paint (FCP)	748 ms
Largest Contentful Paint (LCP)	748 ms
Cumulative Layout Shift (CLS)	0.00
Visual Metrics
First Visual Change	733 ms
Speed Index	741 ms
Visual Complete 85%	733 ms
Visual Complete 99%	1.133 s
Last Visual Change	1.133 s

Waterfall

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.7 sDOM Content Loaded Time 700 ms

0.8 sFirst Visual Change 733 msVisual Complete 85% 733 msVisual Complete 95% 733 msFirst Contentful Paint 748 msLCP <P> 748 ms

1.1 sPage Load Time 1.092 s

1.2 sLast Visual Change 1.133 sVisual Complete 99% 1.133 sLargest Image 1.133 sHeading 1.133 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 90
• Performance score 97
• Privacy score 82
• Best practice score 83

Performance advice (97)

Show/hide details

Title	Advice	Score
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 3 kB 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://en.wikipedia.beta.wmflabs.org/favicon.ico
Always compress text content (compressAssets)	The page has 2 requests that are served uncompressed. You could save a lot of bytes by sending them compressed instead.	80
Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.
Offenders: URL Transfer size Content size https://en.wikipedia.beta.wmflabs.org/wiki/Barack_Obama 2.9 KB 2.2 KB https://en.wikipedia.beta.wmflabs.org/favicon.ico 2.9 KB 2.2 KB
Avoid missing and error requests (responseOk)	The page has 2 error responses. The page has 2 responses with code 403.	80
Description: Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it.
Offenders: https://en.wikipedia.beta.wmflabs.org/wiki/Barack_Obama https://en.wikipedia.beta.wmflabs.org/favicon.ico

Best practice advice (83)

Show/hide details

Title	Advice	Score
Meta description (metaDescription)	The page is missing a meta description.	0
Description: Use a page description to make the page more relevant to search engines.
Avoid too many third party requests (thirdParty)	The page do 33% requests to third party domains (1 requests and 4.4 kB). First party is 2 requests and 6 kB. The regex .*wmflabs.* was used to calculate first/third party requests.	50
Description: Do not load most of your content from third party URLs.
Avoid unnecessary headers (unnecessaryHeaders)	There are 1 response that sets both a max-age and expires header. There are 3 responses that sets a server header.	96
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://en.wikipedia.beta.wmflabs.org/wiki/Barack_Obama https://www.wikimedia.org/static/images/wmf-logo.png https://www.wikimedia.org/static/images/wmf-logo.png https://en.wikipedia.beta.wmflabs.org/favicon.ico

Privacy advice (82)

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://en.wikipedia.beta.wmflabs.org/wiki/Barack_Obama
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://en.wikipedia.beta.wmflabs.org/wiki/Barack_Obama
Avoid third party cookies that is used to track the user. (thirdPartyCookies)	The page sets 1 third party cookie.	0
Description: Third party cookies are used to track the user. They are automatically blocked in Safari and Firefox.
Offenders: .wikipedia.org

Page info

Page info
Title	Wikimedia Error
Width	1919
Height	992
DOM elements	25
Avg DOM depth	4
Max DOM depth	6
Iframes	0
Script tags	0
Local storage	0 b
Session storage	0 b
Network Information API	4g

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
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	P
Element/tag	<p class="text-muted"></p>
Render time	748 ms
Element render delay	59 ms
TTFB	689 ms
Resource delay	0 ms
Resource load duration	0 ms
Elements that needed recalculate style before LCP	26
Time spent in recalculate style before LCP	0.546 ms
Load time	0 ms
Size (width*height)	34632
DOM path
div:eq(1) > p:eq(1)> div:eq(1) > p:eq(1)>

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.

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

The page logs the following messages to the console.

Requests loaded after onLoad event

Included requests done after load event end.

Requests loaded after onContentLoad

Includes requests done after DOM content loaded.

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 time spent

Calculated using Tracium.

Screenshots

afterPageCompleteCheck.jpg

layoutShift.jpg

largestContentfulPaint.jpg