This is a problem 
Hello Webflow team,
I think the problem is quite serious, it would be nice if you could give the community a reference on what you are doing to solve the problem, if you are doing it.
It is important for many who are paying attention to SEO aspects to have a clear direction on what to expect from you.
This problem has persisted for years and there are thousands of reports made about this serious problem.
I hope you can understand that many users, like me, have been seriously considering migrating elsewhere for some time because of this problem, and that the only thing that is not driving us to do so is the frustration of having to redo the whole project elsewhere.
Please, give us an answer on this.
Thank you
I agree with everyone’s opinion here. Mobile experience nowadays have a huge impact in the website, and we don’t have much control of how to improve it.
A clear picture of this is one of our websites, this is a snapshot of the mobile version:
And this is the desktop version of the same page:
Basically we get 10x more impressions from the desktop version that we do in the mobile, where if we could improve the mobile page it would allow us to be ranked way better and improve our $$$.
@jfiche I was able to get my mobile CWV’s to “needs improvement” rather than “failing” using a reverse proxy & edge cache.
It doesn’t directly optimize the CSS/JS or improve render blocking, but images are WEBP-optimized and everything delivers much faster.
Not a perfect solution, but it’s a substantial improvement.
Bumping this thread — I’m hoping some progress is being made on this in 2024…
It’s frustrating when I work hard to get 95-100 for accessibility, best practices, and SEO but there’s nothing I can do to improve performance 
My site is spending almost 2 seconds with Google CDN. Can Webflow do something about this please?
@Richard_George - By default there should be no Google CDN use on a project. If you are talking about fonts then localize them. If you are talking about analytics then that’s a choice that Webflow would have no control over.
Yet another bump for this thread. I’m surprised to see how long this has been an issue for with no resolution in sight…
I was able to work around this by setting up CloudFlare Workers and injecting the minified CSS into the HTML response. Not optimal or clean but it worked.
Hi Daniel, I’m working on the same issue for several days now. Any chance you could share the steps you took to get this working along with the pros and cons?
It’s not a trivial thing to do and you need technical background to perform it.
- Set up a Cloud Flare account and set up it’s CDN to serve your web page.
- Set up a CloudFlare KV to store the whole minified CSS/Javascript of your web page.
- Set up a CloudFlare Worker to intercept the generated HTML being returned to the clients.
The worker implementation should:
- Remove the link tag that instructs the page to load the CSS/Javascript from the Webflow servers (these are the annoying aforementioned blocking resources).
- Inject the CSS/Javascript that is stored on the KV store into your webpage as inline script/css
The cons of this are that you need to manually update the KV store values everytime you publish a new version of your webpage, so if you are constantly making changes to it it will introduce a lot of operational overhead. Also if the CSS or Javascript you are injecting is very large, the Speed Insights tool will complain about this, but you will definitely see an improvement on loading times
We ended up moving the site to Wordpress, I find it very unusual that it’s 2024 and the Webflow team has not provided any tools to optimize CSS/Javascript loading
Thank you so much for your detailed response @daniel_amezcua!
I really appreciate your suggestions. However, I’m a bit concerned about the practicality of implementing them in a production environment, particularly because manually updating Cloudflare with every Webflow site upgrade seems quite daunting. Unfortunately, this isn’t feasible for us.
It’s disappointing that in 2024, the Webflow team still hasn’t addressed this issue. If a solution isn’t found soon, I may be forced to consider leaving this platform, as it’s becoming increasingly difficult to meet my clients’ needs.
Once again, thank you for your assistance!
Hello Webflow team,
Yes, I would like to join the previous speakers.
You try to optimize your site, throw out all the unnecessary crap and then go to the SEO and ranking checks and find that you are blocked by the system you are trying to optimize your site with.
A bit questionable, isn’t it?
Then it’s better to do without things like “page templates” in order to open up Webflow to even more user groups. In the end, even these marketers won’t get anything out of it if they want a clean website.
Best regards
Toby
Bump 2025. Now I am just typing to meet the minimum.
Hii @Martin_SEO , It sounds like you’re feeling a bit frustrated with the render-blocking resources issue in your CSS file. As per your question, eliminating render-blocking resources simply means that you need to make sure your CSS and JavaScript files are not preventing the rest of the page from rendering quickly. When these files are large or placed in the head of the document without proper handling, they delay the visible content from loading.
Here are some more additional things you need to consider -
1.Load non-critical CSS asynchronously
One thing you can try is to defer your CSS until after the page content has been rendered. For example , you can load critical styles inline in the and move the rest to be loaded async. Example-
<link rel="stylesheet" href="non-critical.css" media="print" onload="this.media='all'">
2.Minify your CSS and JS
You’ve likely already optimized these files, but check for any large, unused styles or selectors. Webflow’s built-in tools can handle minification but try to manually inspect and remove any unused CSS classes, especially from third-party embeds.Below I am showing you the example to do the same.
JavaScript (Before Minification):
function calculateSum(a, b) {
// This function calculates the sum of two numbers
var sum = a + b;
console.log('Sum:', sum);
return sum;
}
JavaScript(After Minification) :
function calculateSum(a,b){var sum=a+b;console.log('Sum:',sum);return sum}
3.Font Optimization
Fonts played an important role in website load time. So we have to keep them optimized as well. Below are some of the practices to enhance performance:
- Trim Unused Unicode Characters: Use FontForge to remove unnecessary character sets and reduce file size.
- Limit Font Variations: Stick to one or two fonts with minimal weights/styles to reduce load time.
- Use font-display: swap: Ensures text remains visible during font loading, preventing the Flash of Invisible Text (FOIT).
Alternatively, if you feel like the manual optimizations aren’t enough, I’d recommend checking out Website Speedy—a Webflow optimization tool. It automates a lot of the optimizations you’re trying to achieve, like JS/CSS minification, image compression, and font optimization that enhances the performance and boosts the speed.
(Disclaimer : We are the part of the developing team so happy to assist you further )
It’s always so disappointing when the team behind such a big platform like Webflow just outright ignore people. You don’t even bother responding with a comment to show that we’ve been heard. It’s not hard…