Run 3 summary

Summary

Metric	Value
Page metrics
Performance score	87
Total page size	372.7 KB
Requests	12
Timing metrics
TTFB	119 ms
First Paint	480 ms
Fully Loaded	3.788 s
Google Web Vitals
TTFB	119 ms
First Contentful Paint (FCP)	480 ms
Largest Contentful Paint (LCP)	840 ms
Cumulative Layout Shift (CLS)	0.29
Total Blocking Time	1.212 s
Max Potential FID	500 ms
CPU metrics
CPU long tasks	14
CPU last long task happens at	4.360 s
Visual Metrics
First Visual Change	500 ms
Speed Index	3.068 s
Visual Complete 85%	4.367 s
Visual Complete 99%	12.800 s
Last Visual Change	13.467 s

Waterfall

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.3 sCPU Long Task duration 57 msmwStartup 264 ms

0.4 sCPU Long Task duration 94 ms

0.5 sFirst Contentful Paint 480 msFirst Visual Change 500 msLargest Image 500 ms

0.6 s

0.7 s

0.8 sCPU Long Task duration 66 ms

0.9 sLCP <P> 840 ms

1 sCPU Long Task duration 61 msCPU Long Task duration 73 ms

1.1 sCPU Long Task duration 68 ms

1.2 s

1.3 s

1.5 s

1.6 s

2.4 sCPU Long Task duration 217 ms

2.5 sDOM Content Loaded Time 2.461 s

2.6 sPage Load Time 2.557 s

2.7 s

2.8 sCPU Long Task duration 114 ms

3 sCPU Long Task duration 500 ms

3.5 sCPU Long Task duration 55 ms

3.6 sCPU Long Task duration 111 ms

3.8 sCPU Long Task duration 270 msFully Loaded 3.788 s

4 sCPU Long Task duration 180 ms

4.2 s

4.3 smwCentralNoticeBanner 4.257 sLayout Shift 0.29473 4.297 s

4.4 sHeading 4.334 sCPU Long Task duration 97 msVisual Complete 85% 4.367 s

4.5 s

4.6 s

4.7 s

4.8 s

4.9 s

5 s

5.1 s

5.2 s

5.3 s

5.4 s

5.5 s

5.6 s

5.7 s

5.8 s

5.9 s

6 s

6.1 s

6.2 s

6.3 s

6.4 s

6.5 s

6.6 s

6.7 s

6.8 s

6.9 s

7 s

7.1 s

7.2 s

7.3 s

7.4 s

7.5 s

7.6 s

7.7 s

7.8 s

7.9 s

8 s

8.1 s

8.2 s

8.3 s

8.4 s

8.5 s

8.6 s

8.7 s

8.8 s

8.9 s

9 s

9.1 s

9.2 s

9.3 s

9.4 s

9.5 s

9.6 s

9.7 s

9.8 s

9.9 s

10 s

10.1 s

10.2 s

10.3 s

10.4 s

10.5 s

10.6 s

10.7 s

10.8 s

10.9 s

11 s

11.1 s

11.2 s

11.3 s

11.4 s

11.5 s

11.6 s

11.7 s

11.8 s

11.9 s

12 s

12.1 s

12.2 s

12.3 s

12.4 s

12.5 s

12.6 s

12.7 sVisual Complete 95% 12.667 s

12.8 sVisual Complete 99% 12.800 s

12.9 s

13 s

13.1 s

13.2 s

13.3 s

13.4 s

13.5 sLast Visual Change 13.467 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 85
• Performance score 87
• Privacy score 88
• Best practice score 74

Performance advice (87)

Show/hide details

Title	Advice	Score
Don't scale images in the browser (avoidScalingImages)	The page has 2 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them.	80
Description: It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one.
Offenders: https://en.m.wikipedia.org/static/images/mobile/copyright/wikipedia-wordmark-en.svg https://en.m.wikipedia.org/static/images/mobile/copyright/wikipedia-wordmark-en.svg
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 14 CPU long tasks with the total of 1.963 s. The total blocking time is 1.212 s and 2 long tasks before first contentful paint with total time of 151 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.	0
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: self unknown unknown unknown self unknown self self self self self self self self
Avoid doing redirects (assetsRedirects)	The page has 1 redirect. 1 request are from other domains, it could be 3rd-party assets doing unnecessary redirects. :(	90
Description: A redirect is one extra step for the user to download the asset. Avoid that if you want to be fast. Redirects are even more of a showstopper on mobile.
Offenders: https://meta.wikimedia.org/w/index.php...a.org/w/index.php
Avoid extra requests by setting cache headers (cacheHeaders)	The page has 4 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 50.1 kB the next access.	60
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://upload.wikimedia.org/wikipedia/commons/thumb/8/8d/President_Barack_Obama..._Barack_Obama.jpg https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Barack_Obama_signature...signature.svg.png https://meta.wikimedia.org/w/index.php...a.org/w/index.php https://meta.m.wikimedia.org/w/index.php...a.org/w/index.php
Long cache headers is good (cacheHeadersLong)	The page has 1 request that have a shorter cache time than 30 days (but still a cache time).	99
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://en.m.wikipedia.org/w/load.php...ia.org/w/load.php
Always compress text content (compressAssets)	The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.	90
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://meta.m.wikimedia.org/w/index.php...a.org/w/index.php 2.3 KB 4.8 KB
Make each CSS response small (optimalCssSize)	https://en.m.wikipedia.org/w/load.php?lang=en&modules=ext.cite.styles%7Cext.phonos.icons%2Cstyles%7Cext.relatedArticles.styles%7Cext.tmh.player.styles%7Cext.wikimediaBadges%7Cext.wikimediamessages.styles%7Cmediawiki.hlist%7Cmobile.init.styles%7Cskins.minerva.amc.styles%7Cskins.minerva.codex.styles%7Cskins.minerva.content.styles.images%7Cskins.minerva.icons%2Cstyles%7Cwikibase.client.init&only=styles&skin=minerva size is 18.2 kB (18216) 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://en.m.wikipedia.org/w/load.php...ia.org/w/load.php 17.8 KB 125.3 KB

Best practice advice (74)

Show/hide details

Title	Advice	Score
Cumulative Layout Shift (cumulativeLayoutShift)	You have a poor cumulative layout shift score (0.2947). It is in the Google Web Vitals poor range, with a shift higher than 0.25. You should manually check the filmstrip or video and check if it will affect the user.	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.
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 unnecessary headers (unnecessaryHeaders)	There are 7 responses that sets both a max-age and expires header. There are 12 responses that sets a server header.	81
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.m.wikipedia.org/wiki/Barack_Obama https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://upload.wikimedia.org/wikipedia/commons/thumb/8/8d/President_Barack_Obama..._Barack_Obama.jpg https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Barack_Obama_signature...signature.svg.png https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://en.m.wikipedia.org/w/load.php...ia.org/w/load.php https://meta.wikimedia.org/w/index.php...a.org/w/index.php https://meta.m.wikimedia.org/w/index.php...a.org/w/index.php

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://en.m.wikipedia.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.m.wikipedia.org/wiki/Barack_Obama

Page info

Page info
Title	Barack Obama - Wikipedia
Generator	MediaWiki 1.44.0-wmf.16
Width	360
Height	6808
DOM elements	13713
Avg DOM depth	14
Max DOM depth	23
Iframes	0
Script tags	7
Local storage	787.2 KB
Session storage	0 b
Network Information API	4g

Resource Hints
dns-prefetch
https://meta.wikimedia.org/
https://en.m.wikipedia.org/wiki/login.wikimedia.org
preconnect
https://upload.wikimedia.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
MediaWiki	100	Wikis
PHP	100	Programming languages
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></p>
Render time	840 ms
Element render delay	722 ms
TTFB	119 ms
Resource delay	0 ms
Resource load duration	0 ms
Elements that needed recalculate style before LCP	240
Time spent in recalculate style before LCP	68.855 ms
Load time	0 ms
Size (width*height)	75725
DOM path
div#mw-mf-viewport > div#mw-mf-page-center > main#content > div#bodyContent > div#mw-content-text > div:eq(0) > section#mf-section-0 > p:eq(1)> div#mw-mf-viewport > div#mw-mf-page-center > main#content > div#bodyContent > div#mw-content-text > div:eq(0) > section#mf-section-0 > 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

0.29473 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.29473	<div class="pre-content heading-holder"></div>,<ul id="p-views" class="page-actions-menu__list"></ul>,<div id="bodyContent" class="content"></div>,<table class="infobox vcard"></table>
body > div#mw-mf-viewport > div#mw-mf-page-center > main#content > div:eq(1),body > div#mw-mf-viewport > div#mw-mf-page-center > main#content > div:eq(1) > nav > ul#p-views,body > div#mw-mf-viewport > div#mw-mf-page-center > main#content > div#bodyContent,body > div#mw-mf-viewport > div#mw-mf-page-center > main#content > div#bodyContent > div#mw-content-text > div:eq(0) > section#mf-section-0 > table

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.

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.

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 4.360 s

Individual Long Tasks

CPU time spent

Calculated using Tracium.

Time spent per request

Screenshots

afterPageCompleteCheck.jpg

layoutShift.jpg

largestContentfulPaint.jpg