Tested 2025-04-05 18:22:58 using Chrome 134.0.6998.35 (runtime settings).
| Metric | Value |
|---|---|
| Page metrics | |
| Performance score | 77 |
| Total page size | 508.8 KB |
| Requests | 38 |
| Timing metrics | |
| TTFB | 488 ms |
| First Paint | 712 ms |
| Fully Loaded | 1.807 s |
| Google Web Vitals | |
| TTFB | 488 ms |
| First Contentful Paint (FCP) | 712 ms |
| Largest Contentful Paint (LCP) | 856 ms |
| Cumulative Layout Shift (CLS) | 0.04 |
| 160 ms | |
| CPU metrics | |
| CPU long tasks | 1 |
| CPU last long task happens at | 697 ms |
| Visual Metrics | |
| First Visual Change | 700 ms |
| Speed Index | 801 ms |
| Visual Complete 85% | 833 ms |
| Visual Complete 99% | 1.400 s |
| Last Visual Change | 1.433 s |
Use--filmstrip.showAll to show all filmstrips.
0 s
0.7 sCPU Long Task duration 94 msFirst Visual Change 700 ms
0.8 sFirst Contentful Paint 712 msLayout Shift 0.00330 784 ms
0.9 sDOM Content Loaded Time 807 msmwStartup 810 msVisual Complete 85% 833 msLCP <UL> 856 msLargest Image 866 ms
1 sVisual Complete 95% 933 ms
1.1 s
1.2 s
1.3 sPage Load Time 1.269 s
1.4 sLayout Shift 0.03771 1.318 sHeading 1.366 sVisual Complete 99% 1.400 s
1.5 sLast Visual Change 1.433 sThe 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.
| Title | Advice | Score | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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.mediawiki.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector-2022 | 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: | ||||||||||||||||||||||||||
| Don't scale images in the browser (avoidScalingImages) | The page has 1 image 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. | 90 | ||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| 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 1 CPU long task with the total of 94 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 94 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. | 80 | ||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 14 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 24.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: | ||||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 408.8 kB and the uncompressed size is 1.7 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.mediawiki.org/w/load.php?lang=en&modules=ext.discussionTools.init.styles%7Cext.dismissableSiteNotice.styles%7Cext.translate%7Cext.translate.edit.documentation.styles%7Cext.translate.tag.languages%7Cext.uls.pt%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediamessages.styles%7Cmediawiki.widgets.styles%7Coojs-ui-core.icons%2Cstyles%7Coojs-ui.styles.indicators%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles%7Cwikibase.client.init&only=styles&skin=vector-2022 size is 35.3 kB (35349) 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 4 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. | 70 | ||||||||||||||||||||||||
| 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: | ||||||||||||||||||||||||||
| 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: | ||
| 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: | ||
| Page info | |
|---|---|
| Title | How to contribute - MediaWiki |
| Generator | MediaWiki 1.44.0-wmf.23 |
| Width | 1904 |
| Height | 3452 |
| DOM elements | 1052 |
| Avg DOM depth | 12 |
| Max DOM depth | 20 |
| Iframes | 0 |
| Script tags | 6 |
| Local storage | 1.1 MB |
| Session storage | 0 b |
| Network Information API | 4g |
| Resource Hints |
|---|
| dns-prefetch |
| https://meta.wikimedia.org/ |
| https://www.mediawiki.org/wiki/auth.wikimedia.org |
| preconnect |
| https://upload.wikimedia.org/ |
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 | |
|---|---|
| First Visual Change | 700 ms |
| Speed Index | 801 ms |
| Largest Image | 866 ms |
| Heading | 1.366 s |
| LargestContentfulPaint | 1.366 s |
| Last Meaningful Paint | 1.366 s |
| Largest Contentful Paint | 1.366 s |
| Visual Complete 85% | 833 ms |
| Visual Complete 95% | 933 ms |
| Visual Complete 99% | 1.400 s |
| Last Visual Change | 1.433 s |
| Visual Readiness | 733 ms |
| Navigation Timing | |
|---|---|
| backEndTime | 488 ms |
| domContentLoadedTime | 807 ms |
| domInteractiveTime | 807 ms |
| domainLookupTime | 90 ms |
| frontEndTime | 760 ms |
| pageDownloadTime | 21 ms |
| pageLoadTime | 1.269 s |
| redirectionTime | 0 ms |
| serverConnectionTime | 201 ms |
| serverResponseTime | 216 ms |
| Google Web Vitals | |
|---|---|
| Time to first byte (TTFB) | 488 ms |
| First Contentful Paint (FCP) | 712 ms |
| Largest Contentful Paint (LCP) | 856 ms |
| Cumulative Layout Shift (CLS) | 0.04 |
| Interaction to next paint (INP) | 160 ms |
| Total Blocking Time (TBT) | 0 ms |
| First Contentful Paint info | |
|---|---|
| Elements that needed recalculate style before FCP | 1072 |
| Time spent in recalculate style before FCP | 27.666 ms |
| Extra timings | |
|---|---|
| TTFB | 488 ms |
| First Paint | 712 ms |
| Load Event End | 1.269 s |
| Fully loaded | 1.807 s |
| User Timing marks | |
|---|---|
| mwStartup | 810 ms |
When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.
| Element type | UL |
| Element/tag | <ul class="mw-pt-languages-list"></ul> |
| Render time | 856 ms |
| Element render delay | 368 ms |
| TTFB | 488 ms |
| Resource delay | 0 ms |
| Resource load duration | 0 ms |
| Elements that needed recalculate style before LCP | 1146 |
| Time spent in recalculate style before LCP | 29.109 ms |
| Load time | 0 ms |
| Size (width*height) | 234080 |
| DOM path | |
| div:eq(1) > div > div:eq(2) > main#content > div#bodyContent > div#mw-content-text > div:eq(1) > div:eq(0) > ul> div:eq(1) > div > div:eq(2) > main#content > div#bodyContent > div#mw-content-text > div:eq(1) > div:eq(0) > ul> | |
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.
0.04102 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.03771 | <div class="mw-content-container"></div> |
| body > div:eq(1) > div > div:eq(2) | |
| 0.00330 | <header class="vector-header mw-header"></header>,<div class="mw-page-container"></div> |
| body > div:eq(0) > header,body > div:eq(1) | |
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.
Interaction to Next Paint (INP) is a metric that try to measure responsiveness. It's useful if you are testing user journeys. Read more about Interaction to Next Paint.
The measured latency was 160 ms.
| Event type | pointerenter |
| Element type | HTML |
| Element class name | client-js vector-feature-language-in-header-disabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-disabled skin-theme-clientpref-day vector-sticky-header-enabled vector-toc-not-available vector-animations-ready ve-available ext-discussiontools-init-ready |
| Event target | html.client-js.vector-feature-language-in-header-disabled.vector-feature-language-in-main-page-header-disabled.vector-feature-page-tools-pinned-disabled.vector-feature-toc-pinned-clientpref-1.vector-feature-main-menu-pinned-disabled.vector-feature-limited-width-clientpref-1.vector-feature-limited-width-content-enabled.vector-feature-custom-font-size-clientpref-1.vector-feature-appearance-pinned-clientpref-1.vector-feature-night-mode-disabled.skin-theme-clientpref-day.vector-sticky-header-enabled.vector-toc-not-available.vector-animations-ready.ve-available.ext-discussiontools-init-ready |
| Load state when the event happened | loading |
Read more about the Long Animation Frames API here here.
The top 10 longest animation frames entries
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 47.8 ms | 11.8 ms | 87.6 ms | 87.3 ms | 0.3 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 170.4 ms | 21.3 ms | 0 ms | 21.3 ms |
| No availible script information. | ||||
| name | duration | description |
|---|---|---|
| cache | 0 | hit-front |
| host | 0 | cp3067 |
There are no custom configured scripts.
There are no custom extra metrics from scripting.
| name | value |
|---|---|
| AudioHandlers | 0 |
| AudioWorkletProcessors | 0 |
| Documents | 38 |
| Frames | 17 |
| JSEventListeners | 103 |
| LayoutObjects | 2078 |
| MediaKeySessions | 0 |
| MediaKeys | 0 |
| Nodes | 2795 |
| Resources | 39 |
| ContextLifecycleStateObservers | 45 |
| V8PerContextDatas | 3 |
| WorkerGlobalScopes | 0 |
| UACSSResources | 0 |
| RTCPeerConnections | 0 |
| ResourceFetchers | 38 |
| AdSubframes | 0 |
| DetachedScriptStates | 2 |
| ArrayBufferContents | 2 |
| LayoutCount | 12 |
| RecalcStyleCount | 19 |
| LayoutDuration | 82 |
| RecalcStyleDuration | 47 |
| DevToolsCommandDuration | 65 |
| ScriptDuration | 157 |
| V8CompileDuration | 3 |
| TaskDuration | 499 |
| TaskOtherDuration | 146 |
| ThreadTime | 1 |
| ProcessTime | 2 |
| JSHeapUsedSize | 10846268 |
| JSHeapTotalSize | 18075648 |
| FirstMeaningfulPaint | 855 |
| Name | Display Time | X | Y | Width | Height |
|---|---|---|---|---|---|
| LargestImage (mediawikiwiki.svg) | 866 ms | 246 | 8 | 50 | 50 |
| <img class="mw-logo-icon" src="/static/images/icons/mediawikiwiki.svg" alt="" aria-hidden="true" height="50" width="50"> | |||||
| Heading | 1.366 s | 342 | 191 | 948 | 40 |
| <h1 id="firstHeading" class="firstHeading mw-first-heading"></h1> | |||||
| LargestContentfulPaint | 1.366 s | 448 | 309 | 842 | 323 |
| <ul class="mw-pt-languages-list"></ul> | |||||
How the page is built.
| Summary | |
|---|---|
| HTTP version | HTTP/2.0 |
| Total requests | 38 |
| Total domains | 4 |
| Total transfer size | 508.8 KB |
| Total content size | 2.1 MB |
| Responses missing compression | 10 |
| Number of cookies | 1 |
| Third party cookies | 0 |
| Requests per response code | |
|---|---|
| 200 | 36 |
| 302 | 2 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 25.8 KB | 104.5 KB | 1 |
| css | 0 b | 35.9 KB | 287.1 KB | 2 |
| javascript | 0 b | 399.2 KB | 1.7 MB | 7 |
| image | 0 b | 22.6 KB | 13.0 KB | 11 |
| svg | 0 b | 17.2 KB | 17.3 KB | 14 |
| favicon | 0 b | 8.2 KB | 15.0 KB | 1 |
| Total | 0 b | 508.8 KB | 2.1 MB | 36 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.mediawiki.org | 3.820 s | 485.0 KB | 2.1 MB | 25 |
| upload.wikimedia.org | 3.141 s | 22.6 KB | 13.0 KB | 11 |
| login.wikimedia.org | 207 ms | N/A | 0 b | 1 |
| auth.wikimedia.org | 190 ms | 1.2 KB | 254 B | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 4 weeks | 1 year |
| Last modified | 14 minutes | 37 weeks | 2 years |
The page logs the following messages to the console.
| Level | Message |
|---|---|
| WARNING | https://www.mediawiki.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector-2022 11:76 "This page is using the deprecated ResourceLoader module \"mediawiki.Uri\".\n[1.43] Please use browser native URL." |
Included requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 30.7 KB | 4 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| svg | 9.3 KB | 9 |
| favicon | 8.2 KB | 1 |
| Total | 48.1 KB | 16 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 379.9 KB | 6 |
| image | 12.4 KB | 5 |
| font | 0 b | 0 |
| svg | 9.3 KB | 9 |
| favicon | 8.2 KB | 1 |
| Total | 409.8 KB | 23 |
Render blocking information directly from Chrome.
| Blocking | In body parser blocking | Potentially blocking |
|---|---|---|
| 2 | 0 | 1 |
| URL | Type |
|---|---|
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | blocking |
| https://www.mediawik...ki.org/w/load.php | potentially_blocking |
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | blocking |
| https://auth.wikimed...gin/checkLoggedIn | non_blocking |
| https://www.mediawik...alAutoLogin/start | non_blocking |
| https://login.wikime...gin/checkLoggedIn | non_blocking |
Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.
Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.
| Type | Quantity | Total duration (ms) |
|---|---|---|
| Total Blocking Time | 0 | |
| Max Potential First Input Delay | 0 | |
| Long Tasks before First Paint | 1 | 94 |
| Long Tasks before First Contentful Paint | 1 | 94 |
| Long Tasks before Largest Contentful Paint | 1 | 94 |
| Long Tasks after Load Event End | 0 | 0 |
| Total Long Tasks | 1 | 94 |
CPU last long task happened at 697 ms
| name | startTime | duration | containerId | containerName | containerSrc | containerType |
|---|---|---|---|---|---|---|
| unknown | 697 | 94 | window |
Calculated using Tracium.
| Categories (ms) | |
|---|---|
| parseHTML | 19 |
| styleLayout | 132 |
| paintCompositeRender | 19 |
| scriptParseCompile | 3 |
| scriptEvaluation | 158 |
| garbageCollection | 5 |
| other | 120 |
| Events (ms) | |
|---|---|
| FunctionCall | 133 |
| RunTask | 84 |
| Layout | 83 |
| UpdateLayoutTree | 48 |
| Paint | 15 |
| v8.run | 14 |
| ParseHTML | 12 |
| CpuProfiler::StartProfiling | 12 |
afterPageCompleteCheck.jpg
layoutShift.jpg
largestContentfulPaint.jpg
