How to improve page speed with cache, images and HTTP/3

Page speed for global users is cache, image weight, fonts and handshake. What Cloud CDN changes, and what still belongs in the application.

Get started Performance

Page speed advice often starts at minification. For anyone not in the origin region, it should start at geography. Cache the document, shrink the LCP image, self-host fonts, then talk about JavaScript.

Put HTML on the edge

Anonymous pages should be cacheable at Cloud CDN. Asset-only CDNs leave TTFB on origin. Purge HTML on publish.

Images and fonts

Transform heroes to display size in WebP or AVIF. Host WOFF2 on the same distribution. Those two changes move LCP more often than another gzip pass.

Transport

HTTP/3, HTTP/2, TLS 1.3 and Brotli are on Cloud CDN. They help waterfalls. They do not delete a 2 MB bundle.

Measure far from origin

If your lab is next to the origin, you will ship a slow site for everyone else. 210+ PoPs exist so field data is not a surprise.

Continue on Aptranet

Frequently Asked Questions

Will a CDN make a heavy app fast?

It makes the heavy files arrive faster. It will not make main-thread work cheaper.

Should I cache HTML?

Yes when it is anonymous and you can purge it. That is usually the largest TTFB win.

Is compression enough?

Brotli helps text. Images need format and size changes, not another gzip.