Can’t eliminate render-blocking resources.

  • Resolved boppar

    (@boppar)


    3 years, 11 months ago

    I’m rebuilding my site with a minimum of plugins. One of the few plugins I chose to use is your excellent plugin. Site: https://ibb.co/wMMgTqM

    On Pagespeedinsights I got warnings on Eliminate render-blocking resources (see below). I’ve read the forum and tried some suggestions as enabling Load CSS Asynchronously. Unfortunately without success.

    Do you have any suggestions how to solve the problem with eliminating render-blocking resources?

    MOBILE

    …build/style.css?ver=4.4.3
17,7 KiB
300 ms
…base/gutenberg-blocks.css?ver=3.5.1
3,7 KiB
150 ms
…storefront/style.css?ver=3.5.1
8,4 KiB
150 ms
…base/icons.css?ver=3.5.1)
14,8 KiB
150 ms
/css?family=…(fonts.googleapis.com)
1,6 KiB
780 ms
…jquery/jquery.min.js?ver=3.5.1
30,1 KiB
450 ms

    DESKTOP

    …v14/6xK3dSBYK….woff2(fonts.gstatic.com)
10 ms
…v14/6xKydSBYK….woff2(fonts.gstatic.com)
10 ms
…v14/6xKydSBYK….woff2(fonts.gstatic.com)
0 ms
…v14/6xKydSBYK….woff2(fonts.gstatic.com)
10 ms
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    please provide the report number , you can get it in toolbox -> report -> click “send to LiteSpeed”

    Best regards,

    Thread Starter boppar

    (@boppar)

    Hi @qtwrk

    Done. Report number: ELWWARZQ

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    for CSS you can try enable load async css , for JS you can try enable defer JS but usually I’d suggest not to defer jquery

    for fonts , you can try enable load async google font

    please do remember purge all after you made any change.

    Best regards,

    Thread Starter boppar

    (@boppar)

    Hi @qtwrk
    I did what you say, results below.

    Pagespeed, values: Points, First Contentful Paint, Speed Index, Largest Contentful Paint, Time to Interactive, Total Blocking Time, Cumulative Layout Shift

    * Before making any changes:
    Pagespeed, mobile: 75, 3,2s 3,2s 4,8 3,9 10ms 0,111
    Pagespeed, desktop: 92, 0,8s 0,8s 1,3s 0,8s 0ms 0,397

    * Enabling load async css:
    Pagespeed, mobile: 78, 2,8s 3,9s 4,3 4,0 10ms 0,111
    Pagespeed, desktop: 91, 0,8s 1,1s 1,4s 0,8s 0ms 0,409
    Conclusion: Made almost no difference.

    * Enabling defer JS:
    Pagespeed, mobile: 74, 3,1s 4,2s 4,9 3,2 0ms 0,111
    Pagespeed, desktop: 91, 0,8s 1,1s 1,3s 0,8s 0ms 0,407
    Conclusion: Made almost no difference.

    * Enabling load async google font:
    Pagespeed, mobile: 66, 4,1s 4,1s 5,6 4,1 0ms 0,111
    Pagespeed, desktop: 94, 1,0s 1,0s 1,3s 1,0s 0ms 0,001
    Conclusion: No big difference except for lower CLS.

    Out of curiosity I also tried enabling remove google fonts.
    * Enabling remove google fonts:
    Pagespeed, mobile: 94, 2,2s 2,2s 2,9 2,2 0ms 0
    Pagespeed, desktop: 98, 0,5s 0,5s 1,1s 0,5s 0ms 0
    Conclusion: Made an speed improvement.

    @qtwrk, it seems like none of your suggestion made any difference. Obviously removing google fonts make a difference, but it makes the site look a bit odd.

    As I’m rebuilding my site I try to avoid unnecessary plugins. My host speaks so good about your plugin. They tell me with Litespeed Cache I won’t need other plugins for speed.

    I would appreciate if you could give any suggestions?

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    if the page was built good enough , LSCWP may not be able to push much further

    Best regards,

    Thread Starter boppar

    (@boppar)

    @qtwrk

    That means your plugin can’t improve my speed? That was sad as I was hoping it would, considering how few plugins I use.

    Do you have any suggestion of a plugin that would help and that works well with your plugin?

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I don’t have any specific plugins , but generally speaking , it should work with most of plugin , as long as you don’t enable same-feature on both sides

    Best regards,

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Can’t eliminate render-blocking resources.’ is closed to new replies.