hey Will; can you
1. delete wp-content/uploads/ao_ccss/queuelog.html?
2. delete all jobs in the queue?
3. enable debug logging?
based in that I can start looking into this.
frank
OK, I’m seeing “Queue is already running, skipping the attempt to run it again”, so can you also delete wp-content/uploads/ao_ccss/queue.lock ?
Hi – I have deleted the file and the huge queue that had built up (turned off debug). It is sort of working now, but the queue builds up too quickly again.
As yet it has not run a file for the homepage – nor has it processed a path pased file /trucks-for-sale/ that I requested ages ago.
Also the target rule/page type is showing the same (listings) for both individual products and for (some) archive pages.
I think the queue just builds up too quickly for the system to function?
Can you disable “also aggregate inline CSS” and re-clear the queue?
Done that – a new, long list generated with some ‘Uknown’ flags.
All we need is one CCSSfor the listing archives, one for listings product page – plus a few for the homepage and some statics?
“unknown” jobs generally indicate issues in the communication between your server & criticalcss.com I’m afraid ..
what you could do to simplify things is create a couple of manual rules for those and let the plugin take care of the other automatically?
Not sure I’m up to making a manual one – do I use the CCSS website and copy/paste the code?
indeed;
1. click add rule
2. choose conditional
3. from the dropdown choose the applicable conditional tag
4. generated the critical CSS for a representative page for that tag
5. copy/paste the crit. CSS from (4) into the form from (3)
6. save/ submit
do that for your main pages and make sure to save the entire ruleset.
I have added these manual rules, but I am not sure that they are correct (I pay for the CCSS service so I don’t have this responsibility.) I have noticed that there has only been one API call to my CCSS web account since the 5th November (when there were loads) could this indicate a different issue?
I have added these manual rules, but I am not sure that they are correct (I pay for the CCSS service so I don’t have this responsibility.)
well, yes and no; by paying for CCSS you have:
* AUTO rules being created (which is the default really)
* but also the possibility to create manual rules
* and obviously access to criticalcss.com to generate CCSS yourself
but I had a quick look around and for the homepage and for /trucks-for-sale/ things look OK really 🙂
I would advise to exclude uploads/2020/09/08/TruckPages.co_.uk_.jpg from being lazyloaded, that will ensure the header does not change size.
I have noticed that there has only been one API call to my CCSS web account since the 5th November (when there were loads) could this indicate a different issue?
yes, also see my comment on the U jobs, these typically indicate communication issues between your server and the critical CSS server :-/
Many thanks – will start to look at page speed again son.
So I need to get in touch with the CCSS team about the server connection?
re. server connection; re-enable “debug logging” for an hour or so (after having removed the file maybe, it seems to get quite huge in your case) and then check if there is any relevant info in there?
