The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Removing a Chinese web font can cut a large amount of page transfer when the design does not need that custom typeface. In this case, “about 1 MB per page” is an author-reported result, not a verified benchmark: the available sources explain why a large saving is plausible but do not establish how it was measured or whether it applied consistently.
Why a Chinese web font can add so much weight
A web font file stores the outlines and related data needed to render its characters. Chinese, Japanese and other CJK typefaces may cover thousands of glyphs; file size also depends on the complexity of those glyph outlines. A page that displays only a small fraction of that inventory can still prompt a browser to download a much broader font file.
As an Amazon Associate I earn from qualifying purchases.
As Google web.dev author Ilya Grigorik explains, “A ‘full’ WebFont that includes all stylistic variants, which you may not need, plus all the glyphs, which may go unused, can easily result in a multi-megabyte download.” Google web.dev’s font-loading guidance discusses why full fonts and unnecessary variants can be costly.
The headline’s 1 MB figure should be read as a report about one site, not a typical or guaranteed saving. The available sources do not verify the site’s pages, test conditions, or measurement boundary. “One megabyte” could mean the font transfer alone or a change in total page bytes; compression, browser cache and whether the observation was an average also affect what the number means.
#1 Best Overall
Decide whether the custom Chinese typeface is needed
Remove it if the design can use a fallback
If the site does not rely on a particular Chinese typeface for branding, legibility or visual consistency, removing the custom font is the most direct way to prevent its download. Check the actual pages after removal: the operating system or browser will render Chinese characters using an available fallback font, and the resulting appearance can differ across devices.
Keep it, but deliver less of it, if the typography matters
If the typeface is an important part of the design, optimize what the browser receives rather than assuming the only choice is a full font or no font. Identify the characters, language coverage, styles and weights the site actually needs. A subset can omit unused glyphs, while Unicode-range declarations can let the browser request relevant font resources for the text it encounters.
Subset reuse matters. If each page has a different overlapping subset, visitors may download duplicate glyph data as they move around the site. Reusable subsets or script-based ranges are generally a better fit for sites with changing or multilingual content than a separate hand-built font for every page. Google web.dev explains font subsetting, Unicode ranges and reuse.
Choose a delivery method that fits the text
Use a character-specific request only for stable text
When using Google Fonts, the API’s text= parameter can request a font for specified characters, including UTF-8 characters. Google says this can reduce font-file size by up to 90% in some cases; that is a stated potential for this technique, not a promised saving for every language, page or site. It is most suitable when the required character set is known and does not change unexpectedly. See Google’s Google Fonts API guide.
Rank #3
Use language or Unicode subsets for broader content
For general multilingual sites, content may include names, user-generated text or characters not known in advance. In that situation, evaluate the font’s available subsets and Unicode ranges, and confirm that the selected resources cover the content the site needs. A narrow character request that omits a required glyph can make that character fall back to another font.
Request only the styles and weights the design uses
Do not load italic styles or multiple font weights unless the page uses them. Google Fonts’ CSS API supports requesting specific styles and weights, and its documentation describes the font-display option. Google’s CSS API documentation covers those request controls. For modern browsers, web.dev recommends WOFF2 where supported; consult its guidance on reducing web font size.
Make font loading work without delaying or hiding text
Smaller font files do not automatically mean an unchanged reading experience. A browser may show fallback text while a web font loads, swap to the custom face later, or handle text visibility according to the chosen font-display value. Preloading can help a font needed for initial rendering, but preloading every weight or subset can waste bandwidth and compete with more important page resources.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Set an intentional
font-displayvalue and check how text looks before and after the font loads. - Preload only a font that is genuinely critical to the first screen; avoid preloading every subset or variant.
- Test fallback rendering for Chinese text on the devices and browsers your audience uses.
Google web.dev’s font loading and rendering guidance explains the trade-offs between font delivery, preload and display behavior. Its typography guide also covers loading and visual fallback considerations.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify the saving on your own pages
- Measure representative pages with a cold cache and a warm cache, and record font transfer bytes separately from total page transfer. State which condition the result describes.
- Compare the full font, the proposed subsets and the no-custom-font version. Use the same pages, browser and network conditions so the comparison is meaningful.
- Check the page’s actual Chinese characters against the subset. Look for missing glyphs, unexpected fallback fonts and visual changes as fonts load.
- Review every weight and style requested by the CSS, plus any preload hints. Remove requests that the page does not need.
- Repeat the checks across pages with different content. Confirm that shared subsets are reused rather than redownloaded as visitors navigate.
This separates a real font-payload reduction from other changes in page weight and shows whether the optimized version still renders the text correctly.
Quick Recap
When to remove the font—and when to subset it
| Choice | Best fit | Main trade-off |
|---|---|---|
| Remove the custom font | The design can accept system or browser fallback typography. | Chinese text may look different across operating systems and devices. |
| Subset the font or use Unicode ranges | The custom typeface matters and the site’s required glyph coverage can be identified or divided into reusable ranges. | Incomplete coverage can trigger fallback; poorly designed page-specific subsets can duplicate downloads. |
Use Google Fonts text= |
The characters needed for the request are known and stable. | Changing or unanticipated text may need glyphs the request did not include; the potential size reduction varies. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
