Skip Navigation

[Resolved] Eliminate render-blocking resources – Big CSS file being loaded on archive page

This support ticket is created 2 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 1 reply, has 2 voices.

Last updated by Minesh 2 years, 9 months ago.

Assisted by: Minesh.

Author
Posts
#2328285

I'm checking in to my sites archive pages that I'm building, so far so good with the help I'm getting from Toolset support and everything.

I checked on

hidden link

And noticed that for mobile, it doesn't matter which archive page, but there is a big "eliminate render blocking resources" issue going on.

Doesn't seem to matter which archive page, but it looks like it's loading some massive CSS sheet which is taking 2.4 seconds to load on mobile.

Desktop doesnt seem to be as dramatically affected, 0.5 second delay.

The suggestion is to,

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

Is there a way to trim down this CSS file that's loading.

Or somehow deliver all the JS and CSS in line on the page and eliminate it altogether?

I wish mobile was such a BIG deal, but now that Google does its website crawling EXCLUSIVELY on mobile, it kind of is a big deal...

This is even while using WP Rocket to try and speed things up.

Any comments or thoughts are greatly appreciated and thank you!

G

#2328427

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

This is more related to performance issue and I suggest you should check with the performance or optimization plugin you are using and check with their support.

Here are few articles:
- hidden link
- hidden link
- hidden link