• Resolved Ian Pegg

    (@ianpegg)


    Hello,
    I’ve spotted an issue that relates to CCSS generation in the v.3 version of your plugin (3.0.8.6).

    I had a site that was recently upgraded. I obtained a key and linked to the QUIC Dashboard but for some reason the CCSS generation was delayed – the first time I tried to force the cron I got a rate limiting error back, but a quick glance at the Dashboard showed that no requests for CCSS had been made to date.

    I didn’t believe this was an issue at first as the page still rendered correctly without the CCSS, albeit more slowly. However, I started getting errors in Google Search Console telling me that pages were no longer mobile-friendly. When I looked at Google’s screenshot I could see it had rendered the pages without any CSS at all. Forcing the CCSS cron again resulted in the CCSS being generated successfully this time.

    When I ran the Mobile Friendly Test after the CCSS generation, Google was able to render the pages correctly so I requested reindexing for the pages affected.

    I’m hoping my other sites won’t succumb to the same fate. Are the plugin authors aware of any issues in this area?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    If you set CCSS generation in background , it will be delay and require purge page cache in order to re-generate the page cache with CCSS inserted.

    Please try set CCSS generation in foreground , it will costs few seconds delay on very first time if CCSS rules are purged, but afterwards it should be smooth.

    Best regards,

    Thread Starter Ian Pegg

    (@ianpegg)

    Hello,

    Thanks for your reply. I understand how the generation system works. My understanding also is that CCSS is not required in order for a page to be displayed properly. It is just a feature that speeds up rendering, but the absence of it should not prevent the correct rendering.

    However, the issue I saw was that Google was judging the page layout without any CSS at all. Whether there is CCSS or not, the page should still have the original CSS available for rendering. It appeared as if that was not the case for four pages on the site in question – in the screenshots GSC made all four pages were just plain HTML without any CSS at all. As a result those pages failed the mobile-friendly test.

    Hope this helps.

    please stop..

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Could you please provide the report number ?

    You can get it in Toolbox –> Report.

    Best regards,

    Thread Starter Ian Pegg

    (@ianpegg)

    Thanks, @qtwrk – the page doesn’t currently display a report number. Presumably I need to submit the report to LiteSpeed first in order to get one? We might not gain much by doing so at this stage as the issue hasn’t cropped up again but I’m happy to send it through if it will help?

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Yes, please click “send to LiteSpeed” , it will generate you a string , please pass me that string.

    as the issue hasn’t cropped up again

    the issue is gone ?

    then please send it next time when it happens.

    Best regards,

    Thread Starter Ian Pegg

    (@ianpegg)

    Thanks, @qtwrk – I will send it through if the error crops up again. To date, the pages concerned are now passing the mobile friendly test and no more errors of this nature have cropped up.

    Thanks for your help!

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Pages Fail Google Mobile Friendly Test’ is closed to new replies.