www.gnavi.co.jp speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 14:39 UTC. Grade C (79/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 72 ms 10%
- TCP connect 130 ms 19%
- Server wait 487 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
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 689 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 574.4 KB over 15 request(s), which is lean. Javascript files are 70% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
- It runs over HTTP/2, so the assets share a connection instead of opening one each.
- 75% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
- The largest element took 2.51 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
- The main thread was blocked for 485 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. 15 request(s) in total, 574.4 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 689 ms. Of that, 487 ms was the server thinking and 202 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.
Compress text responses
high impact1 text response(s) of 10 KB or more are sent uncompressed, and the document itself is compressed. That is 131.2 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.
Render-blocking resources
high impact3 render-blocking resource(s) in the document head (1 script(s), 2 stylesheet(s)). The page cannot paint until each one arrives.
Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.
Cache static assets
medium impact6 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.
Third-party weight
medium impact8 third-party host(s) serve 431.6 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.
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://b.yjtag.jp/iframe?c=ugpOkqj 3rd party | html | 404 | 1.02 s | 6.7 KB |
| https://questant.jp/q/e.js?q=W7LS7XDM&d=0 3rd party | javascript | 200 | 913 ms | 797 B |
| https://x.gnst.jp/meta-sc_page-js/js/ga_meta_sc_page-1.0.0.js 3rd party | javascript | 200 | 903 ms | 384 B |
| https://www.gnavi.co.jp/favicon.ico | images | 200 | 891 ms | 33.7 KB |
| https://questant.jp/q/e.js?q=9BNW5QVX&d=0 3rd party | javascript | 200 | 816 ms | 797 B |
| https://rimage.gnst.jp/www-home/assets/img/logo.svg?t=20260805100703&q=80 3rd party | images | 200 | 640 ms | 1.9 KB |
| https://www.googleoptimize.com/optimize.js?id=GTM-NFTV9QS 3rd party | javascript | 200 | 635 ms | 113.4 KB |
| https://rimage.gnst.jp/www-home/assets/css/app.css?t=20260805100703&q=80 3rd party | css | 200 | 635 ms | 17.8 KB |
| https://cmhf.gnst.jp/css/yakuhanjp.min.css 3rd party | css | 200 | 623 ms | 364 B |
| https://rimage.gnst.jp/www-home/assets/js/app.bundle.js?t=20260805100703&q=80 3rd party | javascript | 200 | 594 ms | 152.9 KB |
| https://securepubads.g.doubleclick.net/tag/js/gpt.js 3rd party | javascript | 200 | 594 ms | 131.2 KB |
| https://cmhf.gnst.jp/js/gn-footer-v2.8.0.js 3rd party | javascript | 200 | 594 ms | 4.6 KB |
| https://site.gnavi.co.jp/analysis/gtm_nt.js 3rd party | javascript | 200 | 594 ms | 753 B |
| https://site.gnavi.co.jp/analysis/ga_measure.js 3rd party | javascript | 200 | 594 ms | 216 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.
