Tested 2026-08-24 23:38:26 using Chrome 151.0.7922.75 (script).(runtime settings)
Test mobile as a logged in userLogin the user with an empty browser cache, then visit Obama and Facebook
The red band on the timeline marks when the main thread was busy with long tasks: moments when the page could not paint or respond, however the video looks.
Download videoUse --filmstrip.showAll to show all filmstrips.
Click a frame to seek the video to that moment. The dot marks frames where the page changed visually.
The whole recording in one image: every pixel is tinted by how often it changed. Amber changed once, deep red changed ten or more times. The scale is fixed, so heatmaps from different runs compare directly.
Flat amber is a page that painted once and stayed put. Red speckle in the shape of the text means the same pixels repainted over and over, usually invisible rendering noise that inflates Last Visual Change and Speed Index. A solid red block is a genuinely restless area, like an ad or a carousel.
How smoothly Chrome delivered frames to the screen during the test. Dropped counts only frames Chrome flags as affecting smoothness. On mostly-static pages the longest gap includes idle time where there was simply nothing to draw.
The server dominated the wait. The first byte took 2.308 s (65 % of the time to First Contentful Paint). Nothing can render before it arrives, and Google Web Vitals considers a TTFB over 800 ms in need of improvement. See the request timing on the Waterfall tab. First paint landed at 3.536 s; the 3 render-blocking requests were done by 2.949 s and the remaining ~587 ms is style and layout work (226 ms of it measured style recalculation and forced reflows).
Style the browser had to recalculate before it could paint: many elements or a lot of time spent here points at expensive CSS on the critical rendering path. The recalculation count and the largest single one tell the two problems apart: one massive style change touching most of the page (few recalculations, the largest close to the total) needs different medicine than thousands of tiny ones (many recalculations, each tiny).
One large recalculation dominates. Restyling 1 085 elements cost 206 ms before the page painted (5.8 % of the time to First Contentful Paint), and a single recalculation of 1 073 elements accounts for 201 ms of it. Look for one class or inline-style change on a large container near the top of the DOM that restyles the whole subtree at once. The changes driving it are listed under Style invalidations below.
The recalculation work before first paint is 5.8 % of the time to First Contentful Paint.
JavaScript read a layout value (offsetTop, getBoundingClientRect, …) while the page was mid-change, so the browser had to re-layout synchronously, work that blocks rendering. Reflows before First Contentful Paint delayed the first pixels; reflows before Largest Contentful Paint delayed the main content.
That is 0.6 % of the time to Largest Contentful Paint. The number of reflows matters more than the milliseconds: layout thrashing multiplies on slower devices.
See every forced reflow for the whole page load on the CPU tab
Blocking requests delay both paints: the browser renders nothing until they arrive, so they push First Contentful Paint and everything after it, including the largest paint (LCP). Requests that block the parser inside the body stall everything after them in the document. Load JavaScript with defer or async, and keep non-critical CSS off the critical path with media attributes. Bars show when each request loaded on a clock that runs to the last paint; the gap after the bars is style and layout work.
| Request | When it loaded | Transfer | Download |
|---|---|---|---|
document | 2.732 s | 55.6 KB | 1.283 s |
306 ms | 27.8 KB | 306 ms | |
user.stylesblocking | 149 ms | 1.0 KB | 149 ms |
site.stylesblocking | 104 ms | 2.9 KB | 104 ms |
startuppotentially blocking | 145 ms | 21.9 KB | 145 ms |
0884 ms1.768 sFCP · LCP 3.536 s |
Why the browser had to recalculate style and layout: every DOM/style change invalidates some set of nodes, and the same class or attribute churning over and over is the pattern to hunt. Counts, not milliseconds: the time is in the style recalculation numbers above.
Chase what keeps changing after the page is up. 155 style recalculations and 216 layout invalidations fired after first paint, on a page the user was already looking at. The biggest driver is pseudo disabled (4×). Start with the script under "Scripts causing invalidations" that keeps triggering it.
pseudo: disabled4×pseudo: enabled4×attribute: title3×attribute: disabled1×pseudo: last-child1×pseudo: only-child1×class: touch-events1×class: minerva-animations-ready1×Invalidations on a page the user was already looking at, the actionable half.
| Reason | Style recalculations | Layout |
|---|---|---|
| A node was inserted into the page | 64 | – |
| An animation updated stylesAnimate transform and opacity so the compositor can run it off the main thread. | 36 | – |
| Related style rule | 25 | – |
| A stylesheet rule changed | 19 | – |
| An @keyframes rule changed | 11 | – |
| An element entered layout | – | 194 |
| Unknown | – | 6 |
| An element's size changed | – | 7 |
| A style change forced layout | – | 6 |
| An element left layout | – | 2 |
| An SVG element changed | – | 1 |
The page being constructed and styled for the first render. Expected work, shown for scale.
| Reason | Style recalculations | Layout |
|---|---|---|
| A node was inserted into the page | 9 | – |
| A stylesheet rule changed | 1 | – |
| An element entered layout | – | 1 782 |
| Unknown | – | 4 |
| An element's size changed | – | 2 |
3 animations run on the main thread instead of on the browser's fast path that animates without blocking other page work (the compositor); they can make the rendering you see above janky. See them on the CPU tab.
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 9.2.1.
firstContentfulPaintFirst contentful paint is poor (3.536 s). It is in the Google Web Vitals poor range, slower than 3 seconds.The page has a high time to first byte (TTFB) 2.308 s that you should look into to improve first contentful paint.
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.
longTasksThe page has 8 CPU long tasks with the total of 1.212 s. The total blocking time is 803 ms and 1 long task before first contentful paint with total time of 59 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.
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.
modernImageFormatsThe page ships 17 images (out of 17) in JPEG/PNG/GIF without a modern alternative. Wrap them in a <picture> with a <source type="image/avif"> or "image/webp" before the legacy <img>, or serve modern formats from your image pipeline directly. AVIF and WebP usually deliver 25–50% smaller files at the same quality.
AVIF and WebP routinely deliver 25–50% smaller files than JPEG and PNG at the same perceived quality, and every browser version still under support understands at least one of them. Ship modern formats either through a <picture> element with <source type="image/avif"> / "image/webp" entries in front of the legacy <img>, or directly from a content-negotiating image pipeline that returns AVIF / WebP when the client accepts it. https://web.dev/articles/serve-images-webp
assetsRedirectsThe page has 67 redirects. 2 of the redirects are from the base domain, please fix them! 65 requests are from other domains, it could be 3rd-party assets doing unnecessary redirects. :(
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.
cacheHeadersThe page has 83 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 254.1 kB the next access.
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.
documentRedirectThe main document gets redirected 3 time(s). Remove those redirect and make the page faster!
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. :)
javascriptSizeThe total JavaScript transfer size is 411.9 kB and the uncompressed size is 1.9 MB. This is totally crazy! There is really room for improvement here.
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?
privateAssetsThe page has 60 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.
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.
decodingAsyncThe page has 20 images (out of 37) without a decoding hint. Add decoding="async" to non-critical images so the browser can decode them off the main thread.
Setting decoding="async" on an <img> tells the browser it can decode the image off the main thread, which keeps the page responsive to user interactions while images are being processed. The default ("auto") leaves the choice to the browser. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#decoding
lazyLoadingImagesThe page has 17 below-the-fold images without loading="lazy". Add loading="lazy" so the browser defers downloading and decoding them until the user scrolls them into view.
Adding loading="lazy" to an <img> tells the browser not to download or decode it until it is close to the viewport. For images that the user may never see (deep in the page, behind a tab, in a footer carousel), this saves bandwidth and main-thread time during initial render. The LCP image and any image in the initial viewport should NOT be lazy-loaded — that delays the first paint. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#loading
cacheHeadersLongThe page has 22 requests that have a shorter cache time than one year (but still a cache time).
Setting a cache header is good. Setting a long cache header (a year) is even better because the asset will stay in the browser cache across visits. For content-hashed URLs (e.g. app.4af2.css) you can safely use Cache-Control: max-age=31536000, immutable. For unversioned URLs that may change, use a revalidating strategy instead.
avoidScalingImagesThe 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.
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.
largestContentfulPaintLargest contentful paint can be improved 3.536 s. It is in the Google Web Vitals needs improvement range, slower than 2.5 seconds.
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.
compressAssetsThe page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.
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.
| URL | Transfer | Content |
|---|---|---|
| https://en.wikipedia.org/wiki/Main_Page | 55.6 KB | 247.3 KB |
optimalCssSizehttps://en.wikipedia.org/w/load.php?lang=en&modules=ext.echo.styles.alert%2Cbadge%7Cext.personalDashboard.menuIcon%7Cext.wikimediamessages.styles%7Cmediawiki.codex.messagebox.styles%7Cmediawiki.hlist%7Cmediawiki.skinning.content.parsoid%7Cmediawiki.skins.legacy%7Cmobile.init.styles%7Coojs-ui.styles.icons-alerts%7Cskins.minerva.codex.styles%7Cskins.minerva.content.styles.images%7Cskins.minerva.icons%2Cstyles%7Cskins.minerva.loggedin.styles%7Cskins.minerva.mainPage.styles%7Cwikibase.client.init&only=styles&skin=minerva size is 28.5 kB (28505) and that is bigger than the limit of 25 kB. Try to keep each CSS response under 25 kB.
Render-blocking CSS holds up the first paint until it has fully downloaded, parsed and applied, so smaller CSS files mean a faster start. Split your CSS into a small critical bundle inlined or eagerly loaded, with the rest lazy-loaded.
| URL | Transfer | Content |
|---|---|---|
| https://en.wikipedia.org/w/load.php...ia.org/w/load.php | 27.8 KB | 234.6 KB |
inlineCssThe 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.
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.
avoidRenderBlockingThe page has 3 blocking requests and 0 in body parser blocking (0 JavaScript and 3 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&skin=minerva
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.
metaDescriptionThe page is missing a meta description.
Use a page description to make the page more relevant to search engines.
unnecessaryHeadersThere are 77 responses that sets both a max-age and expires header. There are 113 responses that sets a server header.
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.
longHeadershttps://en.wikipedia.org/wiki/Main_Page has a header set-cookie that is 2102 characters long. https://en.wikipedia...ia.org/w/load.php has a header sourcemap that is 1397 characters long.
Do not send response headers that are too long.
contentSecurityPolicyHeaderSet a Content-Security-Policy header to mitigate cross-site scripting attacks. You can start with a Content-Security-Policy-Report-Only header, which only reports violations rather than blocking them.
A Content-Security-Policy response header tells the browser which sources of script, style, and other content are allowed. The most effective form is a strict CSP using nonces or hashes together with strict-dynamic; the worst is a missing header, with unsafe-inline and unsafe-eval close behind. https://web.dev/articles/strict-csp
crossOriginEmbedderPolicyHeaderSet a Cross-Origin-Embedder-Policy header (typically require-corp or credentialless) on the document response to control cross-origin embedding.
Cross-Origin-Embedder-Policy (COEP) makes the page refuse to load cross-origin subresources unless they explicitly opt in via CORP or CORS. Together with Cross-Origin-Opener-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy
crossOriginOpenerPolicyHeaderSet a Cross-Origin-Opener-Policy header (typically same-origin) on the document response to isolate the page from cross-origin windows.
Cross-Origin-Opener-Policy (COOP) lets a page sever its window-group ties to cross-origin documents that opened it or that it opens. Together with Cross-Origin-Embedder-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy
crossOriginResourcePolicyHeaderSet a Cross-Origin-Resource-Policy header (same-origin, same-site or cross-origin) on the document response to limit who may embed it.
Cross-Origin-Resource-Policy (CORP) is a per-response opt-in that tells the browser which origins are allowed to embed the resource. It blocks cross-origin or cross-site no-cors embedding (img, script, iframe, etc.) and is one of the building blocks of cross-origin isolation. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Resource-Policy
permissionsPolicyHeaderSet a Permissions-Policy header to control which browser features the page can use.
The Permissions-Policy response header (the successor to Feature-Policy) lets a site explicitly opt in or out of powerful browser features such as camera, microphone, geolocation, payment and clipboard. Setting a strict policy reduces the attack surface and limits what embedded third parties can do. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
referrerPolicyHeaderSet a referrer-policy header to make sure you do not leak user information.
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/.
A snapshot of what the browser actually built for this page: the document, how big and deep the DOM tree is and what it kept in storage. Big, deep trees are slower to style and lay out, so the counts Chrome warns about carry a flag.
Document
What the page says it is and how large it rendered.
DOM structure
How much markup the browser has to build, style and lay out.
What the page stored on the client, and the network it was tested on.
Data collected using
Coach-core version 9.2.1. With updated code from
Webappanalyzer 2026-05-04. Use
--browsertime.firefox.includeResponseBodies html or
--browsertime.chrome.includeResponseBodies html to help Wappalyzer find more information about technologies used.
0.0s3.9s4.8s5.3s7.0s8.1s11.1s13.9sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div#mw-mf-viewport > div#mw-mf-page-center > main#content > div:eq(0) > div#siteNotice > div:eq(1) > div
The LCP element is highlighted in the screenshot. If nothing is highlighted the element was removed before the screenshot or the LCP API couldn't find it.
How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.
No layout shifts were detected on this page.
Timing data the server chose to expose through Server-Timing response headers on the main document — typically backend time, cache status or experiment flags.
| Name | Duration | Description |
|---|---|---|
cache | 0 ms | pass |
host | 0 ms | cp3070 |
co_id | 0 ms | 3292867581 |
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
https://en.wikipedia.org/wiki/Main_Page
| Header | Value |
|---|---|
accept-ch | Sec-CH-UA, Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Form-Factor, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version, Sec-CH-UA-WoW64 |
age | 2 |
cache-control | private, max-age=0, s-maxage=0 |
content-length | 0 |
content-type | text/html; charset=UTF-8 |
date | Mon, 24 Aug 2026 23:38:28 GMT |
expires | Thu, 01 Jan 1970 00:00:00 GMT |
location | https://en.wikipedia.org/w/index.php?title=Special:UserLogin/return&returnto=Main+Page&wpLoginToken=ee7d5034849fc799374676f8b40ba5776a8cd5e3%2B%5C&useformat=mobile&usesul3=1¢ralauthLoginToken=e770a57cfe9940fe7e080a5dc202d17f |
nel | { "report_to": "wm_nel", "max_age": 604800, "failure_fraction": 0.05, "success_fraction": 0.0} |
report-to | { "group": "wm_nel", "max_age": 604800, "endpoints": [{ "url": "https://intake-logging.wikimedia.org/v1/events?stream=w3c.reportingapi.network_error&schema_uri=/w3c/reportingapi/network_error/1.0.0" }] } |
server | mw-web.eqiad.main-7cd74bd656-ffvfr |
server-timing | cache;desc="pass", host;desc="cp3070",co_id;desc="828202493" |
strict-transport-security | max-age=106384710; includeSubDomains; preload |
vary | Accept-Encoding,X-Forwarded-Proto,Cookie,Authorization |
x-analytics | |
x-cache | cp3070 miss, cp3070 pass |
x-cache-status | pass |
x-client-ip | 138.201.135.103 |
x-content-type-options | nosniff |
x-request-id | f1f796df-21b6-4b97-9f69-5104afe04105 |
Transfer size764.3 KB
Content size2.5 MB
Requests46
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 55.6 KB | 247.3 KB | 1 |
| css | 0 b | 31.8 KB | 241.6 KB | 3 |
| javascript | 0 b | 402.2 KB | 1.8 MB | 6 |
| image | 0 b | 250.3 KB | 206.3 KB | 18 |
| favicon | 0 b | 1.8 KB | 2.7 KB | 1 |
| svg | 0 b | 18.2 KB | 13.6 KB | 13 |
| json | 0 b | 1.8 KB | 288 B | 1 |
| plain | 0 b | 2.6 KB | 0 b | 3 |
| Total | 0 b | 764.3 KB | 2.5 MB | 46 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| auth.wikimedia.org | 10.117 s | N/A | 0 b | 33 |
| en.wikipedia.org | 7.523 s | 516.1 KB | 2.3 MB | 31 |
| en.wikibooks.org | 805 ms | 3.0 KB | 68 B | 3 |
| en.wikinews.org | 1.333 s | 3.0 KB | 68 B | 3 |
| en.wikiquote.org | 783 ms | 3.0 KB | 68 B | 3 |
| en.wikisource.org | 798 ms | 3.0 KB | 68 B | 3 |
| en.wikiversity.org | 853 ms | 3.0 KB | 68 B | 3 |
| en.wikivoyage.org | 815 ms | 3.0 KB | 68 B | 3 |
| en.wiktionary.org | 779 ms | 3.0 KB | 68 B | 3 |
| www.mediawiki.org | 756 ms | 3.0 KB | 68 B | 3 |
| commons.wikimedia.org | 754 ms | 2.8 KB | 68 B | 3 |
| foundation.wikimedia.org | 739 ms | 1.2 KB | 68 B | 3 |
| incubator.wikimedia.org | 781 ms | 2.8 KB | 68 B | 3 |
| meta.wikimedia.org | 738 ms | 2.8 KB | 68 B | 3 |
| species.wikimedia.org | 1.016 s | 2.8 KB | 68 B | 3 |
| wikimania.wikimedia.org | 844 ms | 1.2 KB | 68 B | 3 |
| www.wikidata.org | 1.155 s | 3.0 KB | 68 B | 3 |
| www.wikifunctions.org | 1.429 s | 1.4 KB | 68 B | 3 |
| upload.wikimedia.org | 541 ms | 205.8 KB | 203.9 KB | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 0 seconds | 1 year |
| Last modified | 4 days | 7 weeks | 7 weeks |
The page logs the following messages to the console.
| Level | Message |
|---|---|
| INFO | https://en.wikipedia.org/w/load.php?lang=en&modules=ext.centralNotice.bannerHistoryLogger%2CchoiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2ClargeBannerLimit%2ClegacySupport%2CstartUp%7Cext.centralauth.ForeignApi%7Cext.centralauth.centralautologin.clearcookie%7Cext.checkUser.clientHints%7Cext.cx.entrypoints.languagesearcher.v2%7Cext.cx.eventlogging.campaigns%7Cext.cx.model%7Cext.echo.api%2Cinit%7Cext.eventLogging%2CnavigationTiming%2Cpopups%2CtestKitchen%2CwikimediaEvents%7Cext.eventLogging.metricsPlatform%7Cext.growthExperiments.SuggestedEditSession%7Cext.parsermigration.reportbug.init%7Cext.personalDashboard.blueDot%7Cext.uls.interface%2Cpreferences%2Cwebfonts%7Cext.uls.rewrite.entrypoints%7Cext.urlShortener.toolbar%7Cext.wikimediaEvents.emailConfirmationBanner%2CtestKitchen%7Cjquery%2Coojs%2Csite%7Cjquery.client%2CtextSelection%7Cjquery.uls.data%7Cmediawiki.DateFormatter%2CForeignApi%2CString%2CTitle%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Cpulsatingdot%2Crouter%2Cstorage%2Ctemplate%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.ForeignApi.core%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.template.mustache%7Cmmv.bootstrap%2Ccodex%7Cmobile.codex.styles%7Cmobile.init%2Cstartup%7Cmw.cx.SiteMapper%7Cmw.externalguidance.init%7Cskins.minerva.scripts%7Cwikibase.databox.fromWikidata&skin=minerva&version=ppsjf 834:13906 "Hello friend! 🍦\n\nWikipedia is built by developers like you 👨💻 (yes it's open source)\n\nStart your journey 🛤️ here @ https://developer.wikimedia.org\n\n💪 Or work with us @ https://wikimediafoundation.org/about/jobs/" |
| WARNING | https://en.wikipedia.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=minerva 11:76 "This page is using the deprecated ResourceLoader module \"moment\".\n[1.44] Use mediawiki.DateFormatter or native Intl function instead. See https://phabricator.wikimedia.org/T146798" |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 2.1 KB | 1 |
| font | 0 b | 0 |
| favicon | 1.8 KB | 1 |
| Total | 3.9 KB | 2 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 125.9 KB | 1 |
| image | 225.0 KB | 9 |
| font | 0 b | 0 |
| favicon | 1.8 KB | 1 |
| Total | 352.6 KB | 35 |
Tasks ≥ 50 ms blocking the main thread, collected via the Long Task API.
A long animation frame (LOAF) is a frame that took ≥ 50 ms from input to the next paint. The part beyond the threshold is blocking time, the number that hurts Interaction to Next Paint and Total Blocking Time. Break long tasks up (scheduler.yield(), smaller chunks) or move the work off the main thread. Read more about the Long Animation Frames API.
| Script | Frames | Time running | Blocking (share by run time) | Forced style & layout | Triggered by |
|---|---|---|---|---|---|
| load.php[startup] | 7 | 1.004 s | 820.8 ms | – | script tag, timer or animation callback |
| load.php[scripts:ext.centralNotice.bannerHistoryLogger] | 4 | 151.5 ms | 63.4 ms | 2.8 ms | script tag, event handler, timer or animation callback |
| Main_Page | 2 | 14.6 ms | 11.6 ms | – | script tag |
A frame's blocking time is split between its scripts by their share of the frame's work, capped at each script's own run time — blocking from work no script owns (HTML parsing, browser internals) stays unattributed. The per-script blocking view below uses the same attribution.
2 more long frames carried no blocking time (nothing ran past the 50 ms threshold) — long, but harmless to INP and TBT.
How much each script blocked the main thread, derived from the Long Animation Frame API. Each frame's blocking time is split between its scripts by their share of the frame's work, capped at each script's own run time — blocking from work no script owns (HTML parsing, browser internals) is not attributed (older data credits the script that started the frame). The closest answer to "which script should I fix to improve TBT" the platform exposes.
Total Blocking Time attributed per script from the Chrome trace: every main-thread task longer than 50 ms blocks input for the remainder, and each blocking task is credited to the script whose own code ran the longest during that task.
All main-thread work during the full page load, not just the share that blocked input. Calculated from the Chrome trace.
parseHTMLstyleLayoutscriptParseCompilescriptEvaluationpaintCompositeRendergarbageCollectionotherThe functions where main-thread JavaScript time was actually spent, sampled by Chrome's JavaScript profiler. Self time is spent in the function itself; total time includes the functions it called. For loader/dispatcher functions whose total dwarfs their self time, the runs line shows the top functions and modules (up to five, ≥ 1 ms) the total was actually spent running.
| Function | Where | Self time | Total time |
|---|---|---|---|
flushWritesruns: load.php[startup] (33.6 ms) | load.php[startup] | 208.9 ms | 242.7 ms |
insertBefore | 94.9 ms | 94.9 ms | |
runScriptruns: load.php[scripts:ext.centralNotice.bannerHistoryLogger] (246.0 ms) | load.php[startup] | 90.5 ms | 558.4 ms |
requireruns: load.php[scripts:ext.centralNotice.bannerHistoryLogger] (15.0 ms), load.php[startup] (4.2 ms) | load.php[startup] | 51.2 ms | 85.0 ms |
setTimeout | 41.3 ms | 41.3 ms | |
implruns: load.php[startup] (3.7 ms), load.php[scripts:ext.centralNotice.bannerHistoryLogger] (4.3 ms) | load.php[startup] | 31.2 ms | 39.5 ms |
doPropagationruns: load.php[startup] (379.6 ms), load.php[scripts:ext.centralNotice.bannerHistoryLogger] (1.8 ms) | load.php[startup] | 29.7 ms | 411.3 ms |
appendChildruns: (anonymous) (4.1 ms) | 25.9 ms | 30.1 ms | |
truns: load.php[scripts:ext.centralNotice.bannerHistoryLogger] (93.2 ms) | load.php[scripts:ext.centralNotice.bannerHistoryLogger] | 24.3 ms | 87.6 ms |
setruns: load.php[startup] (9.1 ms) | load.php[startup] | 24.3 ms | 33.6 ms |
requestIdleCallback | 16.3 ms | 16.3 ms | |
getUserViewportBucket | load.php[scripts:ext.centralNotice.bannerHistoryLogger] | 15.9 ms | 15.9 ms |
(anonymous)runs: load.php[scripts:ext.centralNotice.bannerHistoryLogger] (54.0 ms) | load.php[scripts:ext.centralNotice.bannerHistoryLogger] | 15.3 ms | 73.8 ms |
(anonymous)runs: appendChild (1.3 ms) | load.php[scripts:ext.centralNotice.bannerHistoryLogger] | 14.2 ms | 15.5 ms |
sendEvent | load.php[scripts:ext.centralNotice.bannerHistoryLogger] | 12.9 ms | 12.9 ms |
How much setTimeout/setInterval work the page runs, credited to the script that scheduled each timer. Many zero-delay timers mean work sliced into a machine-gun of tiny tasks; repeating timers are polling.
| Set by | Delay | Type | Times set | Times fired | Fire time |
|---|---|---|---|---|---|
| load.php[scripts:ext.centralNotice.bannerHistoryLogger]:412 | 0 ms | once | 49 | 49 | 224.3 ms |
SafeStorage in load.php[scripts:ext.centralNotice.bannerHistoryLogger]:731 | 2000 ms | once | 2 | 2 | 4.6 ms |
| load.php[scripts:ext.centralNotice.bannerHistoryLogger]:154 | 0 ms | once | 1 | 1 | 2.9 ms |
requestUpdate in load.php[startup]:22 | 2000 ms | once | 1 | 1 | 0.1 ms |
run in load.php[scripts:ext.centralNotice.bannerHistoryLogger]:210 | 60000 ms | once | 1 | 0 | 0.0 ms |
setActive in load.php[scripts:ext.centralNotice.bannerHistoryLogger]:210 | 100000 ms | once | 1 | 0 | 0.0 ms |
A forced reflow happens when JavaScript reads a layout-triggering property (offsetTop, getBoundingClientRect, …) inside a handler, forcing the browser to synchronously recompute layout. The scripts below caused most of the page's reflows. Fix them in priority order.
Each long animation frame reports how much time each script spent forcing synchronous style and layout, i.e. JavaScript reading layout-triggering properties mid-execution. Same actionable answer as forced reflows above but measured directly by the browser instead of inferred from the trace.
Main-thread CPU time from the Chrome trace split by domain. First party is wikipedia.org.
Animations that fell back from the compositor to the main thread, blocking each frame instead of running on the GPU.
Each chip below is a CSS property the page tried to animate that Chrome couldn't hand to the compositor. Swap it for a transform or opacity equivalent where you can.
color1×Want to dig deeper? Download the Chrome trace and drag-and-drop it into Performance in DevTools.