www.demonware.net speed test — 20 Oct 2026

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

https://www.demonware.net/

20 October 2026 at 15:16 UTC · Free test · report pt_db1c9ca9ad8c

Re-test this page Test your own site

Grade

83/100

Performance84/100

Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)378 msmeasured from this server

Fully loaded4.54 sfirst byte + slowest asset

Requests26document + assets

Page weight249.8 KBcompressed transfer

HTML document7.7 KBgzip

ProtocolHTTP/3server not sent

Third-party113.3 KBother hosts

Where the first byte went

DNS lookup 64 ms 17%
TCP connect 55 ms 15%
Server wait 259 ms 69%

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

Page weightlighter than 76% of 4,999 pages tested here249.8 KB against a median of 650.5 KB

Fully loadedslower than 89% of 4,999 pages tested here4.54 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 arrived in 378 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 249.8 KB over 26 request(s). Other files are 51% of it, so that one type is worth a look on its own.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
45% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Other 13 requests

127.8 KB 51%

Images 12 requests

114.3 KB 46%

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

Top issues

Render-blocking resources

high impact

7 render-blocking resource(s) in the document head (3 script(s), 4 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.

Avoid extra redirects

medium impact

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

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.