biosites.com speed test — 20 Oct 2026

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

https://biosites.com/

20 October 2026 at 16:14 UTC · Free test · report pt_5cacc55583fb

Re-test this page Test your own site

Grade

72/100

Performance75/100

Structure67/100

9 audit(s) passed, 7 need work

First byte (TTFB)154 msmeasured from this server

Fully loaded1.31 sfirst byte + slowest asset

Requests26document + assets

Page weight7.90 MBcompressed transfer

HTML document14.6 KBgzip

ProtocolHTTP/3server not sent

Third-party7.89 MBother hosts

Where the first byte went

DNS lookup 52 ms 34%
TCP connect 21 ms 14%
Server wait 81 ms 53%

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 98% of 4,999 pages tested here154 ms against a median of 449 ms

Page weightheavier than 96% of 4,999 pages tested here7.90 MB against a median of 650.3 KB

Fully loadedfaster than 82% of 4,999 pages tested here1.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 server answered in 154 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 7.90 MB over 26 request(s). Javascript files are 93% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
100% 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 696 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
The main thread was blocked for 32 ms in total, which is not enough to feel.

Fix first: Compress text responses - 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.

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 biosites.com — **Desktop** 1366 × 768 · 991.0 KB · page is 6000 px tall

Mobile screenshot of biosites.com — **Mobile** 390 × 844 · 301.8 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 paint696 msgood is under 2.5 s

Cumulative layout shift0.002under 0.1 is stable

Total blocking time32 mslong tasks during load

First contentful paint652 msfirst content on screen

Browser page weight24.94 MB71 request(s), scripts included

Failed requests10blocked or unreachable

Largest contentful paint696 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.002

Goodgood under 0.1, poor over 0.25

Total blocking time32 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 5 requests

7.38 MB 93%

Images 20 requests

526.5 KB 7%

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

Top issues

Compress text responses

high impact

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

3 render-blocking resource(s) in the document head (0 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

high impact

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

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

Third-party weight

medium impact

1 third-party host(s) serve 7.89 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: _app-f2cbe82a44a40d53.js (6.95 MB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.