www.xero.com/us speed test — 20 Oct 2026

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

https://www.xero.com/us/

20 October 2026 at 13:33 UTC · Free test · report pt_da19a818e2bb

Re-test this page Test your own site

Grade

87/100

Performance88/100

Structure86/100

12 audit(s) passed, 4 need work

First byte (TTFB)424 msmeasured from this server

Fully loaded2.31 sfirst byte + slowest asset

Requests26document + assets

Page weight1.24 MBcompressed transfer

HTML document62.5 KBbr

ProtocolHTTP/3AmazonS3

Where the first byte went

DNS lookup 73 ms 17%
TCP connect 23 ms 5%
Server wait 328 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 bytefaster than 53% of 4,999 pages tested here424 ms against a median of 449 ms

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

Fully loadedslower than 68% of 4,999 pages tested here2.31 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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 424 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 1.24 MB over 26 request(s). Html files are 95% of it, so that one type is worth a look on its own.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 972 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.020), so nothing jumps under the reader's cursor.
The main thread was blocked for 530 ms, so taps and scrolling wait while scripts run.

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 www.xero.com — **Mobile** 390 × 844 · 49.3 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 paint972 msgood is under 2.5 s

Cumulative layout shift0.020under 0.1 is stable

Total blocking time530 mslong tasks during load

First contentful paint972 msfirst content on screen

Browser page weight2.96 MB123 request(s), scripts included

Failed requests6blocked or unreachable

Largest contentful paint972 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.020

Goodgood under 0.1, poor over 0.25

Total blocking time530 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 25 requests

1.18 MB 95%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 424 ms. Of that, 328 ms was the server thinking and 96 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.

Total page weight

medium impact

The page transfers 1.24 MB across 26 request(s), with the document itself at 62.5 KB.

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

Avoid extra redirects

medium impact

2 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.