Chinese-language pages on a bilingual website often load more slowly than their English counterparts on the exact same site. The usual cause is not the design or the server — it is the font. A Chinese web font has to cover thousands more characters than a Latin font, so the file a browser must download before it can draw any Chinese text is often far larger. The fix does not require a redesign: serving only the characters a page actually needs, or skipping the downloaded font for Chinese body text entirely, closes most of the gap.
Why Does the Chinese Version of My Site Feel Slower?
English text only ever needs the roughly 100 characters of the Latin alphabet, digits and punctuation that make up a typeface. Chinese text draws from thousands of commonly used characters. According to Google's web.dev developer documentation, a CJK (Chinese/Japanese/Korean) font covers roughly 15 to 20 times as many characters as a Latin font — which is why a full Chinese web font file is routinely many times larger than the English typeface sitting next to it on the same page. Visitors on a slower mobile connection feel that extra weight as a longer wait before any Chinese text appears, even though the English version of the same page loads normally.
Is This Actually Worth Fixing for a Small Business Site?
Yes, for two reasons. First, how fast your main content appears — Largest Contentful Paint — is one of Google's Core Web Vitals and affects both user experience and search ranking. A slow-loading Chinese homepage does not just frustrate a visitor; it can rank and convert worse than the English version of the same business. Second, this problem is easy to miss: most site owners test their English pages, see normal load times, and never separately test the Chinese pages where the heavy font is actually doing the work. If nobody has opened the Chinese homepage in a browser's network tab, the slowdown is invisible until a customer feels it.
What's the Simplest Fix — Skip the Downloaded Font for Chinese Text?
Every major operating system already ships a high-quality Chinese typeface: PingFang SC/TC on Apple devices, Microsoft YaHei on Windows, and Noto Sans CJK on Android and ChromeOS. A font stack that lists these system fonts before any custom web font means the browser renders Chinese text immediately, using a font that is already installed — zero bytes downloaded. For most business sites, this single change removes the Chinese-font weight problem entirely, with no visible design change to most readers:
font-family: "PingFang SC", "Microsoft YaHei", "Noto Sans CJK SC", sans-serif;
When a Custom Chinese Web Font Is Worth It, How Do You Keep It Small?
Some brands do want a specific Chinese typeface for headlines or a logo mark. In that case, the goal is to download only the characters the page actually uses, not the full character set. Google has offered a built-in way to do this since 2011: appending a text= parameter to a Google Fonts request tells the API to return only the specific characters named in the request instead of the entire font file, which works for CJK fonts as well as Latin ones. Combined with the CSS unicode-range feature — which splits a font into character-range "slices" so the browser only fetches the slice it needs — Google's own web.dev documentation states this approach can cut font file transfer by about 90% compared with downloading the full font. Font vendors have also started shipping variable CJK font formats that pack several weights into one file instead of one download per weight — a newer option worth asking a type foundry about, though actual savings vary by vendor and typeface, so get the specific number for your chosen font rather than assuming a fixed percentage.
Checklist: Test Your Bilingual Site's Font Loading in 10 Minutes
- Open your Chinese homepage (not the English one) in Chrome DevTools, go to the Network tab, and filter by "Font."
- Note the total kilobytes transferred for fonts. Do the same on the English homepage and compare — a Chinese page pulling several times more font weight than English is the pattern this article describes.
- Check whether your site currently downloads a custom Chinese web font at all, or whether it is already falling back to a system font.
- If a custom Chinese font is loading, confirm whether it is subsetted (only the characters used) or the full character set.
- Confirm your CSS uses
font-display: swapso visible text, even in a fallback font, never waits invisibly behind a font download. - If headline or logo text is the only place a custom Chinese font is really needed, consider restricting the custom font to just those elements and using a system-font stack for Chinese body text.
FAQ
Will switching to a system font change how my Chinese pages look?
Slightly, but usually not in a way visitors notice. PingFang SC, Microsoft YaHei, and Noto Sans CJK are all designed as clean, highly legible Chinese typefaces, which is why operating systems ship them as the default. Most businesses only need a distinct custom Chinese font for a logo or a few headlines, not for every paragraph of body text.
Does this also help my English pages?
The subsetting and unicode-range techniques apply to any web font, Latin included, but the size gap this article addresses is specific to CJK fonts. If your English pages already load quickly, the main benefit here is bringing the Chinese pages up to the same standard — not a redesign of the English side.
Do I need to rebuild my whole website to fix this?
No. This is a font-loading and CSS change, not a redesign. On most sites it is a single file or a few lines of CSS, and it does not touch layout, color, or content.
How We Approach It
When we build a bilingual site, we test font loading on the Chinese pages separately from the English pages, not as an afterthought — because the two language versions genuinely load differently even on identical layouts. We default to system-font stacks for Chinese body text and reserve custom, subsetted web fonts for the places a brand actually needs them.
See how we build bilingual sites on our web design page, or request a free check of your site's font loading.
Sources
- Google web.dev: An API for fast, beautiful web fonts — CJK character-count comparison and unicode-range transfer-reduction figures
- Google Developers Blog: Streamline your web font requests — introducing "text=" — dynamic font subsetting parameter