www.tv-tokyo.co.jp speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 16:14 UTC. Grade A (90/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 69 ms 15%
- TCP connect 53 ms 12%
- Server wait 332 ms 73%
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
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 453 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 420.8 KB over 22 request(s). Javascript files are 62% 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.
- The largest element painted at 1.30 s, inside the 2.5 s Google calls good.
- Layout shift is 0.151 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
- The main thread was blocked for 675 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.
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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 22 request(s) in total, 420.8 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 453 ms. Of that, 332 ms was the server thinking and 122 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.
Cache static assets
medium impact18 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.
Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.
Avoid extra redirects
medium impact1 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 impactHSTS 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
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://js.hs-scripts.com/47285213.js 3rd party | javascript | 307 | 1.18 s | 0 B |
| https://www.tv-tokyo.co.jp/tbcms/javascripts/index.js | javascript | 200 | 1.17 s | 9.0 KB |
| https://www.tv-tokyo.co.jp/txcms/media/biz/txtop_bizranking_biz_bnr.jpg | images | 200 | 1.13 s | 30.8 KB |
| https://www.tv-tokyo.co.jp/tbcms/javascripts/index.banners.js | javascript | 200 | 1.08 s | 27.3 KB |
| https://www.tv-tokyo.co.jp/tbcms/javascripts/common.js | javascript | 200 | 977 ms | 1.5 KB |
| https://www.tv-tokyo.co.jp/tbcms/assets/images/icon_sns_youtube.svg | images | 200 | 977 ms | 531 B |
| https://www.tv-tokyo.co.jp/tbcms/javascripts/library.min.js | javascript | 200 | 895 ms | 115.7 KB |
| https://www.tv-tokyo.co.jp/tbcms/javascripts/layout.js | javascript | 200 | 883 ms | 55.9 KB |
| https://www.tv-tokyo.co.jp/tbcms/javascripts/header.js | javascript | 200 | 879 ms | 466 B |
| https://www.tv-tokyo.co.jp/tbcms/assets/images/icon_sns_facebook.svg | images | 200 | 862 ms | 573 B |
| https://www.tv-tokyo.co.jp/tbcms/assets/images/icon_sns_twitter.svg | images | 200 | 860 ms | 299 B |
| https://scdn.cxense.com/cx.js 3rd party | javascript | 200 | 852 ms | 37.3 KB |
| https://www.tv-tokyo.co.jp/tbcms/assets/images/icon_sns_line.svg | images | 200 | 845 ms | 945 B |
| https://www.googletagmanager.com/ns.html?id=GTM-ND9WBXK 3rd party | html | 200 | 841 ms | 191 B |
| https://www.tv-tokyo.co.jp/tbcms/css/style.css | css | 200 | 837 ms | 78.4 KB |
| https://www.tv-tokyo.co.jp/tbcms/assets/images/logo.svg | images | 200 | 837 ms | 2.9 KB |
| https://www.tv-tokyo.co.jp/tbcms/assets/images/icon_sns_tiktok--black.svg | images | 200 | 832 ms | 1.7 KB |
| https://www.tv-tokyo.co.jp/favicon.ico | images | 200 | 825 ms | 32.1 KB |
| https://www.tv-tokyo.co.jp/tbcms/javascripts/ad.js | javascript | 200 | 822 ms | 9.8 KB |
| https://www.tv-tokyo.co.jp/tbcms/assets/images/icon_sns_instagram.svg | images | 200 | 815 ms | 1.2 KB |
| https://www.tv-tokyo.co.jp/tbcms/javascripts/banners.js | javascript | 200 | 800 ms | 3.2 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.