Matheus, we implement this regularly for our clients using a reverse proxy setup we call Hyperspeed. Images are automatically optimized to WEBP’s and delivered from an edge cache. HTML, JS and CSS are optimized and edge cached, it’s fast.
We see about a 20 point improvement in lighthouse scores.
While we generally don’t mess with script placements, adding “defer”, etc., these are all possible in the right circumstances with this kind of setup. So is upgrading jQuery, for example, which we frequently need to do.
Here are the details and enquiry form if you’re interested, but please note a few key things-
Webflow’s recently made some excellent improvements to it asset delivery - edge caching on Cloudflare, compression support for CMS assets, and recently AVIF compression support. From a performance standpoint, those are significant steps, and are where we see most of our performance gain in Hyperspeed. You get that out of the box with Webflow now.
To my knowledge edge caching is not done with HTML, CSS, and JS yet, but that goes more to latency than download time.
Other chances, like deferring scripts can be done but require careful testing to ensure the site isn’t broken as a result, so you can’t blindly enable those. We use Cloudflare as a framework for all of our work so those features are available if you wanted to learn and experiment with them.
Our team is very busy at the moment with a different set of feature builds, more focused on bandwidth conservation, so we’re not doing much specifically on the performance optimization side currently.
There are a number of excellent devs here who know Webflow optimization through and through, and how to implement lighthouse/CWV optimizations on WF. I highly recommend you reach out to @webdev to help you with your site internally and then once that’s done, Hyperspeed can add a bit more performance on top of that by edge caching your HTML / CSS / JS.