Disabled “critical css”, still a “critical issue” in site health?

  • Resolved Anonymous User 17976131

    (@anonymized-17976131)


    1 year, 5 months ago

    So I deactivated the Optimize Critical CSS feature because I didn’t need it, but Site Health continues to show the nag that I need to regenerate my critical CSS, which I’d assumed was a nag to remind you to regenerate when you’re using the feature but hadn’t regenerated after making changes, in which case it should not be nagging me anymore.

    Is this instead meant to be some sort of nag to enable the feature, or is this a bug?

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Pete (a11n)

    (@dilirity)

    Hello there!

    Is this instead meant to be some sort of nag to enable the feature, or is this a bug?

    Nice catch! This is indeed a bug and thank you for reporting it.

    The Site Health page should not show “Outdated Critical CSS” if the feature is disabled.

    I’ve opened a GitHub ticket for it here. We’ll follow up on that the first chance we get.

    I assume this will be fixed in a patch, but having same issue. I am commenting to keep in the loop of replies.

    Plugin Support Paulina H. (a11n)

    (@pehaa)

    Hey @grungyape

    I assume this will be fixed in a patch, but having same issue. I am commenting to keep in the loop of replies.

    You can subscribe to the updates directly at https://github.com/Automattic/jetpack/issues/33526 – please notice the Subscribe button in the right sidebar. This requires a GitHub account but is the best way to keep updated about the progress on this.

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Disabled “critical css”, still a “critical issue” in site health?’ is closed to new replies.