www.dmm.co.jp/en/age_check/=?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F speed test — 20 Oct 2026

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

https://www.dmm.co.jp/en/age_check/=/?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F

20 October 2026 at 12:40 UTC · Free test · report pt_68642d65b114

Re-test this page Test your own site

Grade

91/100

Performance95/100

Structure85/100

13 audit(s) passed, 3 need work

First byte (TTFB)374 msmeasured from this server

Fully loaded1.38 sfirst byte + slowest asset

Requests17document + assets

Page weight410.2 KBcompressed transfer

HTML document6.4 KBgzip

ProtocolHTTP/3server not sent

Third-party2.0 KBother hosts

Where the first byte went

DNS lookup 57 ms 15%
TCP connect 27 ms 7%
Server wait 290 ms 78%

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

Page weightlighter than 64% of 4,999 pages tested here410.2 KB against a median of 650.5 KB

Fully loadedfaster than 78% of 4,999 pages tested here1.38 s against a median of 1.84 s

Requestssends fewer requests than 82% of 4,999 pages tested here17 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 374 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 410.2 KB over 17 request(s). Html files are 98% 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.
The largest element painted at 512 ms, inside the 2.5 s Google calls good.
The main thread was blocked for 123 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.

Mobile screenshot of www.dmm.co.jp — **Mobile** 390 × 844 · 35.7 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 paint512 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time123 mslong tasks during load

First contentful paint512 msfirst content on screen

Browser page weight1.08 MB37 request(s), scripts included

Failed requests1blocked or unreachable

Largest contentful paint512 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time123 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 14 requests

402.0 KB 98%

Javascript 2 requests

1.9 KB 0%

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

Top issues

Compress text responses

high impact

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

Avoid extra redirects

medium impact

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