The service worker of my website is caching several contents to speed up response to the users. Google fonts are also cached.
Because those fonts come back as opaque http responses from Google, they take a lot of space in the cache and can produce even other problems when using a cache-first strategy.
In order to avoid leakage of cross-domain information, there's significant padding added to the size of an opaque response used for calculating storage quota limits (i.e. whether a QuotaExceeded exception is thrown) and reported by the navigator.storage API.
The details of this padding vary from browser to browser, but for Google Chrome, this means that the minimum size that any single cached opaque response contributes to the overall storage usage is approximately 7 megabytes.
Self-hosting Google fonts moves away their opaqueness and makes the network responses being default responses. This in return makes the cache entries for those items as small as they should be. A 7KB response is 7KB again, and not 7MB!
The Google Webfonts Helper helped me a lot to achieve this.