ad-contents.jp speed test — 20 Oct 2026

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

https://ad-contents.jp/

20 October 2026 at 12:54 UTC · Free test · report pt_910376d82f99
Grade
B
88/100
Performance87/100
Structure89/100

13 audit(s) passed, 3 need work

First byte (TTFB)667 msmeasured from this server
Fully loaded1.64 sfirst byte + slowest asset
Requests11document + assets
Page weight235.6 KBcompressed transfer
HTML document1.4 KBgzip
ProtocolHTTP/2Apache

Where the first byte went

  • DNS lookup 53 ms 8%
  • TCP connect 141 ms 21%
  • Server wait 473 ms 71%

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 67% of 4,999 pages tested here667 ms against a median of 448 ms
Page weightlighter than 77% of 4,999 pages tested here235.6 KB against a median of 650.5 KB
Fully loadedfaster than 61% of 4,999 pages tested here1.64 s against a median of 1.84 s
Requestssends fewer requests than 87% of 4,999 pages tested here11 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 667 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 235.6 KB over 11 request(s), which is lean. Images files are 98% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.15 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 35 ms in total, which is not enough to feel.

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 ad-contents.jp
Mobile 390 × 844 · 103.0 KB · page is 2771 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.15 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time35 mslong tasks during load
First contentful paint916 msfirst content on screen
Browser page weight235.6 KB11 request(s), scripts included
Largest contentful paint1.15 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time35 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 8 requests
231.8 KB 98%
Css 2 requests
2.4 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 667 ms. Of that, 473 ms was the server thinking and 194 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.

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.

Waterfall

Slowest requests

IMAGESad-contents.jp/assets/top/pc/img/mainvisual_calculate…
976 ms
IMAGESad-contents.jp/assets/top/pc/img/mainvisual_calendar.png
938 ms
IMAGESad-contents.jp/assets/top/pc/img/icon_calendar.png
905 ms
IMAGESad-contents.jp/assets/top/pc/img/icon_eitango.png
877 ms
IMAGESad-contents.jp/assets/top/pc/img/mainvisual_eitango.png
853 ms
IMAGESad-contents.jp/assets/top/pc/img/mainvisual_quiz.png
840 ms
CSSad-contents.jp/assets/top/pc/css/sanitize.css
814 ms
CSSad-contents.jp/assets/top/pc/css/style.min.css
808 ms
IMAGESad-contents.jp/assets/top/pc/img/icon_quiz.png
798 ms
IMAGESad-contents.jp/assets/top/pc/img/icon_calculate.png
785 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://ad-contents.jp/assets/top/pc/img/mainvisual_calculate.png?v=20220615101040images200976 ms65.2 KB
https://ad-contents.jp/assets/top/pc/img/mainvisual_calendar.png?v=20220615101040images200938 ms26.9 KB
https://ad-contents.jp/assets/top/pc/img/icon_calendar.png?v=20220615101040images200905 ms11.3 KB
https://ad-contents.jp/assets/top/pc/img/icon_eitango.png?v=20220615101040images200877 ms8.8 KB
https://ad-contents.jp/assets/top/pc/img/mainvisual_eitango.png?v=20220615101040images200853 ms46.5 KB
https://ad-contents.jp/assets/top/pc/img/mainvisual_quiz.png?v=20220615101040images200840 ms40.8 KB
https://ad-contents.jp/assets/top/pc/css/sanitize.css?v=20220615101040css200814 ms1.6 KB
https://ad-contents.jp/assets/top/pc/css/style.min.css?v=20220615101040css200808 ms916 B
https://ad-contents.jp/assets/top/pc/img/icon_quiz.png?v=20220615101040images200798 ms13.2 KB
https://ad-contents.jp/assets/top/pc/img/icon_calculate.png?v=20220615101040images200785 ms19.1 KB
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.