• Resolved Pratham

    (@pratham2003)


    I observed that Jetpack Boost uses client-side JS and iframes to figure out critical CSS for pages in the free plan. But for unknown reason it seems to be skipping a certain page from being used for critical CSS generation. I only have 6 pages on the website. Note: By pages I mean the post_type: page.

    If I mark 3 other pages as draft then the plugin uses one of the pages that it was not using for critical CSS generation (it is viewable by looking at the URLs in the Chrome Dev Tools > Network Log (apply filter: doc) when generating critical CSS).

    Is there some internal limit on the number of pages the plugin should calculate the critical CSS for?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Pratham

    (@pratham2003)

    I checked a little more, found out it is affected by successRatio and MAX_SUCCESS_URLS / MIN_SUCCESS_URLS in the file /app/lib/critical-css/source-providers/providers/Singular_Post_Provider.php

    Edit: Can a filter hook be provided to modify the success ratio?

    • This reply was modified 2 years, 10 months ago by Pratham.

    Hey there, thanks for reporting this! Our developers were able to reproduce the issue and they’re going to check into it. Once we have an update, we will follow up here in this thread.

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @pratham2003

    Our development team has added this to their backlog. They are planning to fix the underlying logic. We’ll update this thread once the fix is completed.

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hello @pratham2003,

    A quick update to let you know that the bug fix will be release soon with the next plugin update. Keep an eye on the updates and let us know if the issue isn’t solved after you update the plugin. Thanks!

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

The topic ‘Certain pages are skipped for unknown reason from critical CSS’ is closed to new replies.