papy.co.jp speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 15:40 UTC. Grade B (81/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 98 ms 14%
- TCP connect 191 ms 27%
- Server wait 406 ms 58%
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 695 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 842.2 KB over 18 request(s). Images files are 99% of it, so resize and recompress the largest images before anything else.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- 99% 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 960 ms, inside the 2.5 s Google calls good.
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. 18 request(s) in total, 842.2 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 695 ms. Of that, 406 ms was the server thinking and 289 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.
Image delivery and format
high impact1 image(s) over 200 KB and 3 large image(s) still served as JPEG or PNG.
Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.
Third-party weight
medium impact2 third-party host(s) serve 833.1 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.
Mobile viewport
medium impactNo 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 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://img.papy.co.jp/lc/corp_site/img/top/main_top_sp.jpg 3rd party | images | 200 | 1.14 s | 38.4 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/Service_original_top.png 3rd party | images | 200 | 1.12 s | 16.9 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/recruit_top.jpg 3rd party | images | 200 | 1.12 s | 157.5 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/main_top_sp2.jpg 3rd party | images | 200 | 1.12 s | 155.2 KB |
| https://www.googletagmanager.com/ns.html?id=GTM-W32748T7 3rd party | html | 200 | 888 ms | 92 B |
| https://img.papy.co.jp/lc/corp_site/img/top/Service_overseas_top.png 3rd party | images | 200 | 862 ms | 36.0 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/for_publisher_top.png 3rd party | images | 200 | 847 ms | 46.9 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/home.svg 3rd party | images | 200 | 836 ms | 218 B |
| https://img.papy.co.jp/lc/corp_site/img/top/Service_Renta_top.png 3rd party | images | 200 | 804 ms | 55.1 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/header_top_log.png 3rd party | images | 200 | 792 ms | 6.8 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/main_top.jpg 3rd party | images | 200 | 790 ms | 55.2 KB |
| https://img.papy.co.jp/lc/corp_site/img/icon/link_glay.svg 3rd party | images | 200 | 788 ms | 232 B |
| https://img.papy.co.jp/lc/corp_site/pub/css/company_all_1.css 3rd party | css | 200 | 785 ms | 2.3 KB |
| https://img.papy.co.jp/lc/corp_site/img/icon/papyless.png 3rd party | images | 200 | 770 ms | 1.6 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/main_top2.jpg 3rd party | images | 200 | 765 ms | 255.3 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/icon_x.png 3rd party | images | 200 | 762 ms | 4.3 KB |
| https://img.papy.co.jp/lc/corp_site/img/top/Facebook.png 3rd party | images | 200 | 761 ms | 991 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.