www.ultimate-guitar.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:40 UTC. Grade A (94/100), with the screenshots, the timings and the fixes that matter.

https://www.ultimate-guitar.com/

20 October 2026 at 12:40 UTC · Free test · report pt_04d5728bfb2a

Re-test this page Test your own site

Grade

94/100

Performance95/100

Structure92/100

13 audit(s) passed, 3 need work

First byte (TTFB)371 msmeasured from this server

Fully loaded1.20 sfirst byte + slowest asset

Requests17document + assets

Page weight571.5 KBcompressed transfer

HTML document27.5 KBbr

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 49 ms 13%
TCP connect 2 ms 1%
Server wait 320 ms 86%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 61% of 4,999 pages tested here371 ms against a median of 449 ms

Page weightlighter than 54% of 4,999 pages tested here571.5 KB against a median of 650.5 KB

Fully loadedfaster than 87% of 4,999 pages tested here1.20 s against a median of 1.84 s

Requestssends fewer requests than 82% of 4,999 pages tested here17 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The first byte arrived in 371 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 571.5 KB over 17 request(s). Javascript files are 64% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.

Fix first: JavaScript weight - Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Javascript 4 requests

364.1 KB 64%

Fonts 2 requests

154.4 KB 27%

Images 9 requests

25.1 KB 4%

Other 1 request

361 B 0%

Transfer size, compressed as sent. 17 request(s) in total, 571.5 KB across all of them.

Top issues

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: ug.6570aa6ff7765d52f24ad17e6613f38a.js (274.6 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.