Run 2 summary

Summary

Metric	Value
Page metrics
Performance score	97
Total page size	199.3 KB
Requests	11
Timing metrics
TTFB	667 ms
First Paint	931 ms
Fully Loaded	1.569 s
Google Web Vitals
TTFB	667 ms
First Contentful Paint (FCP)	1.423 s
Largest Contentful Paint (LCP)	1.428 s
Visual Metrics
First Visual Change	1.466 s
Speed Index	1.495 s
Visual Complete 85%	1.466 s
Visual Complete 99%	2.500 s
Last Visual Change	2.566 s

Waterfall

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

1.3 sDOM Content Loaded Time 1.241 sPage Load Time 1.245 s

1.5 sFirst Contentful Paint 1.423 sLCP <P> 1.428 sFirst Visual Change 1.466 sVisual Complete 85% 1.466 s

1.6 sVisual Complete 95% 1.533 sFully Loaded 1.569 s

1.7 s

1.8 s

2.5 sVisual Complete 99% 2.500 s

2.6 sLast Visual Change 2.566 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 8.1.1.

Coach score

• Total score 91
• Performance score 97
• Privacy score 88
• Best practice score 74

Performance advice (97)

Show/hide details

Title	Advice	Score
Avoid slowing down the critical rendering path (avoidRenderBlocking)	The style https://query.wikidata.org/querybuilder/assets/index.81b2e6d1.css is larger than the magic number TCP window size 14.5 kB. Make the file smaller and the page will render faster. Avoid loading synchronously JavaScript inside of head, you shouldn't need JavaScript to render your page! The page has 1 render blocking CSS request and 1 blocking JavaScript request inside of head.	85
Description: The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS for really fast rendering and a short rendering path.
Offenders: https://query.wikidata.org/querybuilder/assets/index.81b2e6d1.css https://query.wikidata.org/querybuilder/assets/index.727c9d3b.js
Long cache headers is good (cacheHeadersLong)	The page has 9 requests that have a shorter cache time than 30 days (but still a cache time).	91
Description: Setting a cache header is good. Setting a long cache header (at least 30 days) is even better beacause then it will stay long in the browser cache. But what do you do if that asset change? Rename it and the browser will pick up the new version.
Offenders: https://query.wikidata.org/querybuilder/assets/index.727c9d3b.js https://query.wikidata.org/querybuilder/assets/index.81b2e6d1.css https://query.wikidata.org/querybuilder/i18n/en.json https://query.wikidata.org/favicon.ico https://query.wikidata.org/querybuilder/i18n/en.json https://query.wikidata.org/querybuilder/img/QB_Logo.svg https://query.wikidata.org/querybuilder/img/close.svg https://query.wikidata.org/querybuilder/img/search.svg https://query.wikidata.org/querybuilder/img/clear.svg
Total JavaScript size shouldn't be too big (javascriptSize)	The total JavaScript transfer size is 164.5 kB. This is quite large.	50
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: URL Transfer size Content size https://query.wikidata.org/querybuilder/assets/index.727c9d3b.js 160.7 KB 0 b
Make each CSS response small (optimalCssSize)	https://query.wikidata.org/querybuilder/assets/index.81b2e6d1.css size is 20.2 kB (20231) 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: URL Transfer size Content size https://query.wikidata.org/querybuilder/assets/index.81b2e6d1.css 19.8 KB 0 b

Best practice advice (74)

Show/hide details

Title	Advice	Score
Cumulative Layout Shift (cumulativeLayoutShift)	Layout Shift is not supported in this browser	0
Description: 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.
Meta description (metaDescription)	The page is missing a meta description.	0
Description: Use a page description to make the page more relevant to search engines.
Avoid unnecessary headers (unnecessaryHeaders)	There are 11 responses that sets a server header.	89
Description: 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: https://query.wikidata.org/querybuilder/ https://query.wikidata.org/querybuilder/assets/index.727c9d3b.js https://query.wikidata.org/querybuilder/assets/index.81b2e6d1.css https://query.wikidata.org/querybuilder/i18n/en.json https://query.wikidata.org/favicon.ico https://query.wikidata.org/querybuilder/i18n/en.json https://www.wikidata.org/beacon/statsv?Wikidata.query-builder.main-page-loaded=1c https://query.wikidata.org/querybuilder/img/QB_Logo.svg https://query.wikidata.org/querybuilder/img/close.svg https://query.wikidata.org/querybuilder/img/search.svg https://query.wikidata.org/querybuilder/img/clear.svg

Privacy advice (88)

Show/hide details

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: https://query.wikidata.org/querybuilder/
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: https://query.wikidata.org/querybuilder/

Page info

Page info
Title	Wikidata Query Builder
Width	1920
Height	1261
DOM elements	958
Avg DOM depth	12
Max DOM depth	25
Iframes	0
Script tags	1
Local storage	0 b
Session storage	0 b
Network Information API	unknown

Technologies used to build the page.

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
Debian	100	Operating systems
Apache HTTP Server 2.4.59	100	Web servers
HSTS	100	Security
HTTP/2	100	Miscellaneous

Visual Metrics

Browser Metrics

Largest Contentful Paint

When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.

Element type	P
Element/tag	<p class="querybuilder__description"></p>
Render time	1.428 s
Element render delay	761 ms
TTFB	667 ms
Resource delay	0 ms
Resource load duration	0 ms
Load time	0 ms
Size (width*height)	13520
DOM path
div#app > div#app > div > main > p> div#app > div#app > div > main > p>

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.

Server timings

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 Elements

PageXray

How the page is built.

Largest assets on the page (by transfer size)

Requests and sizes per content type

Data per domain

Expires and last modified statistics

CPU

Screenshots

afterPageCompleteCheck.jpg

largestContentfulPaint.jpg