Critical CSS Cron Problem? and Don’t actually taking effect?

Well, when looking at the Critical CSS settings page, do you see a list of rules there? If you do, then you can safely ignore the warning because there is an alternative cron doing wp-cron’s job (which is great)?

You mean to this?:
https://ibb.co/JvnK8JX

???
(BTW – We have WP-ALTERNATIVE-CRON ON in WP-CONFIG.)

Another thing:
One of the 3 sites doesn’t have the “Manuel” Cron button. (MARK YOU IN THE SCREENSHOT)

It Can be because the version of this WordPress Installation is in Catalan lenguge?

And for the final.
the plugin doesn’t improve anything huh :/
can be i do something wrong, Frank?
be glad you instruct me on how to use this API.

OK, so the screenshot confirms there is no problem with cron, so you can safely ignore the warning.

Now regarding improvements; can you check if locksmithunit.com has an is_front_page rule? If so can you clear the page cache to ensure the rule is used?

If you mean this:
https://ibb.co/grNyHt1

and this is what is in blue:
https://ibb.co/261YGfd

so yes this has a front-page rule.
but don’t have any improvement…
Nothing… absolutely nothing. (no page speed, tk google, Pingdom, nothing )

Now,
I notice in one site he give me a version of HTTP and in another one HTTP.
I change all the sites inside the plugin to HTTPS ( in the “Bound domain” section ).

Another last thing Frank:
2 sites from the 3 don’t have the option:
“Manually process the job queue”

I suspect maybe it’s because of the language. (work only in English? or i am wrong?)
serious problem? ignore it? i will be glad to get a recommendation from you Franki

OK, so you have an is_front_page rule, but when checking the HTML source, the rule is not applied, so there is no critical CSS used for that page even if it is available. typically this is due to page caching, can you clear any/ all caches?

yup, i even clean Nginx as well.

on the WordPress:
Autoptimize + Cache Enabler and Docket Cache for the Persisting cache. ( i even turn him off, not connected to Critical CSS)

My server is default cPanel with Nginx (Engintron)

The only logical explanation would be you have even more caching (at Nginx level maybe)? The HTTP response headers indeed mention something that seems to confirm that;

I don’t think is this header, this header comes from Engintron inside WHM on a server level…

Nginx ( Engintron ) copy Apache, completely.
it’s not nginx, it’s come from WordPress.

Bommer, i see a lot of good results on other sites.

• This reply was modified 3 years, 2 months ago by Nadav Levi.

Ok, i think is my Mesmerize Theme.

Mesmerize theme rendering blocking all the CSS.
It mean this plugin maybe not be useful for me… :/

the HTTP response header indicates the cache is stale 123nadav, which is confirmed by the fact the Critical CSS rule (which is there) is not resulting in the critical css being used. I don’t see how the theme is involved there, theme’s don’t stop a page from being updated, but page caches do?

is not the Theme himself.
in the Theme have the option to Optimize your plugin by default.

Its checkmark by default the checkbox in Autoptimize:

Inline all CSS?	
Inlining all CSS is an easy way to stop the CSS from being render-blocking but is generally not recommended because the size of the HTML increases significantly. Additionally, it might push meta-tags down to a position where e.g. Facebook and Whatsapp will not find them anymore, breaking thumbnails when sharing.

when this is active, the other chack box above it ( the check box of Critical CSS )
is gone.

is means this plugin may not be useful to me.
this is because of my Theme, by default Inline all the CSS from your plugin.

or maybe i wrong and even if you INLINE ALL CSS in Autoptimize, you actually can use Critical CSS?

I got confused. if you do not understand this is screenshot of the check box:
https://ibb.co/NVZCbxf

the theme forces the use of “inline all CSS”? so the theme forbids you to enable “remove render-blocking CSS”??

it’s not “forcing” me, but yes, is kind of.
The developer designed the THEME with your plugin.

They have the option to optimize the THEME.
The THEME by default recommended optimizing and inlining ALL THE CSS…

It’s by default from Mesmerize Theme,
I get the same result with Optimization of the THEME + AO (Inline all CSS) by default from the THEME COSUMIZER… ( THE SAME RESULT LIKE CRITICAL CSS I SWEAR )

So, if the THEME already designed it this way, why should i spend 250 euros now
on something my THEME already covered you got me?

I was thinking this “Critical CSS” actually makes the site slimmer.
and remove KB from the CSS himself.

but this is not what this plugin does.
More than that, AO doing already what Critical CSS doing.

have Theme’s company’s relay on your plugin and optimize all the CSS by default.
It means: the Critical CSS does not have noting to optimize…

The same thing on Rapid Load.
if you INLINE ALL THE CSS, 90% you will not see a problem in PageSpeed of UNUSED CSS.

for example, this now my 3 sites:
https://locksmithunit.com
https://locksmithunit.es
https://locksmithunit.cat

right now don’t have API from Critical CSS.
the site is right now optimized only with AO + Cache Enabler.
inside AO i optimize and Inline ALL THE CSS.

https://pagespeed.web.dev/report?url=https%3A%2F%2Flocksmithunit.com%2F&hl=en

BECAUSE THE THEME INLINE ALL THE CSS BY DEFAULT.
DON’T HAVE ANY UNUSED CSS OR RENDERING CSS ISSUES.

I still want to give a shot for Rapid Load, but i pretty sure, its will be like Critical CSS and not be efficient to my website’s performance.

:/’

if i am wrong and have something you want light for me, i be glad to hear Frank.

I indeed think you’re wrong yes, because when you inline all CSS:
* the size of the HTML grows a lot (so bad for performance)
* the full CSS will get downloaded for every page, again and again, as the full CSS cannot be fetched from cache because it’s not a separate resource (also bad for performance)
* due to the CSS being inlined, the meta tags used for social sharing/ embedding will become less “visible” for twitter/ facebook/ instagram, meaning in some cases you will not have images in the preview.

so no, “inline all CSS” is not as good as “remove render-blocking CSS” no even if pagespeed insights might *seem* OK.

from what i see… the only thing is giving you is 0.2 sec less in this optimizer:
https://www.thinkwithgoogle.com/feature/testmysite/

And in page speed, you get a warning of unused CSS.
(page speed goes in the same speed with critical CSS and Without.

from what i see.
is not worth 250 euro. (especially when we know the THEME DEVELOPER set it as default)

maybe Rapid Load is better because he will do the Critical CSS and the Unused CSS.
(and he much cheaper)
I gonna test Rapidload and delete critical CSS.

I will update.