Eliminate render-blocking resources - Page Speed Mobile

Hi! I have a problem with my “Page Speed”. I don’t understand what I should do with this information…

" Eliminate render-blocking resources

2.15 s

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL Transfer Size Potential Savings

(uploads-ssl.webflow.com)|18.9 KiB|930 ms|"

I hope someone knows this :slight_smile:

Sending my regards from Sweden

Here is my site Read-Only: LINK
(how to share your site Read-Only link)

1 Like

Not everything recommended you can address. This is one of those.

it’s true webflow does not allow us to address this but you guys could address it on your end. Is this something being looked into? I also get less than ideal mobile results on page speed and have no ability to fix the issues in Webflow.

2.2 seconds is no joke

bump @Waldo is there anything to add on this or is it being looked into do you know? :slight_smile:

1 Like

I think Webflow allows to defer and async, and thus solve the problem in the topic, but only after exporting code out of Webflow.

I think it should be possible to deal with it with an additional tool that analyzes the CSS file. Friend suggested to me, that he had once a tool which suggested which CSS classes or selectors should be looked into. Then, it is the matter of logging into Styles Manager in Webflow and checking them manually. Do you perhaps know the name of this tool? I’ve been looking for it to no avail. Have seen it a few years ago.

Any updates on this? Webflow team?

@webdev currently with recent Google Page Speed updates it’s becoming a lot more of an issue, because css request is blocking.

I realize obvious things are done - minify, serve from CDN, one file, etc…

You could go much further:

Then minimum amount of CSS would load and that would mean less time loading and less time processing rules on slower mobiles on slower networks

I understand you keep it render blocking to avoid a flash of unstyled content and it’s great. However, all modern frameworks, like Gatsby, next, anything with webpack, already produce optimized css for each page that dynamically loads.


These are the suggested fixes for my mobile site - 4 out of 5 items can only be addressed by webflow :disappointed_relieved: My SEO is really suffering so any advice would be much appreciated.

Also keen to understand how to fix this issue - or how Webflow are thinking about addressing it.

I come from JAMStack, we moved from there to Webflow because of scaleability issues with designers…it’s great to not have to deal with backend…but not seeing them implement best practices like purging unused CSS (stuff Bootstrap and Tailwind does) is sad.

For this @Supersonic I did an interesting post. If anybody is interested in speeding up the rendering-blocking resources and more look into Pagespeed Improve Webflow