Run 1 summary

Summary

Metric	Value
Page metrics
Performance score	86
Total page size	221.5 KB
Requests	15
Timing metrics
TTFB	764 ms
First Paint	2.035 s
Fully Loaded	2.630 s
Google Web Vitals
TTFB	764 ms
First Contentful Paint (FCP)	2.035 s
Largest Contentful Paint (LCP)	2.035 s
Cumulative Layout Shift (CLS)	0.00
640 ms
CPU metrics
CPU long tasks	1
CPU last long task happens at	1.863 s
Visual Metrics
First Visual Change	2.033 s
Speed Index	2.040 s
Visual Complete 85%	2.033 s
Visual Complete 99%	2.333 s
Last Visual Change	2.333 s

Waterfall

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

1.6 sDOM Content Loaded Time 1.517 sPage Load Time 1.517 s

1.9 sCPU Long Task duration 86 ms

2.1 sFirst Visual Change 2.033 sVisual Complete 85% 2.033 sVisual Complete 95% 2.033 sFirst Contentful Paint 2.035 sLCP <P> 2.035 s

2.2 s

2.3 s

2.4 sLast Visual Change 2.333 sVisual Complete 99% 2.333 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.0.2.

Coach score

• Total score 89
• Performance score 86
• Privacy score 94
• Best practice score 90

Performance advice (86)

Show/hide details

Title	Advice	Score
Have a fast first contentful paint (firstContentfulPaint)	First contentful paint can be improved (2.035 s). It is in the Google Web Vitals needs improvement range, slower than 1.8 seconds.	50
Description: 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.
Avoid CPU Long Tasks (longTasks)	The page has 1 CPU long task with the total of 86 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 86 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: unknown
Avoid extra requests by setting cache headers (cacheHeaders)	The page has 4 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 NaN undefined the next access.	60
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: https://query.wikidata.org/querybuilder/wikit-Icon-296004 https://query.wikidata.org/querybuilder/wikit-Icon-468691 https://query.wikidata.org/querybuilder/wikit-Icon-315409 https://query.wikidata.org/querybuilder/wikit-Icon-30325
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.df3b4cfb.js https://query.wikidata.org/querybuilder/assets/vendor.5730e773.js https://query.wikidata.org/querybuilder/assets/index.e0b88c88.css https://query.wikidata.org/querybuilder/i18n/en.json https://query.wikidata.org/favicon.ico 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 167 kB and the uncompressed size is 524.2 kB. This is quite large.	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: URL Transfer size Content size https://query.wikidata.org/querybuilder/assets/index.df3b4cfb.js 21.4 KB 86.0 KB https://query.wikidata.org/querybuilder/assets/vendor.5730e773.js 141.8 KB 425.9 KB
Make each CSS response small (optimalCssSize)	https://query.wikidata.org/querybuilder/assets/index.e0b88c88.css size is 39.8 kB (39772) 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.e0b88c88.css 38.8 KB 346.7 KB
Avoid missing and error requests (responseOk)	The page has 4 error responses. The page has 4 responses with code 404.	60
Description: 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.
Offenders: https://query.wikidata.org/querybuilder/wikit-Icon-296004 https://query.wikidata.org/querybuilder/wikit-Icon-468691 https://query.wikidata.org/querybuilder/wikit-Icon-315409 https://query.wikidata.org/querybuilder/wikit-Icon-30325

Best practice advice (90)

Show/hide details

Title	Advice	Score
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 15 responses that sets a server header.	85
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.df3b4cfb.js https://query.wikidata.org/querybuilder/assets/vendor.5730e773.js https://query.wikidata.org/querybuilder/assets/index.e0b88c88.css https://query.wikidata.org/querybuilder/i18n/en.json https://query.wikidata.org/favicon.ico 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/wikit-Icon-296004 https://query.wikidata.org/querybuilder/wikit-Icon-468691 https://query.wikidata.org/querybuilder/wikit-Icon-315409 https://query.wikidata.org/querybuilder/wikit-Icon-30325 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 (94)

Show/hide details

Title	Advice	Score
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	1904
Height	1225
DOM elements	917
Avg DOM depth	11
Max DOM depth	26
Iframes	0
Script tags	1
Local storage	0 b
Session storage	0 b
Network Information API	3g

Technologies used to build the page.

Data collected using Wappalyzerversion 6.10.66.  Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyser find more information about technologies used.

Technology	Confidence	Category
Apache HTTP Server	100	Web servers
HSTS	100	Security

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	2.035 s
Elements that needed recalculate style before LCP	394
Time spent in recalculate style before LCP	17.578 ms
Load time	0 ms
Size (width*height)	75032
DOM path
div#app > div > main > p> 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.

Detected Cumulative Layout Shift

No layout shift detected.

Interaction to Next Paint

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.

Long Animation Frames

Read more about the Long Animation Frames API here here.

The top 10 longest animation frames entries

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.

CDP Performance

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

Console log

The page logs the following messages to the console.

Requests loaded after onLoad event

Included requests done after load event end.

Requests loaded after onContentLoad

Includes requests done after DOM content loaded.

Render blocking requests

Render blocking information directly from Chrome.

Render information

CPU

Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.

Long Tasks

Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.

CPU last long task happened at 1.863 s

Individual Long Tasks

CPU time spent

Calculated using Tracium.

Screenshots

afterPageCompleteCheck.jpg

layoutShift.jpg

largestContentfulPaint.jpg