fontawesome.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:27 UTC. Grade B (80/100), with the screenshots, the timings and the fixes that matter.

https://fontawesome.com/

20 October 2026 at 12:27 UTC · Free test · report pt_feab0f66d859
Grade
B
80/100
Performance85/100
Structure73/100

11 audit(s) passed, 5 need work

First byte (TTFB)180 msmeasured from this server
Fully loaded1.13 sfirst byte + slowest asset
Requests26document + assets
Page weight2.68 MBcompressed transfer
HTML document2.9 KBgzip
ProtocolHTTP/3cloudflare
Third-party451.1 KBother hosts

Where the first byte went

  • DNS lookup 49 ms 27%
  • TCP connect 7 ms 4%
  • Server wait 124 ms 69%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 95% of 4,999 pages tested here180 ms against a median of 449 ms
Page weightheavier than 87% of 4,999 pages tested here2.68 MB against a median of 650.3 KB
Fully loadedfaster than 89% of 4,999 pages tested here1.13 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The server answered in 180 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 2.68 MB over 26 request(s). Javascript files are 97% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.84 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 839 ms, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of fontawesome.com
Mobile 390 × 844 · 27.6 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint1.84 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time839 mslong tasks during load
First contentful paint1.84 sfirst content on screen
Browser page weight6.66 MB105 request(s), scripts included
Largest contentful paint1.84 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time839 ms
Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 7 requests
2.61 MB 97%
Css 1 request
67.3 KB 2%
Images 3 requests
2.0 KB 0%
Other 14 requests
122 B 0%

Transfer size, compressed as sent. 26 request(s) in total, 2.68 MB across all of them.

Top issues

Render-blocking resources

high impact

78 render-blocking resource(s) in the document head (1 script(s), 77 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

high impact

The page transfers 2.68 MB across 26 request(s), with the document itself at 2.9 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Cache static assets

medium impact

1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Third-party weight

medium impact

6 third-party host(s) serve 451.1 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

JavaScript weight

medium impact

2 JavaScript file(s) over 200 KB: app-f0ee081dcde6f82b920ade378def7cec.js (2.01 MB), v3 (252.9 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Waterfall

Slowest requests

JAVASCRIPTm.servedby-buysellads.com/monetization.js
948 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
944 ms
JAVASCRIPTwww.google.com/recaptcha/api.js
931 ms
JAVASCRIPTuse.fortawesome.com/1ce05b4b.js
930 ms
IMAGESfontawesome.com/favicon.ico
930 ms
JAVASCRIPTfontawesome.com/js/app-f0ee081dcde6f82b920ade378def7ce…
895 ms
JAVASCRIPTjs.stripe.com/v3/
888 ms
JAVASCRIPTfontawesome.com/js/settings-18c5c7df667d0f39d5ece79dcc…
888 ms
IMAGESfontawesome.com/images/favicon/icon.svg
888 ms
CSSfontawesome.com/css/app-wa-a6f2fee5074f8963ed852baa830…
887 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://m.servedby-buysellads.com/monetization.js 3rd partyjavascript200948 ms16.6 KB
https://www.googletagmanager.com/gtag/js?id=G-BPMS41FJD2 3rd partyjavascript200944 ms177.0 KB
https://www.google.com/recaptcha/api.js?render=6Lfwy8YZAAAAAOymsOdsZ7xDAG-TFKW_fij1Wnjg 3rd partyjavascript200931 ms639 B
https://use.fortawesome.com/1ce05b4b.js 3rd partyjavascript200930 ms4.0 KB
https://fontawesome.com/favicon.icoimages200930 ms304 B
https://fontawesome.com/js/app-f0ee081dcde6f82b920ade378def7cec.js?vsn=djavascript200895 ms2.01 MB
https://js.stripe.com/v3/ 3rd partyjavascript200888 ms252.9 KB
https://fontawesome.com/js/settings-18c5c7df667d0f39d5ece79dccb01f75.js?vsn=djavascript200888 ms165.5 KB
https://fontawesome.com/images/favicon/icon.svgimages200888 ms340 B
https://fontawesome.com/css/app-wa-a6f2fee5074f8963ed852baa8303bca5.css?vsn=dcss200887 ms67.3 KB
https://fontawesome.com/images/favicon/apple-touch-icon.pngimages200887 ms1.4 KB
https://fontawesome.com/manifest/app.jsonother200887 ms122 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/fontawesome.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/whiteboard-semibold.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/sharp-solid.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/utility-duo-semibold.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/duotone-light.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/jelly-duo-regular.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/mosaic-solid.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/slab-duo-regular.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/regular.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/solid.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/light.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/jelly-fill-regular.css 3rd partyother403887 ms0 B
https://site-assets.fontawesome.com/releases/v7.3.1/css/sharp-regular.css 3rd partyother403887 ms0 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.