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

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

https://www.byd.com/us

20 October 2026 at 14:23 UTC · Free test · report pt_ea0827d30c2f

Re-test this page Test your own site

Grade

88/100

Performance92/100

Structure83/100

13 audit(s) passed, 3 need work

First byte (TTFB)427 msmeasured from this server

Fully loaded2.02 sfirst byte + slowest asset

Requests26document + assets

Page weight62.8 KBcompressed transfer

HTML document15.1 KBbr

ProtocolHTTP/3Tengine

Third-party47.8 KBother hosts

Where the first byte went

DNS lookup 215 ms 50%
TCP connect 60 ms 14%
Server wait 151 ms 35%

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 here427 ms against a median of 449 ms

Page weightlighter than 90% of 4,999 pages tested here62.8 KB against a median of 650.5 KB

Fully loadedslower than 58% of 4,999 pages tested here2.02 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 427 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 62.8 KB over 26 request(s). Javascript files are 76% 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.
76% 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 2.04 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.076), so nothing jumps under the reader's cursor.
The main thread was blocked for 277 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.

Desktop screenshot of www.byd.com — **Desktop** 1366 × 768 · 725.0 KB · page is 3473 px tall

Mobile screenshot of www.byd.com — **Mobile** 390 × 844 · 146.0 KB · page is 3467 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 paint2.04 sgood is under 2.5 s

Cumulative layout shift0.076under 0.1 is stable

Total blocking time277 mslong tasks during load

First contentful paint1.03 sfirst content on screen

Browser page weight4.03 MB86 request(s), scripts included

Failed requests8blocked or unreachable

Largest contentful paint2.04 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.076

Goodgood under 0.1, poor over 0.25

Total blocking time277 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 16 requests

47.8 KB 76%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 427 ms. Of that, 151 ms was the server thinking and 275 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

12 render-blocking resource(s) in the document head (3 script(s), 9 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.

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.