doctoreto.com speed test — 20 Oct 2026

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

https://doctoreto.com/

20 October 2026 at 15:58 UTC · Free test · report pt_406228db6e8e

Re-test this page Test your own site

Grade

74/100

Performance66/100

Structure85/100

13 audit(s) passed, 3 need work

First byte (TTFB)1.15 smeasured from this server

Fully loaded3.62 sfirst byte + slowest asset

Requests26document + assets

Page weight296.7 KBcompressed transfer

HTML document231.9 KBgzip

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 62 ms 5%
TCP connect 263 ms 23%
Server wait 828 ms 72%

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 90% of 4,999 pages tested here1.15 s against a median of 448 ms

Page weightlighter than 72% of 4,999 pages tested here296.7 KB against a median of 650.5 KB

Fully loadedslower than 87% of 4,999 pages tested here3.62 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 1.15 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 296.7 KB over 26 request(s).
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 2.20 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
The main thread was blocked for 1.52 s, 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 doctoreto.com — **Mobile** 390 × 844 · 126.9 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 paint2.20 sgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time1.52 slong tasks during load

First contentful paint2.20 sfirst content on screen

Browser page weight2.57 MB141 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint2.20 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time1.52 s

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 9 requests

64.9 KB 22%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1154 ms. Of that, 828 ms was the server thinking and 325 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.

HTML document size

medium impact

The document transfers 231.9 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.