bustimes.org speed test — 20 Oct 2026

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

https://bustimes.org/

20 October 2026 at 15:56 UTC · Free test · report pt_1f9521d8689c
Grade
A
93/100
Performance92/100
Structure95/100

15 audit(s) passed, 1 need work

First byte (TTFB)515 msmeasured from this server
Fully loaded1.27 sfirst byte + slowest asset
Requests7document + assets
Page weight194.5 KBcompressed transfer
HTML document2.5 KBbr
ProtocolHTTP/3cloudflare
Third-party181.3 KBother hosts

Where the first byte went

  • DNS lookup 78 ms 15%
  • TCP connect 41 ms 8%
  • Server wait 396 ms 77%

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 56% of 4,999 pages tested here515 ms against a median of 448 ms
Page weightlighter than 80% of 4,999 pages tested here194.5 KB against a median of 650.5 KB
Fully loadedfaster than 84% of 4,999 pages tested here1.27 s against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 515 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 194.5 KB over 7 request(s), which is lean. Javascript files are 95% 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.
  • 93% 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 664 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.025), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 77 ms in total, which is not enough to feel.

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.

Mobile screenshot of bustimes.org
Mobile 390 × 844 · 57.1 KB · page is 1590 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 paint664 msgood is under 2.5 s
Cumulative layout shift0.025under 0.1 is stable
Total blocking time77 mslong tasks during load
First contentful paint664 msfirst content on screen
Browser page weight10.14 MB302 request(s), scripts included
Failed requests12blocked or unreachable
Largest contentful paint664 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.025
Goodgood under 0.1, poor over 0.25
Total blocking time77 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
183.8 KB 95%
Css 1 request
5.9 KB 3%
Images 2 requests
2.1 KB 1%
Other 1 request
147 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 515 ms. Of that, 396 ms was the server thinking and 119 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.

Waterfall

Slowest requests

OTHERbustimes.org/static/manifest.a723b3ad7751.webmanifest
751 ms
IMAGESbustimes.org/favicon.ico
524 ms
JAVASCRIPTbustimes.org/static/consent.12e2f74a2e79.js
463 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
457 ms
CSSbustimes.org/static/dist/css/style.6ffeb0a59230.css
447 ms
IMAGESbustimes.org/static/svg/bimi.aeab251d5167.svg
405 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://bustimes.org/static/manifest.a723b3ad7751.webmanifestother200751 ms147 B
https://bustimes.org/favicon.icoimages200524 ms921 B
https://bustimes.org/static/consent.12e2f74a2e79.jsjavascript200463 ms2.5 KB
https://www.googletagmanager.com/gtag/js?id=G-X2Z0KM7Z5C 3rd partyjavascript200457 ms181.3 KB
https://bustimes.org/static/dist/css/style.6ffeb0a59230.csscss200447 ms5.9 KB
https://bustimes.org/static/svg/bimi.aeab251d5167.svgimages200405 ms1.2 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.