| Avoid slowing down the critical rendering path (avoidRenderBlocking) | The page has 2 blocking requests and 0 in body parser blocking (0 JavaScript and 2 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://www.wikidata.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector | 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. |
| Offenders: https://www.wikidata.org/w/load.php...ta.org/w/load.php |
| 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://www.wikidata.org/static/images/footer/wikimedia-button.svg https://www.wikidata.org/w/resources/assets/poweredby_mediawiki.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. |
| Have a fast largest contentful paint (largestContentfulPaint) | You can add fetchPriority="high" to the image to increase the load priority in Chrome. | 95 |
| 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. |
| Avoid CPU Long Tasks (longTasks) | The page has 2 CPU long tasks with the total of 212 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 162 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. | 60 |
| 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: unknownself |
| Avoid doing redirects (assetsRedirects) | The page has 1 redirect. 1 of the redirects are from the base domain, please fix them! | 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://www.wikidata.org/wiki/Special:CentralAutoLogin/start?type=script |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 24 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 216.3 kB the next access. | 0 |
| 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/a/a3/Wikidata_nodes_in_whit..._in_white.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/9/97/The_Earth_seen_from_Ap...rom_Apollo_17.jpg https://upload.wikimedia.org/wikipedia/commons/thumb/d/da/Ruler_image.jpg/187px-Ruler_image.jpg https://upload.wikimedia.org/wikipedia/commons/thumb/b/b3/Everest_North_Face_tow..._%28square%29.jpg https://upload.wikimedia.org/wikipedia/commons/thumb/2/21/Mariinsky_-_La_Bayad%C...8Shklyarov%29.jpg https://upload.wikimedia.org/wikipedia/commons/thumb/b/b2/Wikidata-music-logo-en...c-logo-en.svg.png https://upload.wikimedia.org/wikipedia/commons/5/54/Wikidata-logo_white.svg https://upload.wikimedia.org/wikipedia/commons/thumb/8/81/Wikimedia-logo.svg/45p...edia-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/8/80/Wikipedia-logo-v2.svg/...a-logo-v2.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/e/ec/Wiktionary-logo.svg/20...nary-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/f/fa/Wikibooks-logo.svg/21p...ooks-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/2/24/Wikinews-logo.svg/26px...news-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/f/fa/Wikiquote-logo.svg/20p...uote-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/4/4c/Wikisource-logo.svg/20...urce-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/0/0b/Wikiversity_logo_2017....logo_2017.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Wikivoyage-Logo-v3-ico...o-v3-icon.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/d/df/Wikispecies-logo.svg/2...cies-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/0/0c/Wikifunctions-logo.svg...ions-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/4/4a/Commons-logo.svg/18px-Commons-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/e/e3/Incubator-logo.svg/20p...ator-logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Wikimedia_Community_Lo...nity_Logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/c/c6/MediaWiki-2020-small-i...mall-icon.svg.png https://www.wikidata.org/wiki/Special:CentralAutoLogin/start?type=script https://login.wikimedia.org/wiki/Special:CentralAutoLogin/checkLoggedIn...gin/checkLoggedIn |
| Long cache headers is good (cacheHeadersLong) | The page has 3 requests that have a shorter cache time than 30 days (but still a cache time). | 97 |
| 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://www.wikidata.org/w/load.php...ta.org/w/load.php https://www.wikidata.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector https://www.wikidata.org/w/load.php?lang=en&modules=site.styles&only=styles&skin=vector |
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 655.7 kB and the uncompressed size is 2.8 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: |
| Make each CSS response small (optimalCssSize) | https://www.wikidata.org/w/load.php?lang=en&modules=codex-search-styles%7Cext.discussionTools.init.styles%7Cext.uls.pt%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cmediawiki.page.gallery.styles%7Cmediawiki.widgets.styles%7Coojs-ui-core.icons%2Cstyles%7Coojs-ui.styles.indicators%7Cskins.vector.styles.legacy%7Cwikibase.client.init&only=styles&skin=vector size is 28.7 kB (28746) 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 3 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. | 80 |
| 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://www.wikidata.org/wiki/Wikidata:Main_Page https://www.wikidata.org/wiki/Special:CentralAutoLogin/start?type=script https://login.wikimedia.org/wiki/Special:CentralAutoLogin/checkLoggedIn...gin/checkLoggedIn |
0 s
0.9 smwStartup 856 msDOM Content Loaded Time 865 msFirst Contentful Paint 883 msFirst Visual Change 900 ms
1 s
1.1 s
1.2 sVisual Complete 85% 1.133 s
1.3 s
1.8 sLayout Shift 0.00067 1.735 sLast Visual Change 1.800 s
