www.nicovideo.jp speed test — 20 Oct 2026

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

https://www.nicovideo.jp/

20 October 2026 at 13:18 UTC · Free test · report pt_d1bf5aaa7290
Grade
B
84/100
Performance86/100
Structure82/100

10 audit(s) passed, 6 need work

First byte (TTFB)682 msmeasured from this server
Fully loaded1.65 sfirst byte + slowest asset
Requests17document + assets
Page weight568.0 KBcompressed transfer
HTML document17.9 KBgzip
ProtocolHTTP/3Apache
Third-party541.8 KBother hosts

Where the first byte went

  • DNS lookup 74 ms 11%
  • TCP connect 43 ms 6%
  • Server wait 565 ms 83%

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 69% of 4,999 pages tested here682 ms against a median of 448 ms
Page weightlighter than 54% of 4,999 pages tested here568.0 KB against a median of 650.5 KB
Fully loadedfaster than 61% of 4,999 pages tested here1.65 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 took 682 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 568.0 KB over 17 request(s). Javascript files are 88% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 95% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 1.38 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 899 ms, 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 www.nicovideo.jp
Mobile 390 × 844 · 265.6 KB · page is 5639 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.38 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time899 mslong tasks during load
First contentful paint1.38 sfirst content on screen
Browser page weight5.34 MB390 request(s), scripts included
Failed requests39blocked or unreachable
Largest contentful paint1.38 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time899 ms
Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests
497.2 KB 88%
Css 1 request
36.0 KB 6%
Html 4 requests
8.4 KB 1%
Images 5 requests
8.4 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 682 ms. Of that, 565 ms was the server thinking and 117 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.

Third-party weight

medium impact

4 third-party host(s) serve 541.8 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: vendor.js (418.0 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

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.

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.

Waterfall

Slowest requests

HTMLwww.nicovideo.jp/{{values.icon.url}}
964 ms
HTMLwww.nicovideo.jp/{{values.banner.url}}
728 ms
HTMLwww.nicovideo.jp/{{thumbnail}}
725 ms
IMAGESresource.video.nimg.jp/web/images/favicon_uni/48.png
640 ms
HTMLwww.googletagmanager.com/ns.html
639 ms
IMAGESresource.video.nimg.jp/web/images/favicon_uni/32.png
629 ms
JAVASCRIPTresource.video.nimg.jp/web/scripts/bundle/pages_index_TopPage.js
623 ms
IMAGESresource.video.nimg.jp/web/images/favicon_uni/144.png
623 ms
JAVASCRIPTres.ads.nicovideo.jp/assets/js/ads2.js
622 ms
IMAGESresource.video.nimg.jp/web/images/favicon_uni/96.png
622 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://www.nicovideo.jp/{{values.icon.url}}html404964 ms2.7 KB
https://www.nicovideo.jp/{{values.banner.url}}html404728 ms2.7 KB
https://www.nicovideo.jp/{{thumbnail}}html404725 ms2.7 KB
https://resource.video.nimg.jp/web/images/favicon_uni/48.png?re 3rd partyimages200640 ms1.1 KB
https://www.googletagmanager.com/ns.html?id=GTM-KTTXCBK 3rd partyhtml200639 ms200 B
https://resource.video.nimg.jp/web/images/favicon_uni/32.png?re 3rd partyimages200629 ms695 B
https://resource.video.nimg.jp/web/scripts/bundle/pages_index_TopPage.js?1792468514 3rd partyjavascript200623 ms23.7 KB
https://resource.video.nimg.jp/web/images/favicon_uni/144.png?re 3rd partyimages200623 ms3.3 KB
https://res.ads.nicovideo.jp/assets/js/ads2.js?ref=www 3rd partyjavascript200622 ms21.9 KB
https://resource.video.nimg.jp/web/images/favicon_uni/96.png?re 3rd partyimages200622 ms2.2 KB
https://assets.embed.res.nimg.jp/js/api.js 3rd partyjavascript200620 ms33.6 KB
https://resource.video.nimg.jp/web/images/favicon_uni/favicon.ico?re 3rd partyimages200617 ms1.1 KB
https://resource.video.nimg.jp/web/scripts/bundle/vendor.js?1792468514 3rd partyjavascript200614 ms418.0 KB
https://resource.video.nimg.jp/web/styles/bundle/pages_index_TopPage.css?1792468514 3rd partycss200597 ms36.0 KB
https://www.nicovideo.jp/{{ this }}other00 ms0 B
https://www.nicovideo.jp/{{ values.thumbnail.url }}other00 ms0 B
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.