What the 105 .jp sites in this index look like
.jp is Japan's country-code top-level domain, administered by JPRS. Companies commonly register under co.jp, a second-level label restricted to registered Japanese businesses, which is why so many of the names below carry it. The index holds 105 .jp sites, 2% of the 5,294 measured. On every load measure they are the heaviest of the nine TLD groups here, and on both consent-window measures they rank last of the nine.
The heaviest median page of the nine TLDs
The median .jp site contacted 10 companies over 58 requests, with 3 of those companies classified as tracking. All three figures are the highest of the nine top-level domains measured in this index.
The sample shows where that weight comes from. navitime.co.jp, a route-planning service, contacted 36 companies. tenki.jp, a weather site, contacted 25. hotpepper.jp, a restaurant directory, contacted 23. itmedia.co.jp contacted 14. Those are portal-shaped businesses — directories, listings, forecasts — funded by advertising and running the vendor stack that goes with it. Set against them, rakuten.co.jp contacted 1 company and mbga.jp contacted 1.
And the slowest start
The median .jp site waited 1,755 ms before its first contact with a third party. That is the highest median of the nine TLD groups here — nearly two seconds of page life before anything external is fetched. The fastest single first contact recorded on a .jp site was 67 ms.
The individual pages vary enormously. weathernews.jp made first contact at 111 ms and tenki.jp at 463 ms, while ameba.jp waited 5,960 ms, hotpepper.jp 3,821 ms, dmm.co.jp 3,561 ms, mbga.jp 2,812 ms and rakuten.co.jp 2,621 ms. A late first contact is what you get when a page renders from its own server first and loads its tags afterwards — on scroll, on interaction, or simply lower down the queue. The crawl records the timing and not the reason for it.
Consent banners are uncommon here
24 of the 105 .jp sites carried a consent tool the crawl could detect. An IAB TCF banner was seen on 23 of them and OneTrust on 1.
That changes what the early-contact window means on this page. On the other 81 sites there was no banner to answer, so the window is simply the opening moments of the page rather than a period during which a question was pending.
Last of nine on early contact
64 of the 105 sites, 61%, had a company contacted inside the early window. That ranks ninth of the nine TLDs measured. The median number of companies contacted before the window closed was 2, which also ranks ninth of nine — lower than any other TLD group measured.
Six of the twelve sampled sites — rakuten.co.jp, ameba.jp, dmm.co.jp, hotpepper.jp, suumo.jp and mbga.jp — recorded no company at all inside that window, despite hotpepper.jp going on to contact 23 companies in total. On the median .jp site, 6 companies arrived after the window had closed. So the weight is real and the early contact is not: these pages load a great deal, and they load it late.
The sites themselves
The .jp sample spans retail (amazon.co.jp, rakuten.co.jp), blogging (ameblo.jp, ameba.jp), entertainment and gaming (dmm.co.jp, mbga.jp), technology news (itmedia.co.jp), property and local search (suumo.jp, hotpepper.jp, navitime.co.jp) and two separate weather services (weathernews.jp, tenki.jp).
amazon.co.jp is the one page in the sample that behaves like the western commercial average: 4 companies, all 4 inside the early window, first contact at 503 ms. The rest of the list is slower, later and heavier by the end.
| Site | Companies | Before consent | First contact |
|---|---|---|---|
| amazon.co.jp | 4 | 4 | 503 ms |
| rakuten.co.jp | 1 | 0 | 2621 ms |
| ameblo.jp | 3 | 2 | 1534 ms |
| ameba.jp | 5 | 0 | 5960 ms |
| dmm.co.jp | 6 | 0 | 3561 ms |
| itmedia.co.jp | 14 | 3 | 1272 ms |
| hotpepper.jp | 23 | 0 | 3821 ms |
| suumo.jp | 10 | 0 | 2162 ms |
| weathernews.jp | 6 | 6 | 111 ms |
| tenki.jp | 25 | 5 | 463 ms |
| navitime.co.jp | 36 | 15 | 978 ms |
| mbga.jp | 1 | 0 | 2812 ms |
| Tool | Sites |
|---|---|
| IAB TCF consent tool | 23 |
| OneTrust | 1 |
Questions
How many .jp sites are in this index?
105, which is 2% of the 5,294 sites measured and fifth of the nine top-level domains covered here by site count.
Why is the third-party load on .jp sites higher than on other TLDs here?
The measurement records the load, not the reason. What the sample shows is a set of portal-style businesses — directories, listings and weather services — where single pages contacted 23, 25 and 36 companies, pulling the median for the group up to 10.
Do .jp sites show consent banners?
24 of the 105 did. An IAB TCF banner was seen on 23 of those and OneTrust on 1. On the remaining 81 there was nothing for a visitor to answer.
What does a median first contact of 1,755 ms tell you?
That the typical .jp page in this index renders for a while before it reaches out to anyone. It is the highest median of the nine TLD groups measured, and it is why so few of these sites register any contact inside the early window.