Separate Slow Font Transfers From Cache Reuse
Admin ·
Repeated font addresses need separate rows when measuring the traffic recorded in a capture. Check which values are present before interpreting the total or changing your CSS.
Check the three requests in Slow transfer
Select Slow transfer sample and Analyze font loading. The summary shows three font entries, two unique addresses, one repeat and 394,240 transfer bytes. The two reading.woff2 lines remain separate.
Choose Duration under Order font requests. display.otf leads at 1,300 ms. The second reading.woff2 line reports zero bytes and 4 ms, with no cache evidence in the supplied note.
Open Web Font Loading Analyzer and load Slow transfer sampleW3C Web Performance Working Group, HTTP Archive historical draft
Read explicit CSS and cache observations
In the same sample, Evidence in the capture lists font-display: block, max-age=0, a FAIL marker and a rendering signal. These are written in the input. The tool uses them to suggest which CSS and request settings to check.
Now choose Retry limit sample and rerun. The report keeps the font address and retry-limit marker with the transfer size and duration unavailable. Use the capture tool to collect the missing evidence before comparing different strategies.
Open Web Font Loading Analyzer and load Slow transfer sampleW3C CSS Fonts, the font display timeline
Use the JSON report beside the original capture
Export a sanitized HAR in the browser network panel. Open the saved file in this tool. Look for actual transfer sizes, decoded content sizes, cache indicators and request timing stages. In HAR, SSL time belongs within connect time when both are present.
Download font-loading-report.json. Keep the original capture for investigation because the report withholds URL credentials, queries and fragments from address fields. Compare page rendering in the browser before attributing invisible text or layout movement to an individual request.
Chrome DevTools network reference, export requests dataW3C Web Performance Working Group, HTTP Archive historical draft
Common questions
How does the analyzer find extensionless font requests?
A recorded Font resource type or font MIME type can identify a request independently of its filename.
Why can a request be visible with an unavailable transfer size?
Some exporters omit the transfer field or use a negative sentinel. The report keeps that value unavailable and reports separately how many entries supplied a byte count.