booksy.com/en-us speed test — 20 Oct 2026

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

https://booksy.com/en-us/

20 October 2026 at 15:42 UTC · Free test · report pt_64b12979aed4

Re-test this page Test your own site

Grade

77/100

Performance84/100

Structure67/100

8 audit(s) passed, 8 need work

First byte (TTFB)694 msmeasured from this server

Fully loaded1.79 sfirst byte + slowest asset

Requests26document + assets

Page weight1.06 MBcompressed transfer

HTML document677.6 KBno compression

ProtocolHTTP/3istio-envoy

Third-party405.9 KBother hosts

Where the first byte went

DNS lookup 74 ms 11%
TCP connect 68 ms 10%
Server wait 553 ms 80%

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 69% of 4,999 pages tested here694 ms against a median of 448 ms

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

Fully loadedfaster than 52% of 4,999 pages tested here1.79 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 took 694 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.06 MB over 26 request(s).
It runs over HTTP/3, so the assets share a connection instead of opening one each.
37% 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 1.07 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.093), so nothing jumps under the reader's cursor.
The main thread was blocked for 764 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 booksy.com — **Mobile** 390 × 844 · 169.4 KB · page is 5471 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 paint1.07 sgood is under 2.5 s

Cumulative layout shift0.093under 0.1 is stable

Total blocking time764 mslong tasks during load

First contentful paint1.04 sfirst content on screen

Browser page weight4.68 MB422 request(s), scripts included

Failed requests8blocked or unreachable

Largest contentful paint1.07 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.093

Goodgood under 0.1, poor over 0.25

Total blocking time764 ms

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 24 requests

289.5 KB 27%

Other 1 request

116.4 KB 11%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 694 ms. Of that, 553 ms was the server thinking and 142 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 impact

0 text response(s) of 10 KB or more are sent uncompressed, and the document itself is compressed. That is 0 B 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.

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (2 script(s), 3 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.06 MB across 26 request(s), with the document itself at 677.6 KB.

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

Cache static assets

medium impact

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

Waterfall

Slowest requests

IMAGESd1naav5lcrqyn7.cloudfront.net/1.440.0/mp-2026-public/images/page-mai…

1.10 s

IMAGESd1naav5lcrqyn7.cloudfront.net/1.440.0/mp-2026-public/images/page-mai…

1.09 s