I’m not sure if this is the right place for this?
Currently, Shopify hosts and serves fonts via fonts.shopifycdn.com using the font_url and font_face Liquid filters. However, there is no option to load only a specific Unicode subset of a font.
For example, the font Mochiy Pop P One (a Japanese font available in Shopify’s font library) weighs nearly 2 MB as a .woff2 file because it includes thousands of Japanese characters (Kanji, Hiragana, Katakana) — even when the store only uses Latin characters.
Google Fonts solves this elegantly by serving fonts with unicode-range descriptors, splitting the font into multiple smaller files and only loading the subsets the browser actually needs.
Feature request: Please add support for Unicode subset loading for Shopify-hosted fonts — either by:
-
Automatically splitting font files by script (Latin, Japanese, Cyrillic, etc.) and using
unicode-rangein the generated@font-facedeclarations, or -
Allowing merchants to specify which subsets to load via the
font_faceLiquid filter (e.g.font_face: subset: 'latin')
This would significantly improve Largest Contentful Paint (LCP) and Core Web Vitals scores for stores using non-Latin fonts.