www.band.us speed test — 20 Oct 2026

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

https://www.band.us/

20 October 2026 at 14:12 UTC · Free test · report pt_ee2be97b4667

Re-test this page Test your own site

Grade

82/100

Performance86/100

Structure77/100

10 audit(s) passed, 6 need work

First byte (TTFB)589 msmeasured from this server

Fully loaded1.12 sfirst byte + slowest asset

Requests11document + assets

Page weight1.31 MBcompressed transfer

HTML document5.3 KBgzip

ProtocolHTTP/3nfront

Third-party1.30 MBother hosts

Where the first byte went

DNS lookup 77 ms 13%
TCP connect 54 ms 9%
Server wait 458 ms 78%

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 byteslower than 62% of 4,999 pages tested here589 ms against a median of 448 ms

Page weightheavier than 70% of 4,999 pages tested here1.31 MB against a median of 650.3 KB

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

Requestssends fewer requests than 87% of 4,999 pages tested here11 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 took 589 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 1.31 MB over 11 request(s), which is lean. Javascript files are 80% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
100% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 752 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Desktop screenshot of www.band.us — **Desktop** 1366 × 768 · 258.3 KB · page is 6000 px tall

Mobile screenshot of www.band.us — **Mobile** 390 × 844 · 114.7 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint752 msgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint700 msfirst content on screen

Browser page weight4.31 MB80 request(s), scripts included

Largest contentful paint752 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking timenone over 50 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests

1.04 MB 80%

Css 5 requests

258.4 KB 19%

Images 2 requests

4.5 KB 0%

Transfer size, compressed as sent. 11 request(s) in total, 1.31 MB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 589 ms. Of that, 458 ms was the server thinking and 131 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (0 script(s), 5 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

medium impact

The page transfers 1.31 MB across 11 request(s), with the document itself at 5.3 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

1 third-party host(s) serve 1.30 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: boot.bundle.js (994.8 KB)

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