www.booking.com speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 13:22 UTC. Grade B (88/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 96 ms 19%
- TCP connect 36 ms 7%
- Server wait 366 ms 73%
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
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 498 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 810.1 KB over 3 request(s), which is lean. Javascript files are 83% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- The main thread was blocked for 133 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.
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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 3 request(s) in total, 810.1 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 498 ms. Of that, 366 ms was the server thinking and 132 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.
Compress text responses
high impact2 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 806.2 KB of compressible text.
Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.
Cache static assets
medium impact1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.
Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.
JavaScript weight
medium impact1 JavaScript file(s) over 200 KB: challenge.js (675.1 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 impact1 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.
Waterfall
Slowest requests
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://www.booking.com/referrer | html | 200 | 595 ms | 131.2 KB |
| https://www.booking.com/__challenge_h78IRKX3kpQxScCExxShBNwRUlb/d8c14d4960ca/a18a4859af9c/challenge.js | javascript | 200 | 396 ms | 675.1 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.