Japanese WordPress hosting for pages where the font is the payload.
A Latin webfont is forty kilobytes. A Japanese one covering the same text is several megabytes, because it has to carry thousands of characters.
The typography is the performance budget.
Nothing else on a Japanese page comes close to the weight of the type, and most advice about web fonts was written for alphabets.
Fonts subsetted to the characters used
A full Japanese font carries thousands of glyphs and weighs megabytes. Subsetting to the characters a page actually contains turns the largest asset on the site into one of the smaller ones.
Vertical text and ruby without a rebuild
Japanese layout uses features that reflow differently from Latin text. Pages are cached whole rather than assembled client-side, so the layout does not settle in front of the reader.
An origin on this side of the world
Signed-in pages always reach the origin, and a European one is a fifth of a second away before it starts working. The origin sits in the Asia region instead.
APPI questions answered directly
Japan's regime asks who handles the data and where it goes when it leaves the country. Those answers are given as facts rather than as a region name.
Mobile carriers, not office fibre
A large share of Japanese traffic is on mobile networks where the first byte matters more than raw bandwidth.
Megabytes before a word is read.
Optimise images on a Japanese site and you have addressed the second-largest thing on the page. The font is first, usually by a wide margin.
- Fonts subsetted per page rather than served whole
- Cached HTML so layout does not shift
- Origin placed in the Asia region
- Data handling stated for APPI
Text that appears before the font finishes.
The measure on a Japanese site is when readable type reaches the screen, and that is decided almost entirely by how the font was packaged.
What we change for Japanese sites
One fact dominates: the writing system needs thousands of glyphs, and shipping all of them is the default.
| Setting | What we do | Why |
|---|---|---|
| Font delivery | Subsetted to the characters each page uses | A complete Japanese face carries thousands of glyphs and runs to megabytes, making it larger than every image on the page combined. |
| Font loading | Sequenced so text is readable before the face arrives | A multi-megabyte font blocking first paint leaves a Japanese page blank for exactly as long as the download takes. |
| Origin region | Placed in Asia rather than fronted by an Asian edge | Cached pages are served locally either way, but signed-in and transactional pages always reach the origin wherever it happens to be. |
| Markup caching | Full HTML cached rather than assembled in the browser | Japanese layout features reflow differently from Latin text, so client-side assembly settles visibly in front of the reader. |
| Data handling | Stated for APPI including cross-border movement | Japan's regime asks specifically what happens when data leaves the country, which is a question about facts rather than about a provider's region names. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why is my Japanese site slow when the images are optimised?
Can Japanese fonts be subsetted?
Do I need an origin in Asia if I use a CDN?
What about APPI?
Ship the type, not the whole typeface.
Move the site to an Asia origin - migration is free, fonts reviewed.