bluecava.com speed test — 20 Oct 2026

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

https://bluecava.com/

20 October 2026 at 14:50 UTC · Free test · report pt_5d8a72241ed1
Grade
A
91/100
Performance97/100
Structure83/100

13 audit(s) passed, 3 need work

First byte (TTFB)306 msmeasured from this server
Fully loaded1.17 sfirst byte + slowest asset
Requests14document + assets
Page weight198.1 KBcompressed transfer
HTML document3.9 KBbr
ProtocolHTTP/3server not sent
Third-party14.9 KBother hosts

Where the first byte went

  • DNS lookup 87 ms 28%
  • TCP connect 60 ms 20%
  • Server wait 160 ms 52%

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 73% of 4,999 pages tested here306 ms against a median of 449 ms
Page weightlighter than 79% of 4,999 pages tested here198.1 KB against a median of 650.5 KB
Fully loadedfaster than 88% of 4,999 pages tested here1.17 s against a median of 1.84 s
Requestssends fewer requests than 84% of 4,999 pages tested here14 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 306 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 198.1 KB over 14 request(s), which is lean. Images files are 63% of it, so resize and recompress the largest images before anything else.
  • 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 836 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.021), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 1.03 s, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - 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.

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 bluecava.com
Mobile 390 × 844 · 42.6 KB · page is 2750 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 paint836 msgood is under 2.5 s
Cumulative layout shift0.021under 0.1 is stable
Total blocking time1.03 slong tasks during load
First contentful paint836 msfirst content on screen
Browser page weight331.5 KB20 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint836 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.021
Goodgood under 0.1, poor over 0.25
Total blocking time1.03 s
Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 6 requests
125.4 KB 63%
Javascript 4 requests
58.8 KB 30%
Css 2 requests
10.1 KB 5%

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

Top issues

Render-blocking resources

high impact

11 render-blocking resource(s) in the document head (8 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.

Image delivery and format

medium impact

0 image(s) over 200 KB and 1 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Cache static assets

medium impact

1 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

IMAGESbluecava.com/images/dma-logo.png
864 ms
IMAGESbluecava.com/images/loading.gif
815 ms
IMAGESbluecava.com/images/global/hero.jpg
754 ms
JAVASCRIPTbluecava.com/js/jquery-1.8.2.min.js
712 ms
IMAGESbluecava.com/images/iab-logo.png
711 ms
HTMLadstradata.com/wp-content/uploads/2022/04/AdstraX3Art…
580 ms
JAVASCRIPTbluecava.com/js/bluecava.js
579 ms
IMAGESbluecava.com/images/daa-logo.png
556 ms
JAVASCRIPTsync.graph.bluecava.com/js/bc.js
543 ms
CSSbluecava.com/css/main.css
531 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://bluecava.com/images/dma-logo.pngimages200864 ms4.5 KB
https://bluecava.com/images/loading.gifimages200815 ms536 B
https://bluecava.com/images/global/hero.jpgimages200754 ms107.3 KB
https://bluecava.com/js/jquery-1.8.2.min.jsjavascript200712 ms29.1 KB
https://bluecava.com/images/iab-logo.pngimages200711 ms5.4 KB
https://adstradata.com/wp-content/uploads/2022/04/[email protected] 3rd partyhtml301580 ms0 B
https://bluecava.com/js/bluecava.js?v=1.6javascript200579 ms2.4 KB
https://bluecava.com/images/daa-logo.pngimages200556 ms5.5 KB
https://sync.graph.bluecava.com/js/bc.js 3rd partyjavascript200543 ms14.9 KB
https://bluecava.com/css/main.csscss200531 ms3.0 KB
https://bluecava.com/images/favicon.icoimages200528 ms2.2 KB
https://bluecava.com/css/style.csscss200514 ms7.0 KB
https://bluecava.com/js/jquery.carouFredSel-6.2.1-packed.jsjavascript200500 ms12.4 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.