Are you at risk of exceeding your bandwidth or traffic limits on your Webflow-hosted site?
Webflow is currently tightening its 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.
If your business uses Webflow regularly and can benefit from other Enterprise Plan features, we highly recommend that you consider simply upgrading. While it's a substantial investment, Enterprise has a huge range of features that your team may significantly benefit from.
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.
This service is built on Sygnal's Hyperspeed service.
See all of the answers to your questions on our Hyperspeed page.
We're pretty quick, a typical full build and migration typically takes about 2 to 3 weeks depending on how quickly the DNS migration can occur.
Emergency expedited builds are possible if you're in an emergency situation. There is an added fee of 50% of the total project cost. In most cases this is not necessary, and we recommend planning ahead anyway, so that there is time to fully optimize your site's caching and delivery.
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.
