https://query.wikidata.org/querybuilder/
Tested 2026-09-20 10:18:49 using Chrome 152.0.7977.64 (runtime settings)
Use --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.
Rendering was not meaningfully delayed. First paint landed at 464 ms on a 395 ms first byte.
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).
Style recalculation is not holding up your paint. 1 ms of restyling before the page painted, 0.2 % of the time to First Contentful Paint. Nothing here needs attention.
The recalculation work before first paint is 0.2 % of the time to First Contentful Paint.
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.
Most of this is the page being built. Only 0 style recalculations and 0 layout invalidations happened after first paint; the rest is the first render. Not much to chase here.
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 | 2 | – |
| PlatformColorChange | 1 | – |
| An element entered layout | – | 32 |
| An element left layout | – | 3 |
| Scrollbar changed | – | 1 |
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.
decodingAsyncThe page has 1 image (out of 1) 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
modernImageFormatsThe page ships 1 image (out of 1) 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
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://query.wikidata.org/querybuilder/ | 2.9 KB | 2.3 KB |
responseOkThe page has 1 error response. The page has 1 response with code 403.
Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it.
cacheHeadersLongThe page has 1 request 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.
metaDescriptionThe page is missing a meta description.
Use a page description to make the page more relevant to search engines.
viewportThe page is missing a viewport meta tag. Add <meta name="viewport" content="width=device-width, initial-scale=1"> so the browser lays the page out at the device width.
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
thirdPartyThe page do 33% requests to third party domains (1 requests and 4.5 kB). First party is 2 requests and 10 kB. The regex .*wikidata.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
unnecessaryHeadersThere are 1 response that sets both a max-age and expires header. There are 3 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://query.wikidata.org/favicon.ico has a header content-security-policy-report-only that is 872 characters long.
Do not send response headers that are too long.
referrerPolicyNo <meta name="referrer"> tag was found on the page. Set a Referrer-Policy response header (preferred) or add a meta tag, for example <meta name="referrer" content="strict-origin-when-cross-origin">.
Without an explicit referrer policy the browser falls back to the user-agent default and may leak the full URL of the previous page (including query strings) to every cross-origin request. Set a Referrer-Policy response header (preferred) or a <meta name="referrer"> tag in the document. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
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/.
xContentTypeOptionsHeaderSet X-Content-Type-Options: nosniff on the document response to prevent MIME-sniffing.
X-Content-Type-Options: nosniff prevents browsers from interpreting files as a different MIME type than what is declared in the Content-Type header. This blocks a class of cross-site scripting and content-type confusion attacks and should be set on every response. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options
thirdPartyCookiesThe page sets 1 third party cookie.
Third party cookies are used to track the user. They are automatically blocked in Safari and Firefox.
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.0s0.5s0.6s0.7sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div:eq(1) > p:eq(1)
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 | int-front |
host | 0 ms | cp3070 |
co_id | 0 ms | 174707560 |
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
https://query.wikidata.org/querybuilder/
| Header | Value |
|---|---|
content-length | 2311 |
content-type | text/html; charset=utf-8 |
date | Sun, 20 Sep 2026 10:18:50 GMT |
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 | Varnish |
server-timing | cache;desc="int-front", host;desc="cp3070",co_id;desc="174707560" |
strict-transport-security | max-age=106384710; includeSubDomains; preload |
x-analytics | |
x-cache | cp3070 int |
x-cache-status | int-front |
x-client-ip | 138.201.135.103 |
x-request-id | 87833840-9f46-4054-96eb-532ae0fcc766 |
| URL | Type | Transfer Size | Content Size |
|---|---|---|---|
| https://query.wikidata.org/favicon.ico | favicon | 6.8 KB | 14.7 KB |
| https://www.wikimedi...ages/wmf-logo.png | image | 4.4 KB | 3.2 KB |
| https://query.wikidata.org/querybuilder/ | html | 2.9 KB | 2.3 KB |
Transfer size11.2 KB
Content size18.0 KB
Requests2
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| image | 0 b | 4.4 KB | 3.2 KB | 1 |
| favicon | 0 b | 6.8 KB | 14.7 KB | 1 |
| Total | 0 b | 11.2 KB | 18.0 KB | 2 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| query.wikidata.org | 609 ms | 9.7 KB | 17.0 KB | 2 |
| www.wikimedia.org | 192 ms | 4.4 KB | 3.2 KB | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 hour | 1 year |
| Last modified | 4 weeks | 7 weeks | 10 weeks |
The page logs the following messages to the console.
| Level | Message |
|---|---|
| SEVERE | https://query.wikidata.org/querybuilder/ - Failed to load resource: the server responded with a status of 403 () |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 6.8 KB | 1 |
| Total | 6.8 KB | 1 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 6.8 KB | 1 |
| Total | 6.8 KB | 1 |
Tasks ≥ 50 ms blocking the main thread, collected via the Long Task API.
✓ No long tasks observed during this run.
All main-thread work during the full page load, not just the share that blocked input. Calculated from the Chrome trace.
parseHTMLstyleLayoutscriptParseCompilescriptEvaluationpaintCompositeRendergarbageCollectionotherMain-thread CPU time from the Chrome trace split by domain. First party is wikidata.org.
Want to dig deeper? Download the Chrome trace and drag-and-drop it into Performance in DevTools.