ddsmain.com speed test — 20 Oct 2026

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

https://ddsmain.com/

20 October 2026 at 14:40 UTC · Free test · report pt_6ca8f06755b4
Grade
A
97/100
Performance99/100
Structure94/100

13 audit(s) passed, 2 need work

First byte (TTFB)252 msmeasured from this server
Fully loaded252 msfirst byte + slowest asset
Requests1document + assets
Page weight114 Bcompressed transfer
HTML document114 Bno compression
ProtocolHTTP/2server not sent

Where the first byte went

  • DNS lookup 74 ms 29%
  • TCP connect 22 ms 9%
  • Server wait 155 ms 62%

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 84% of 4,999 pages tested here252 ms against a median of 449 ms
Page weightlighter than 99% of 4,999 pages tested here114 B against a median of 650.5 KB
Fully loadedfaster than 100% of 4,999 pages tested here252 ms against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 252 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 114 B over 1 request(s), which is lean.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.37 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.069), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 19 ms in total, which is not enough to feel.

Fix first: Mobile viewport - Add a viewport meta tag with width=device-width and an initial scale of 1.

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 ddsmain.com
Desktop 1366 × 768 · 42.6 KB · page is 1311 px tall
Mobile screenshot of ddsmain.com
Mobile 390 × 844 · 31.0 KB · page is 844 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.37 sgood is under 2.5 s
Cumulative layout shift0.069under 0.1 is stable
Total blocking time19 mslong tasks during load
First contentful paint1.04 sfirst content on screen
Browser page weight329.6 KB23 request(s), scripts included
Failed requests4blocked or unreachable
Largest contentful paint1.37 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.069
Goodgood under 0.1, poor over 0.25
Total blocking time19 ms
Goodgood under 200 ms, poor over 600 ms

Top issues

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

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.

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.