Reverse Proxy w/ Cloudflare

Maximizing Site Performance

Overview
Introduction to Reverse Proxies + Webflow
001
What Problems are we Solving?
What Problems are we Solving here?
101
The SSL Problem
102
Maximizing Site Performance
103
Staying Within Webflow's Hosting Plan Traffic Limits
104
Setup & Configurations
Proxy Configuration Approaches
201
Reverse-Proxy DNS Config
202
High Performance Configs
Proxying for Performance
300
Caching Strategy
301
Level 1 - Basic Caching
302
Level 2 - Caching + Optimization
303
Level 3 - Extended Caching + Optimization
304
Level 4 - Advanced Caching + Optimization
306
Administration
How to Determine if an Item is Cached
801
How to Remove a Cached Item
803
Emergency Revert
804
Resources
More Resources
901
No items found.
Published
October 28, 2023
Updated
October 28, 2023
in lightbox

Problem: Performance, Core Web Vitals & SEO

Problem: Traffic, and Webflow Plan Limits

Currently, Webflow allows;

300 GB of data egress per

Problem: Separated Sites

Problem: Webflow Paths

Optimizing Images

Automatically convert your images to WebP's and size them efficiently.

Why can't I just use Webflow's WebP conversion tool?

It only handles assets, and nothing uploaded into the CMS

30-Oct-2023 - the WebP conversion tool only works for the images in the Assets panel and for these file formats JPEG, JPG, PNG, and WebP.

It's also not "smart" about when to convert files and when not to.

It also makes no backups of your original files

It breaks

Webflow Support 30-Oct-2023 - There is currently a known issue where images inside a Lightbox converted to webp may not work as expected.

How Much Performance?

Hits

Here is a snapshot of the first 24 hours after a site was migrated to our Level 2 proxy-cache configuration.

Orange indicates hits that were handled by Cloudflare's cache, Blue indicates ones that were handled by Webflow.

Notice the blue spike just after we switched this on, as Cloudflare's cache was empty. Very quickly Cloudflare picked up the popular requested documents and began serving it directly.

In the first 24 hours, traffic to Webflow was reduced by over 99%.

In the first 24 hours, traffic to Webflow was reduced by over 99%.

Bandwidth ( bytes )

Here is a snapshot of the first 24 hours after a site was migrated to our Level 2 proxy-cache configuration.

Orange indicates hits that were handled by Cloudflare's cache, Blue indicates ones that were handled by Webflow.

Notice the spike just after we switched this on, as Cloudflare's cache was empty. Very quickly that leveled out and the vast majority of the traffic is now handled by the cache.

In the first 24 hours, the bytes served by Webflow was reduced by more than 99.8%.

In the first 24 hours, the bytes served by Webflow was reduced by more than 99.8%.

Lighthouse

Core Web Vitals

FAQs

Answers to frequently asked questions.

Videos
No items found.
Table of Contents
Comments
Did we just make your life better?
Passion drives our long hours and late nights supporting the Webflow community. Click the button to show your love.