Page summary

Summary

Metric	Value
Page metrics
Performance Score	73
Total Page Transfer Size	426.0 KB
Requests	24
Timing metrics
TTFB [median]	1.864 s
First Paint [median]	2.440 s
Fully Loaded [median]	8.875 s
Google Web Vitals
TTFB [median]	1.864 s
First Contentful Paint (FCP) [median]	2.440 s
Largest Contentful Paint (LCP) [median]	2.596 s
Cumulative Layout Shift (CLS) [median]	0.00
Total Blocking Time [median]	319 ms
Max Potential FID [median]	239 ms
CPU metrics
CPU long tasks [median]	6
CPU longest task duration	239 ms
CPU last long task happens at	3.797 s
Visual Metrics
First Visual Change [median]	2.433 s
Speed Index [median]	3.041 s
Visual Complete 85% [median]	2.700 s
Visual Complete 99% [median]	7.033 s
Last Visual Change [median]	18.866 s

Timings Summary

Waterfall

Run 1 SpeedIndex median

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

2.4 sCPU Long Task duration 111 ms

2.5 sFirst Visual Change 2.433 sHeading 2.433 sFirst Contentful Paint 2.440 s

2.6 sLCP <P> 2.596 s

2.7 sCPU Long Task duration 76 msDOM Content Loaded Time 2.695 sVisual Complete 85% 2.700 sLargest Image 2.700 s

2.8 smwStartup 2.731 s

2.9 s

3 s

3.1 s

3.2 sPage Load Time 3.184 sCPU Long Task duration 239 ms

3.3 s

3.4 s

3.5 sCPU Long Task duration 75 ms

3.6 s

3.7 sCPU Long Task duration 89 ms

3.8 sCPU Long Task duration 90 ms

3.9 s

4 s

4.1 s

4.2 s

4.3 s

4.4 s

4.5 s

4.6 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 sVisual Complete 95% 7.033 sVisual Complete 99% 7.033 s

7.2 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 sFully Loaded 8.875 s

9 s

9.1 s

9.2 s

9.3 s

9.4 s

9.5 s

9.6 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.3 s

12.4 s

12.5 s

12.6 s

12.7 s

12.8 s

12.9 s

13 s

13.1 s

13.2 s

13.3 s

13.4 s

13.5 s

13.6 s

13.7 s

13.8 s

13.9 s

14 s

14.1 s

14.2 s

14.3 s

14.4 s

14.7 s

14.8 s

14.9 s

15 s

15.1 s

15.2 s

15.3 s

15.4 s

15.5 s

15.6 s

15.7 s

15.8 s

15.9 s

16 s

16.1 s

16.2 s

16.3 s

16.4 s

16.5 s

16.6 s

16.7 s

16.8 s

17.1 s

17.2 s

17.3 s

17.4 s

17.5 s

17.6 s

17.7 s

17.8 s

17.9 s

18 s

18.1 s

18.2 s

18.3 s

18.4 s

18.5 s

18.6 s

18.7 s

18.8 s

18.9 sLast Visual Change 18.866 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.3.

Coach score

• Total score 77
• Performance score 73
• Privacy score 87
• Best practice score 72

Performance advice (73)

Show/hide details

Title	Advice	Score
Avoid slowing down the critical rendering path (avoidRenderBlocking)	The page has 1 blocking requests and 0 in body parser blocking (0 JavaScript and 1 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://en.wikipedia.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&safemode=1&skin=minerva	99
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.
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://auth.wikimedia.org/static/images/mobile/copyright/wikipedia-wordmark-en-25.svg https://auth.wikimedia.org/static/images/mobile/copyright/wikipedia-wordmark-en-25.svg
Have a fast first contentful paint (firstContentfulPaint)	First contentful paint can be improved (2.440 s). It is in the Google Web Vitals needs improvement range, slower than 1.8 seconds.	50
Description: The First Contentful Paint (FCP) metric measures the time from when the page starts loading to when any part of the page content is rendered on the screen. For this metric, "content" refers to text, images (including background images), <svg> elements, or non-white <canvas> elements.
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.
Have a fast largest contentful paint (largestContentfulPaint)	Largest contentful paint can be improved 2.596 s. It is in the Google Web Vitals needs improvement range, slower than 2.5 seconds.	80
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.
Offenders: <p></p>
Avoid CPU Long Tasks (longTasks)	The page has 6 CPU long tasks with the total of 680 ms. The total blocking time is 319 ms and 1 long task before first contentful paint with total time of 111 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: unknown unknown self self self self
Avoid Frontend single point of failures (spof)	The page has 1 request inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head.	90
Description: A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag.
Offenders: https://en.wikipedia.org/w/load.php...ia.org/w/load.php
Avoid doing redirects (assetsRedirects)	The page has 2 redirects. 1 of the redirects are from the base domain, please fix them! 1 request are from other domains, it could be 3rd-party assets doing unnecessary redirects. :(	80
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://auth.wikimedia.org/metawiki/wiki/Special:CentralAutoLogin/checkLoggedIn...gin/checkLoggedIn https://en.wikipedia.org/w/index.php...a.org/w/index.php
Avoid extra requests by setting cache headers (cacheHeaders)	The page has 5 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 18.3 kB the next access.	50
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.org/w/index.php?title=Special:UserLogin&returnto=Main+Page https://auth.wikimedia.org/metawiki/wiki/Special:CentralAutoLogin/checkLoggedIn...gin/checkLoggedIn https://en.wikipedia.org/w/index.php...a.org/w/index.php https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest
Long cache headers is good (cacheHeadersLong)	The page has 2 requests that have a shorter cache time than 30 days (but still a cache time).	98
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.wikipedia.org/w/load.php...ia.org/w/load.php https://en.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://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin 12.2 KB 25.2 KB
Avoid redirecting the main document (documentRedirect)	The main document gets redirected 3 time(s). Remove those redirect and make the page faster!	0
Description: You should never ever redirect the main document, because it will make the page load slower for the user. Well, you should redirect the user if the user tries to use HTTP and there's an HTTPS version of the page. The coach checks for that. :)
Offenders: https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=Main+Page https://auth.wikimedia.org/metawiki/wiki/Special:CentralAutoLogin/checkLoggedIn...gin/checkLoggedIn https://en.wikipedia.org/w/index.php...a.org/w/index.php
Total JavaScript size shouldn't be too big (javascriptSize)	The total JavaScript transfer size is 304.4 kB and the uncompressed size is 1.3 MB. This is totally crazy! There is really room for improvement here.	0
Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?
Offenders: URL Transfer size Content size https://en.wikipedia.org/w/load.php...ia.org/w/load.php 20.5 KB 61.4 KB https://en.wikipedia.org/w/load.php...ia.org/w/load.php 9.1 KB 24.9 KB https://en.wikipedia.org/w/load.php...ia.org/w/load.php 267.6 KB 1.2 MB
Make each CSS response small (optimalCssSize)	https://en.wikipedia.org/w/load.php?lang=en&modules=ext.webauthn.ui.base.styles%7Cext.wp25EasterEggs.styles%7Cmediawiki.codex.messagebox.styles%7Cmediawiki.hlist%7Cmediawiki.htmlform.codex.styles%7Cmediawiki.htmlform.styles%7Cmediawiki.special.userlogin.common.styles%7Cmediawiki.special.userlogin.login.styles%7Cmobile.init.styles%7Cmobile.special.styles%7Cskins.minerva.amc.styles%7Cskins.minerva.codex.styles%7Cskins.minerva.content.styles.images%7Cskins.minerva.icons%2Cstyles&only=styles&skin=minerva size is 30.7 kB (30743) 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.wikipedia.org/w/load.php...ia.org/w/load.php 30.0 KB 270.3 KB
Don't use private headers on static content (privateAssets)	The page has 5 requests with private headers. The main page has a private header. It could be right in some cases where the user can be logged in and served specific content. But if your asset is static it should never be private. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.	60
Description: If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private.
Offenders: https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=Main+Page https://en.wikipedia.org/w/index.php...a.org/w/index.php https://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest

Best practice advice (72)

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.
Have a good URL format (url)	The page is using more than two request parameters. You should really rethink and try to minimize the number of parameters. The URL is 198 characters long. Try to make it less than 100 characters.	40
Description: A clean URL is good for the user and for SEO. Make them human readable, avoid too long URLs, spaces in the URL, too many request parameters, and never ever have the session id in your URL.
Do not send too long headers (longHeaders)	https://en.wikipedia...a.org/w/index.php has a header content-security-policy that is 1388 characters long. https://en.wikipedia...a.org/w/index.php has a header content-security-policy-report-only that is 1397 characters long. https://en.wikipedia...a.org/w/index.php has a header content-security-policy that is 1388 characters long. https://en.wikipedia...a.org/w/index.php has a header content-security-policy-report-only that is 1397 characters long. https://auth.wikimed...Special:UserLogin has a header content-security-policy that is 1388 characters long. https://auth.wikimed...Special:UserLogin has a header content-security-policy-report-only that is 1397 characters long. https://auth.wikimed...Special:UserLogin has a header set-cookie that is 616 characters long. https://auth.wikimed.../enwiki/w/api.php has a header content-security-policy that is 1597 characters long. https://auth.wikimed.../enwiki/w/api.php has a header content-security-policy-report-only that is 1610 characters long. https://en.wikipedia...ia.org/w/load.php has a header sourcemap that is 1188 characters long. https://auth.wikimed.../enwiki/w/api.php has a header content-security-policy that is 1597 characters long. https://auth.wikimed.../enwiki/w/api.php has a header content-security-policy-report-only that is 1610 characters long.	88
Description: Do not send response headers that are too long.
Offenders: https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=Main+Page https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=Main+Page https://en.wikipedia.org/w/index.php...a.org/w/index.php https://en.wikipedia.org/w/index.php...a.org/w/index.php https://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin https://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin https://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest
Avoid too many third party requests (thirdParty)	The page do more requests to third party domains (14 requests and 349.5 kB) then first party (10 requests and 86.7 kB). The page transfer more bytes from third party domains (349.5 kB) then first party (86.7 kB). The regex .*wikimedia.* 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 20 responses that sets both a max-age and expires header. There are 24 responses that sets a server header.	56
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.org/w/index.php?title=Special:UserLogin&returnto=Main+Page https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=Main+Page https://auth.wikimedia.org/metawiki/wiki/Special:CentralAutoLogin/checkLoggedIn...gin/checkLoggedIn https://en.wikipedia.org/w/index.php...a.org/w/index.php https://en.wikipedia.org/w/index.php...a.org/w/index.php https://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin https://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://auth.wikimedia.org/static/images/icons/enwiki-25.svg https://auth.wikimedia.org/static/images/icons/enwiki-25.svg https://auth.wikimedia.org/static/images/mobile/copyright/wikipedia-wordmark-en-25.svg https://auth.wikimedia.org/static/images/mobile/copyright/wikipedia-wordmark-en-25.svg https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/resources/src/mediawiki.special.userlogin.login.style...-people-large.png https://auth.wikimedia.org/static/images/footer/wikimedia.svg https://auth.wikimedia.org/static/images/footer/wikimedia.svg https://auth.wikimedia.org/enwiki/w/resources/assets/mediawiki_compact.svg https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://en.wikipedia.org/w/load.php...ia.org/w/load.php https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://auth.wikimedia.org/enwiki/w/api.php?action=webapp-manifest https://auth.wikimedia.org/static/favicon/wikipedia.ico https://auth.wikimedia.org/static/favicon/wikipedia.ico https://auth.wikimedia.org/ins-502b/v2/events?hasty=true

Privacy advice (87)

Show/hide details

Title	Advice	Score
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://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin
Avoid third party cookies that is used to track the user. (thirdPartyCookies)	The page sets 13 third party cookies.	0
Description: Third party cookies are used to track the user. They are automatically blocked in Safari and Firefox.
Offenders: .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org .wikipedia.org

Page info

Page info
Title	Log in - Wikipedia
Generator	MediaWiki 1.46.0-wmf.21
Width	360
Height	1221
DOM elements	228
Avg DOM depth	9
Max DOM depth	14
Iframes	0
Script tags	6
Local storage	65 B
Session storage	0 b
Network Information API	4g

Technologies used to build the page.

Data collected using Wappalyzer version 6.10.54. 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

Data from run 1

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	2.596 s
Element render delay	732 ms
TTFB	1.864 s
Resource delay	0 ms
Resource load duration	0 ms
Elements that needed recalculate style before LCP	421
Time spent in recalculate style before LCP	70.833 ms
Load time	0 ms
Size (width*height)	31392
DOM path
div#mw-mf-viewport > div#mw-mf-page-center > main#content > div#bodyContent > div#mw-content-text > div#userloginprompt > p> div#mw-mf-viewport > div#mw-mf-page-center > main#content > div#bodyContent > div#mw-content-text > div#userloginprompt > p>

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.

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.

CPU last long task happened at 3.797 s

Individual Long Tasks

CPU time spent

Calculated using Tracium.

Time spent per request