| Don't scale images in the browser (avoidScalingImages) | The page has 4 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. | 60 |
| 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.svg https://auth.wikimedia.org/static/images/mobile/copyright/wikipedia-tagline-en.svg https://auth.wikimedia.org/static/images/footer/wikimedia-button.svg https://auth.wikimedia.org/enwiki/w/resources/assets/poweredby_mediawiki.svg |
| Have a fast first contentful paint (firstContentfulPaint) | First contentful paint can be improved (2.610 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.678 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: https://en.wikipedia.org/w/resources/src/mediawiki.special.userlogin.login.style...-people-large.png |
| 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 3 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 13.1 kB the next access. | 70 |
| 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://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/wiki/Special:UserLogin...Special:UserLogin |
| 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 |
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 199.1 kB. This is quite large. | 50 |
| 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: |
| Make each CSS response small (optimalCssSize) | https://en.wikipedia.org/w/load.php?lang=en&modules=ext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cmediawiki.codex.messagebox.styles%7Cmediawiki.htmlform.codex.styles%7Cmediawiki.htmlform.styles%7Cmediawiki.special.userlogin.common.styles%7Cmediawiki.special.userlogin.login.styles%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles&only=styles&skin=vector-2022 size is 30.7 kB (30711) 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: |
| Don't use private headers on static content (privateAssets) | The page has 1 request with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 90 |
| 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://auth.wikimedia.org/enwiki/wiki/Special:UserLogin...Special:UserLogin |
0 s
2.7 sFirst Contentful Paint 2.610 sFirst Visual Change 2.667 sVisual Complete 85% 2.667 sHeading 2.667 sLCP <DIV> mw-createaccount-cta 2.678 s
2.8 s
2.9 s
3 sPage Load Time 2.915 sLargest Image 2.933 sVisual Complete 95% 2.967 s
3.1 sFully Loaded 3.054 s
3.2 s
3.3 s
3.4 s
11 sVisual Complete 99% 11.000 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 sLast Visual Change 12.233 s
