Run 5 summary

https://en.wikipedia.org/wiki/Barack_Obama

Tested 2026-07-27 21:51:30 using Firefox 153.0 (runtime settings)

SummaryWaterfallMetricsRenderingCoachPageXrayCPU

Summary

Google Web Vitals

423 msTTFB
2.050 sLargest Contentful Paint

Loading

1.349 sFirst Paint
7.540 sFully Loaded

Page weight & requests

1.4 MBTotal transfer size
92Requests

Visual progress

1.400 sFirst Visual Change
1.494 sSpeed Index
1.400 sVisual Complete 85%
3.200 sVisual Complete 99%
3.200 sLast Visual Change
Screenshot
Run 5 · after page complete

Waterfall

First paintFCPLCPDOMContentLoadedDOM interactiveLoadRender-blockingRedirectError

Rendering

Run 5
0.000 s
0s1s2s3s
Download video

Filmstrip

7 frames

Use --filmstrip.showAll to show all filmstrips.

Frame at 0 ms
0 ms
0 %
Frame at 1.400 s
1.400 s
89 %
Frame at 1.800 s
1.800 s
89 %
Frame at 2.000 s
2.000 s
89 %
Frame at 2.100 s
2.100 s
98 %
Frame at 2.400 s
2.400 s
98 %
Frame at 3.200 s
3.200 s
100 %

Click a frame to seek the video to that moment. The dot marks frames where the page changed visually.

Visual instability

19.05 % of pixels ever changed · 0 % changed 5+ times
Heatmap of how often each pixel changed while the page loaded

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.

Rendering was not meaningfully delayed. First paint landed at 1.350 s on a 423 ms first byte. The largest paint followed at 2.050 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 9.2.1.

Performance advice

87
9 warnings3 info
warn(0)Serve images in modern formats (AVIF, WebP)modernImageFormats

The page ships 57 images (out of 57) 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

Offenders
warn(0)Avoid extra requests by setting cache headerscacheHeaders

The page has 60 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 606.5 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.

Offenders
warn(4)Lazy-load below-the-fold imageslazyLoadingImages

The page has 51 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

Offenders
warn(40)Don't scale images in the browseravoidScalingImages

The page has 6 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.

Offenders
warn(50)Total JavaScript size shouldn't be too bigjavascriptSize

The total JavaScript transfer size is 313.9 kB. This is quite large.

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
URLTransferContent
https://en.wikipedia.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector-202222.5 KB0 b
https://en.wikipedia.org/w/load.php...ia.org/w/load.php8.2 KB0 b
https://en.wikipedia.org/w/load.php...ia.org/w/load.php18.0 KB0 b
https://en.wikipedia.org/w/load.php...ia.org/w/load.php226.7 KB0 b
https://en.wikipedia.org/w/load.php...ia.org/w/load.php26.3 KB0 b
https://en.wikipedia.org/w/load.php...ia.org/w/load.php3.1 KB0 b
https://auth.wikimedia.org/metawiki/wiki/Special:CentralAutoLogin/checkLoggedIn...gin/checkLoggedIn1.7 KB0 b
warn(70)Apply the right priority hints to the LCP imagelcpImageHints

The LCP image is missing fetchpriority="high". Adding it tells the browser to fetch the image with high priority instead of the default heuristic (which often deprioritises hero images that are loaded after the HTML has been parsed).

When the Largest Contentful Paint element is an image, the browser priority hints applied to that element directly affect the LCP metric. The image must NOT be loading="lazy" (that defers the fetch until near-viewport, which is the opposite of what an LCP image needs) and SHOULD be fetchpriority="high" (so the browser fetches it with high priority instead of guessing). https://web.dev/articles/fetch-priority

Offenders
  • <img alt="Obama standing in the Oval Office with his arms folded and smiling" resource="https://en.wikipedia.org/wiki/File:President_Barack_Obama.jpg" src="//upload.wikimedia.org/wikipedia/commons/thumb/8/8d/President_Barack_Obama.jpg/250px-President_Barack_Obama.jpg" decoding="async" data-file-width="2687" data-file-height="3356" data-file-type="bitmap" height="312" width="250" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/8/8d/President_Barack_Obama.jpg/500px-President_Barack_Obama.jpg 2x" class="mw-file-element mw-file-upright" style="--mw-file-upright: 1">
infoLong cache headers is goodcacheHeadersLong

The 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.

Offenders
warn(90)Avoid doing redirectsassetsRedirects

The page has 1 redirect. 1 of the redirects are from the base domain, please fix them!

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
infoMake each CSS response smalloptimalCssSize

https://en.wikipedia.org/w/load.php?lang=en&modules=ext.cite.parsoid.styles%7Cext.cite.styles%7Cext.phonos.icons%2Cstyles%7Cext.tmh.player.styles%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cext.wikimediaBadges.ulsV2%7Cext.wikimediamessages.styles%7Cjquery.makeCollapsible.styles%7Cmediawiki.skinning.content.parsoid%7Cmediawiki.skins.legacy%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles%7Cwikibase.client.init&only=styles&skin=vector-2022 size is 28.4 kB (28377) 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.

Offenders
URLTransferContent
https://en.wikipedia.org/w/load.php...ia.org/w/load.php27.7 KB0 b
infoAdd decoding="async" to non-critical imagesdecodingAsync

The page has 5 images (out of 62) 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

Offenders
warn(95)Avoid slowing down the critical rendering pathavoidRenderBlocking

The style https://en.wikipedia.org/w/load.php?lang=en&modules=ext.cite.parsoid.styles%7Cext.cite.styles%7Cext.phonos.icons%2Cstyles%7Cext.tmh.player.styles%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cext.wikimediaBadges.ulsV2%7Cext.wikimediamessages.styles%7Cjquery.makeCollapsible.styles%7Cmediawiki.skinning.content.parsoid%7Cmediawiki.skins.legacy%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles%7Cwikibase.client.init&only=styles&skin=vector-2022 is larger than the magic number TCP window size 14.5 kB. Make the file smaller and the page will render faster. The page has 1 render blocking CSS request and 0 blocking JavaScript request inside of head.

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
warn(95)Inline CSS for faster first renderinlineCss

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.

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.

Best practice advice

62
1 error1 warning4 info
error(0)Cumulative Layout ShiftcumulativeLayoutShift

Layout Shift is not supported in this browser

Cumulative Layout Shift measures the sum total of all individual layout shift scores for unexpected layout shift that occur. The metric is measuring visual stability by quantify how often users experience unexpected layout shifts. It is one of Google Web Vitals.

infoMeta descriptionmetaDescription

The page is missing a meta description.

Use a page description to make the page more relevant to search engines.

infoAvoid unnecessary headersunnecessaryHeaders

There are 27 responses that sets both a max-age and expires header. There are 91 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.

Offenders
infoGive every image a textual alternativeimageAltText

The page has 5 images without an alt attribute. Add alt="..." with a description, or alt="" if the image is purely decorative.

Every <img> needs an alt attribute. Use alt="meaningful description" for content images so assistive technologies can announce them, or alt="" (or role="presentation" / aria-hidden="true") for purely decorative images so they are skipped. A missing alt attribute leaves screen reader users with no information at all. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#alt

Offenders
warn(50)Set a sensible viewport meta tagviewport

The viewport meta tag does not contain width=device-width, the browser may use a desktop-width fallback.

The viewport meta tag tells the browser how to lay out the page on small screens. Without it (or without width=device-width) the page is rendered at a desktop fallback width and scaled down, which makes text unreadable on mobile. Disabling zoom (user-scalable=no, maximum-scale<=1) is also an accessibility regression. https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag

infoDo not send too long headerslongHeaders

https://en.wikipedia...wiki/Barack_Obama has a header content-security-policy that is 4501 characters long. https://en.wikipedia...ia.org/w/load.php has a header sourcemap that is 1359 characters long.

Do not send response headers that are too long.

Offenders

Privacy advice

80
4 warnings2 info
infoSet a Cross-Origin-Embedder-Policy header so cross-origin subresources opt in to being embedded.crossOriginEmbedderPolicyHeader

Set 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

Offenders
warn(0)Set a Cross-Origin-Opener-Policy header to isolate the page from cross-origin windows.crossOriginOpenerPolicyHeader

Set 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

Offenders
infoSet a Cross-Origin-Resource-Policy header to limit who may embed the page.crossOriginResourcePolicyHeader

Set 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

Offenders
warn(0)Set a Permissions-Policy header to control which browser features the page can use.permissionsPolicyHeader

Set 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

Offenders
warn(0)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.

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
warn(30)Use a strict Content-Security-Policy header to mitigate cross-site scripting (XSS) attacks.contentSecurityPolicyHeader

The policy allows 'unsafe-inline', which lets the browser execute inline scripts and styles directly from the page. Move to nonces or hashes plus 'strict-dynamic' so that inline injection cannot run. The policy allows 'unsafe-eval', which lets the page call eval() and Function(). Almost no application needs this; remove it.

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

Page info

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.

Page info

Document

What the page says it is and how large it rendered.

TitleBarack Obama - WikipediaThe document title, shown in the browser tab and used by search results.
GeneratorMediaWiki 1.47.0-wmf.12The tool or CMS that generated the HTML, from the page generator meta tag.
Layout viewport1920 × 56781 pxThe width the page laid out at, and the full height of the rendered document.

DOM structure

How much markup the browser has to build, style and lay out.

DOM elements22,437Very large, slows layout and styleTotal HTML elements. Fewer means less for the browser to style, lay out and paint.
Avg DOM depth19How deeply elements are nested on average.
Max DOM depth34Very deep treeThe deepest nesting on the page. Deep branches cost more style recalculation.
Iframes0No embedded documents on this page.
Script tags5Number of script elements. More scripts usually means more main-thread work.

Storage and connection

What the page stored on the client, and the network it was tested on.

Local storage2.1 MBData the page saved in localStorage, kept across visits.
Session storage0 bData kept in sessionStorage for this tab session only.
Connection typeUNKNOWNWhat the Network Information API reported for the test connection.

Resource hints

3 hints
dns-prefetch
  • https://meta.wikimedia.org/
  • https://en.wikipedia.org/wiki/auth.wikimedia.org
preconnect
  • https://upload.wikimedia.org/

Technologies used to build the page

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.

Detected technologies

4 technologies
  • MediaWikiConfidence100
    Wikis
  • PHPConfidence100
    Programming languages
  • HSTSConfidence100
    Security
  • HTTP/2Confidence100
    Miscellaneous

Visual Metrics

Visual milestones

all times from navigation start
Speed Index1.49 show quickly the page looked done
First Visual Change1.40 sfirst paint reaches the screen
Last Visual Change3.20 sscreen stops changing · 1.80 s after first
nothing painted yet
≥85%
≥95% rendered
First Visual Change · Visual Complete 85%1.40 s
2.07 sVisual Complete 95%
Visual Complete 99% · Last Visual Change3.20 s
Visual Readiness1.80 s· first to last change
01.0 s2.0 s3.0 s
Visual progress
Visual progress at 0 s0.0s
Visual progress at 1.4 s1.4s
Visual progress at 1.8 s1.8s
Visual progress at 2 s2.0s
Visual progress at 2.1 s2.1s
Visual progress at 2.4 s2.4s
Visual progress at 3.2 s3.2s
FCP1.35s
LCP2.05s
VC851.40s
0.0s0.6s1.3s1.9s2.6s3.2s

Google Web Vitals

Largest Contentful Paint

When the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.

2.050 sLCP render time

Phase breakdown

  • TTFB423 ms
  • Resource load delay174 ms
  • Resource load duration1.443 s
  • Element render delay10 ms

Element

Element type
<img>
Size (w × h)
78000
URL
https://upload.wikim..._Barack_Obama.jpg
Load time
2.041 s

DOM path

body > div:eq(2) > div > div:eq(2) > main#content > div#bodyContent > div#mw-content-text > div:eq(1) > section#mwAQ > div#mwDw > div > table:eq(0) > tbody > tr:eq(1) > td > span > a > img
LCP

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.

The Largest Contentful Paint API matched this image:

LCP element

Browser Metrics

Navigation Timing
Extra timings
User Timing marks
mwStartup1.774 s

Server timings

Timing data the server chose to expose through Server-Timing response headers on the main document — typically backend time, cache status or experiment flags.

Server timings

2 entries
NameDurationDescription
WMF-Uniq0 mswe-1-8-tempuser-post-edit=treatment;we-1-8-account-creation-no-desktop-benefits=treatment;
co_id0 ms2918229119

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 Elements3
LargestImage250px-President_Barack_Obama.jpg
Display time2.067 s
Position (x, y)1153, 311
Size (w × h)250 × 312
HTML snippet
<img alt="Obama standing in the Oval Office with his arms folded and smiling" resource="https://en.wikipedia.org/wiki/File:President_Barack_Obama.jpg" src="//upload.wikimedia.org/wikipedia/commons/thumb/8/8d/President_Barack_Obama.jpg/250px-President_Barack_Obama.jpg" decoding="async" data-file-width="2687" data-file-height="3356" data-file-type="bitmap" height="312" width="250" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/8/8d/President_Barack_Obama.jpg/500px-President_Barack_Obama.jpg 2x" class="mw-file-element mw-file-upright" style="--mw-file-upright: 1">
Heading
Display time1.400 s
Position (x, y)486, 90
Size (w × h)776 × 40
HTML snippet
<h1 id="firstHeading" class="firstHeading mw-first-heading"></h1>
LargestContentfulPaint250px-President_Barack_Obama.jpg
Display time2.067 s
Position (x, y)1153, 311
Size (w × h)250 × 312
HTML snippet
<img alt="Obama standing in the Oval Office with his arms folded and smiling" resource="https://en.wikipedia.org/wiki/File:President_Barack_Obama.jpg" src="//upload.wikimedia.org/wikipedia/commons/thumb/8/8d/President_Barack_Obama.jpg/250px-President_Barack_Obama.jpg" decoding="async" data-file-width="2687" data-file-height="3356" data-file-type="bitmap" height="312" width="250" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/8/8d/President_Barack_Obama.jpg/500px-President_Barack_Obama.jpg 2x" class="mw-file-element mw-file-upright" style="--mw-file-upright: 1">

PageXray

How the page is built.

HTTP versionHTTP/2.0
Total requests92
Total domains3
Transfer size1.4 MB
Content size0 b
Missing compression0
Cookies650 third-party

Main document

status 200 · 0 redirects

https://en.wikipedia.org/wiki/Barack_Obama

HeaderValue
dateMon, 27 Jul 2026 16:17:12 GMT
servermw-web.eqiad.main-69bbd59d68-hzhk2
x-content-type-optionsnosniff
content-languageen
accept-ch
reporting-endpointscsp-report-to-endpoint='/w/api.php?action=cspreport&format=json';
content-security-policyscript-src 'unsafe-eval' blob: 'self' meta.wikimedia.org *.wikimedia.org *.wikipedia.org *.wikinews.org *.wiktionary.org *.wikibooks.org *.wikiversity.org *.wikisource.org wikisource.org *.wikiquote.org *.wikidata.org *.wikifunctions.org *.wikivoyage.org *.mediawiki.org mediawiki.org wikimedia.org *.wmflabs.org *.wmcloud.org *.toolforge.org wss://*.toolforge.org *.jsdelivr.net unpkg.com cdnjs.cloudflare.com raw.githubusercontent.com *.github.com code.jquery.com cdn.mathjax.org use.typekit.net fonts.cdnfonts.com use.fontawesome.com i.ytimg.com rsms.me doi.org localhost https://localhost:* http://localhost:* wss://localhost:* ws://localhost:* *.google.com *.gstatic.com *.googleapis.com *.translate.yandex.net yastatic.net ya.ru radically.github.io cdn.sammdot.ca cdn.fontshare.com viaf.org publicai-proxy.alaexis.workers.dev iiif.archive.org api.flickr.com live.staticflickr.com api.anthropic.com api.openai.com api.publicai.co catalogo.pusc.it parsifal.urbe.it opac.sbn.it overpass-api.de api.openrouteservice.org archive.org *.openstreetmap.org *.waymarkedtrails.org *.thunderforest.com registry.ipe.wiki analytics.ipe.wiki qlever.dev app.goacoustic.com wikipedia-archive.ourworldindata.org api.inaturalist.org inaturalist-open-data.s3.amazonaws.com validator.w3.org db.onlinewebfonts.com fontlibrary.org 'unsafe-inline' auth.wikimedia.org; default-src 'self' data: blob: upload.wikimedia.org https://commons.wikimedia.org meta.wikimedia.org *.wikimedia.org *.wikipedia.org *.wikinews.org *.wiktionary.org *.wikibooks.org *.wikiversity.org *.wikisource.org wikisource.org *.wikiquote.org *.wikidata.org *.wikifunctions.org *.wikivoyage.org *.mediawiki.org mediawiki.org wikimedia.org *.wmflabs.org *.wmcloud.org *.toolforge.org wss://*.toolforge.org *.jsdelivr.net unpkg.com cdnjs.cloudflare.com raw.githubusercontent.com *.github.com code.jquery.com cdn.mathjax.org use.typekit.net fonts.cdnfonts.com use.fontawesome.com i.ytimg.com rsms.me doi.org localhost https://localhost:* http://localhost:* wss://localhost:* ws://localhost:* *.google.com *.gstatic.com *.googleapis.com *.translate.yandex.net yastatic.net ya.ru radically.github.io cdn.sammdot.ca cdn.fontshare.com viaf.org publicai-proxy.alaexis.workers.dev iiif.archive.org api.flickr.com live.staticflickr.com api.anthropic.com api.openai.com api.publicai.co catalogo.pusc.it parsifal.urbe.it opac.sbn.it overpass-api.de api.openrouteservice.org archive.org *.openstreetmap.org *.waymarkedtrails.org *.thunderforest.com registry.ipe.wiki analytics.ipe.wiki qlever.dev app.goacoustic.com wikipedia-archive.ourworldindata.org api.inaturalist.org inaturalist-open-data.s3.amazonaws.com validator.w3.org db.onlinewebfonts.com fontlibrary.org en.wikibooks.org en.wikinews.org en.wikiquote.org en.wikisource.org en.wikiversity.org en.wikivoyage.org en.wiktionary.org www.mediawiki.org commons.wikimedia.org foundation.wikimedia.org incubator.wikimedia.org species.wikimedia.org wikimania.wikimedia.org www.wikidata.org www.wikifunctions.org auth.wikimedia.org; style-src 'self' data: blob: upload.wikimedia.org https://commons.wikimedia.org meta.wikimedia.org *.wikimedia.org *.wikipedia.org *.wikinews.org *.wiktionary.org *.wikibooks.org *.wikiversity.org *.wikisource.org wikisource.org *.wikiquote.org *.wikidata.org *.wikifunctions.org *.wikivoyage.org *.mediawiki.org mediawiki.org wikimedia.org *.wmflabs.org *.wmcloud.org *.toolforge.org wss://*.toolforge.org *.jsdelivr.net unpkg.com cdnjs.cloudflare.com raw.githubusercontent.com *.github.com code.jquery.com cdn.mathjax.org use.typekit.net fonts.cdnfonts.com use.fontawesome.com i.ytimg.com rsms.me doi.org localhost https://localhost:* http://localhost:* wss://localhost:* ws://localhost:* *.google.com *.gstatic.com *.googleapis.com *.translate.yandex.net yastatic.net ya.ru radically.github.io cdn.sammdot.ca cdn.fontshare.com viaf.org publicai-proxy.alaexis.workers.dev iiif.archive.org api.flickr.com live.staticflickr.com api.anthropic.com api.openai.com api.publicai.co catalogo.pusc.it parsifal.urbe.it opac.sbn.it overpass-api.de api.openrouteservice.org archive.org *.openstreetmap.org *.waymarkedtrails.org *.thunderforest.com registry.ipe.wiki analytics.ipe.wiki qlever.dev app.goacoustic.com wikipedia-archive.ourworldindata.org api.inaturalist.org inaturalist-open-data.s3.amazonaws.com validator.w3.org db.onlinewebfonts.com fontlibrary.org 'unsafe-inline'; object-src 'none'; report-uri /w/api.php?action=cspreport&format=json; report-to csp-report-to-endpoint
last-modifiedMon, 27 Jul 2026 16:10:44 GMT
content-typetext/html; charset=UTF-8
content-encodinggzip
age20059
accept-rangesbytes
x-cachecp3070 miss, cp3070 hit/77
x-cache-statushit-front
strict-transport-securitymax-age=106384710; includeSubDomains; preload
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" }] }
nel{ "report_to": "wm_nel", "max_age": 604800, "failure_fraction": 0.05, "success_fraction": 0.0}
x-client-ip138.201.135.103
cache-controlprivate, s-maxage=0, max-age=0, must-revalidate, no-transform
varyAccept-Encoding,X-Subdomain,Cookie,Authorization,User-Agent
content-length411084
x-request-ida46d89f2-8da2-4236-894f-9d178a088e30
x-analytics
server-timingWMF-Uniq;desc="we-1-8-tempuser-post-edit=treatment;we-1-8-account-creation-no-desktop-benefits=treatment;",co_id;desc="2918229119"
x-firefox-spdyh2

Response codes

200
9097.8%
202
11.1%
302
11.1%

Requests and sizes per content type

7 types

Transfer size1.4 MB

  • image41.2%
  • html28.7%
  • javascript21.6%
  • svg6.1%
  • css2.2%
  • favicon0.15%
  • plain0.07%

Content size0 b

Requests91

  • image61.5%
  • svg25.3%
  • javascript7.7%
  • css2.2%
  • html1.1%
  • favicon1.1%
  • plain1.1%
ContentHeader SizeTransfer SizeContent SizeRequests
html6.3 KB407.8 KB0 b1
css2.6 KB31.2 KB0 b2
javascript10.3 KB306.5 KB0 b7
image110.0 KB584.3 KB0 b56
favicon1.1 KB2.1 KB0 b1
svg29.3 KB87.0 KB0 b23
plain1.0 KB1.0 KB0 b1
Total160.6 KB1.4 MB0 b91

Data per domain

3 domains
DomainTotal download timeTransfer SizeContent SizeRequests
en.wikipedia.org9.002 s829.9 KB0 b33
upload.wikimedia.org56.248 s589.5 KB0 b58
auth.wikimedia.org186 ms1.7 KB0 b1

Expires & last-modified statistics

typeminmedianmax
Expires0 seconds0 seconds1 year
Last modified6 minutes9 weeks10 years

CPU

Want to dig deeper? Download the Firefox Gecko profile and drop it into profiler.firefox.com.