Features

Why Aurora Loads Font Awesome Locally (No CDN)

By Daniel Ekay May 18, 2026 2 min read
Docs Features Why Aurora Loads Font Awesome Locally (No CDN)
Share:
Last updated:

Aurora includes Font Awesome as part of the theme and serves it directly from your server. No request is made to a third-party CDN. This is a deliberate performance and privacy decision.


Why It Matters

When a theme loads Font Awesome from a CDN, every page load triggers an external DNS lookup, TCP connection, and file request to a server you do not control. This adds latency — typically 50–200ms depending on the visitor’s location — before any icon can render.

Serving Font Awesome locally eliminates that external request entirely. The files are on your server alongside everything else, loaded in the same connection that delivers your page.

There is also a privacy benefit: no visitor data is sent to a third-party CDN. GDPR-conscious sites often need this.


What Aurora Loads

Aurora loads Font Awesome 7.2.0 as four separate stylesheets — the base, solid icons, brand icons, and regular icons — each served from /wp-content/themes/aurora-pro/assets/fonts/font-awesome/css/. The stylesheets are enqueued on every page alongside Aurora’s other styles.


Impact on PageSpeed

Removing the CDN request contributes directly to faster Largest Contentful Paint (LCP) and eliminates a render-blocking dependency from an external origin. It is one of several performance decisions Aurora makes at the theme level. See Aurora PageSpeed and Performance for the full picture.

Make your blog stand out

Enjoy the ease and flexibility of Aurora. Create stunning blog designs your readers will love, with live preview editing and effortless template mixing and matching enabled.

Get Aurora today for just $39

Get Aurora