Built-In Font Optimization: Improve Angular Performance & Core Web Vitals

まず、ビルド時のフォント処理に関係する @angular/core と @angular/cli の領域を確認し、提案されている動作を Next.js next/font と比較してください。実装前に、サポートするフォント識別子、ビルド時のダウンロードとセルフホスティングのフロー、および preconnect、preload、size-adjust の動作を定義してください。Google Fonts で機能が動作し、提示された読み込みとレイアウトシフトの目標が改善されれば完了です。

Which @angular/* package(s) are relevant/related to the feature request?

@angular/core and @angular/cli

Problems :

• Using custom fonts from Google Fonts can significantly impact FCP, LCP and initial load performance in Angular applications.

• Downloading fonts from Google servers adds extra HTTP requests and latency, slowing down initial paint times.

• The font swapping has the potential to cause layout shifts and so impact Cumulative Layout Shift (CLS).

Proposed Solution :

• Introduce a built-in mechanism in Angular to automatically downloads fonts specified by their Google Fonts names (or similar identifiers) during the build process and self-host fonts within the application, eliminating the need for external font services like Google Fonts.

• Utilize preconnect, preload, and size-adjust for optimal performance and seamless font rendering.

Benefits :

• Improved Performance: Reduces reliance on external requests, minimizes layout shifts (thanks to the underlying CSS size-adjust) , and enables efficient caching.

• Improved FCP and LCP: Optimized fonts and proactive loading strategies contribute to significantly faster loading times and smoother user experiences.

• Enhanced SEO: Better Core Web Vitals can lead to higher search engine ranking and increased website traffic.

• Enhanced Security: Minimizes exposure to external vulnerabilities and provides more control over font sources.

• Developer Experience: Built-in font optimization in Angular improves developer experience.

Alternatives considered

Anyone interested is welcome to comment on what the proposed syntax and feature set will be.

Inspired by next.js automatic font self-hosting library ( next/font )