Files
jobtrackingapp/docs/performance/font-startup/QUALIFICATION.md
T

3.0 KiB

PERF-16: remove unused font startup requests

Baseline b1e79a56, branch codex/perf-font-startup, E:/Storage/Projects/Active/temp docs/jobjakt-local-build/next-security-patch. Source ade8b08. Scope: three font link elements in root layout only. No dependency/file deletion, replacement font, CSS/theme/renderer redesign or new external service.

Repository source inventory found Archivo only in the root stylesheet URL, with no application font consumer. Current theme uses Trebuchet MS/system fonts; code/native controls retain their established stacks. A controlled built-app probe observed Trebuchet/system and Arial, never Archivo, across390/1440 widths, EN/NB, light/dark (eight states). All API responses were synthetic, external stylesheet intercepted with inert CSS; no request was sent to Google.

Removed the unused Archivo stylesheet and its Google API/static preconnect hints. Next also stops emitting its automatic stylesheet preload. Paired after-build probe PASSED eight states: one external stylesheet request per page becomes zero (eight to zero in the sample); four font-related head links become zero. Computed font-family sets, heading text/dimensions and overflow results are identical for every pair. This establishes request elimination and retained sampled typography, not real-network latency, saved live font bytes, European TTFB or a whole-product performance result. Initial probe incorrectly expected three generated links; corrected after inspecting Next's generated fourth preload, before changing application source.

PASSED: ordinary Next16.4.6 build/TypeScript/static export (also includes prior interview-add source), scoped layout lint, source diff check, paired browser assertions. Existing tracking pilot PASSED two EN/light journeys at320/1440, eight axe scans/captures, fixture previews/writes only. This is a canary, not a replacement for the preceding36/144 matrix or whole-application regression. Prior full Jest's two stale-label defects and focused correction remain recorded separately. No new backend/full-Jest/native-device/AT/provider/model/PDF/security/recovery/release qualification.

Earlier framework qualification described blocked Google Fonts as potential intended-font substitution. Current computed-font/source evidence narrows that interpretation: Archivo was unused, so blocking it did not change the observed application typography. Intended visual acceptance against A3 and native font availability still need their independent review. Physical document/PDF font rendering is untouched.

Evidence: source and native receipts, paired probe source archived as text and assert-bearing before/after/comparison outputs. No production requests or deployment. Rollback is restoring these three layout links in a dedicated revert and rebuilding; existing theme/bootstrap/auth order remains unchanged. PERF-16 remains PARTIAL for other startup/loading/performance/device qualification, and final A3/security/release gates remain open.