Are you at risk of exceeding your bandwidth or traffic limits on your Webflow-hosted site?
Webflow is currently tightening it's restrictions on plan bandwidth and monthly visitor count, and requiring customers to upgrade who regularly exceed their plan limits.
And, that's fair enough.
The problem is that the cost increase between Webflow's Business Plan and Webflow's Enterprise Lite is substantial.
More than 30 times the annual cost.
We've had more than a few businesses come to us in a panic, hoping to find a way to avoid shifting their entire operation to Wordpress, or to avoid rebuilding their entire site on a new CMS. In less than a month.
Fortunately, you may not need to do any of those things. There is a way to keep your site hosted on Webflow, while respecting your plan bandwidth and traffic limits fully.
A popular application of reverse proxies is to optimize images and cache content so that it can be served as quickly and efficiently as possible.
This means far fewer requests to your Webflow hosted site, and far less bandwidth consumed as images are primarily delivered from the proxy cache.
Together, these can ensure that you stay well within your Webflow plan limits.
The exact impact will depend on your traffic levels and the type of data you are serving ( html, images, video, svgs, etc. ), however you can expect a significant improvement.
Not only that, edge-caching makes the site much faster, and image optimization means its lighter and quicker on mobile devices too.
Here's a 7-day report showing hits in our standard cached configuration. This particular client site is a large blog with a significant number of large images and SVGs.
85% of all requests are served by Cloudflare for this client, meaning an 85% reduction in traffic to Webflow's origin servers.
What about data transfer volume?
Over that same period, we're seeing a 91% reduction in bytes transferred from Webflow's origin servers.
We primarily use Cloudflare for our custom reverse proxy builds, due to its blazingly fast edge-cached architecture and high-performance workers.
Sygnal charges a one-time setup fee of $997 usd.
This includes...
** This part requires that you have Cloudflare Pro for at least the first month ( @ $25/mo ), so that we have Cloudflare's caching reports available.
Each Hyperflow build is a custom development project, and we bill it as part of Sygnal's micro-consulting service, with the fixed cost shown above. We'll invoice you in advance of the project and we schedule each project in as soon as the payment is received.
Learn more about Sygnal's micro-consulting here.
For the first month, you'll need Cloudflare Pro ( @ $25/mo ) in order to monitor your cache performance reports and determine where your traffic is at.
After this point you could choose to cancel Cloudflare Pro and give up those reports, or switch to Cloudflare's annual plan ( @$20/mo ).
If your site also happens to be image-heavy, we recommend that you keep Cloudflare Pro long term so that we can take advantage of its image optimization features. We configure this to automatically optimize the size and compression for every image on your site, including CMS-stored images.
Your domain name will remain wherever you've registered it.
Your DNS will need to be migrated to Cloudflare ( we will set that up for you ). This process is simple, and once it's setup you simply change your nameservers at your domain registrar to use Cloudflare's DNS.
Once that's complete, we do all of the programming and configuration needed within your Cloudflare account.
There are no changes to your Webflow hosting or hosting configuration.
Yes. Your site has end-to-end SSL.
No. You can continue publishing and updating your site as normal.
We'll build and test your reverse proxy, and the process of activating it is seamless. However we do prefer to do this step after hours ( as defined by your site's primary audience & geographic location ), just as a part of our sysops best practices.
If you use Google analytics, it's an ideal way to determine your daily and weekly low-traffic periods.
Any time you want to disable the reverse proxy, you can either;
Either approach will return your Webflow site to its original un-proxied configuration.
In an edge cached site, our goal is to cache your Webflow site as much as possible. We can configure your caching depending on your publishing needs.
Typically, we use a 4 hour cache for HTML, which means that if you edit a blog post and republish it, it may take up to 4 hours for those changes to appear for some users. We can vary this to balance your performance goals with your update needs.
This is the one situation we have not fully tested. None of our current clients use Webflow ECommerce. If you use it, let us know.
Contact us to make arrangements as soon as possible, and we'll schedule in your reverse proxy build. It takes less than a week for us to complete setup, but we have a lot of client requests so the timing will depend on our availability.
If you are in an emergency situation, let us known that you need an emergency solution, and we'll see if we can re-prioritize our project commitments. There's a surcharge for this added work of 50%.
Once the invoicing is complete, the process looks like this;
We'll do videos for you to familiarize you with Cloudflare's reports and how to monitor them.
This service is built on Sygnal's Hyperspeed service.
See all of the answers to your questions on our Hyperspeed page.
Do you need this feature on your site?
We love working with great clients, and building great systems. Give us a shout.
Click on any item to view that FAQ.
