• Resolved spirittlk

    (@spirittlk)


    Hi! I changed css on several pages last night, deleted caches in autoptimize and w3tc, removed rules from critical css, turned off w3tc page cache, clicked all pages, turned it back on, and rechecked pages… and still I don’t see any new rules in critical css and my pages are slow to load. Am I doing something wrong? Thanks!

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    Hey Ann;
    I can indeed see that on a lot (but not all, e.g. https://www.visionsofheaven.com/category/messages-from-ann-albers) of pages there is no Critical CSS (CCSS) and the full CSS is inlined intead (the fallback of the AO CCSS plugin).

    So some questions;
    * how many rules do you see now (and how many are AUTO vs MANUAL)?
    * how many jobs are in the job queue? how many in status N (new) vs P (pending) vs D (done) or E (error)?

    frank

    Hi Frank, Two rules appeared since we talked. I did recheck on the pages again so that may have triggered it. However I did that last night as well and they weren’t triggered. All are auto. When everything runs I used to have 5 total auto rules. At the moment there are tons of pages in the queue – I have over 1600 blog posts that get requeued it seems every time I delete rules.

    Hi Frank, I just talked to my server folks and there were some issues on their side. It is possible that the usual processing with criticalness didn’t run last night. I’m going to let it run and get back to you, so no need for more debug at present. Thanks for your incredible support.

    Hi Frank – Found the issue. Since my last retriggering of critical CSS, I had installed a warm-cache plugin. Between its requests to the server and the criticalness requests, I was overloading the server. So I disabled warm cache and now things appear to be working. Your plugin is great! I just have a huge site and so retriggering rules on all 2200+ pages is a bit intense! Thank you again for the support! We can close this.

    I may have spoken too soon… things are hanging again. I’m going to do some more research. Sorry about this!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    re.: “Between its requests to the server and the criticalness requests, I was overloading the server”

    -> not every job in the queue ends up as a request to criticalcss.com. in fact the majority of rules will not do so, but it’s the job of the queue processing job to make that distinction, which is why you might indeed have a lot of jobs in the queue after clearing all ๐Ÿ™‚

    I may have spoken too soonโ€ฆ things are hanging again. Iโ€™m going to do some more research. Sorry about this!

    no problem Ann. I’m going to get some sleep now, but will follow up on your CCSS adventures tomorrow ๐Ÿ™‚

    Hi Frank,

    Your plugin is fine (of course!). I discovered that I was bombarding my server with a combination of critical css, warm cache, and clicking on over a 100 pages from multiple tabs which eventually triggered them to put up a firewall for ten minutes at a time! So all is well, and thank you once again for your time. We can close this.

    If possible, can you tell me before you do – When it is appropriate to delete rules, purge caches and re-trigger the rules. For example, do I have to do that each time I add a new page, or each time I change css on an old page? Thanks!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    sure;
    * adding pages requires no cache purges (your page cache knows when a page is published and acts accordingly, AO will normally not have to do a thing (as most pages share the bulk of CSS/JS) and the CCSS-rules will automatically apply to the new page (and if not for some reason, a new CCSS-rule will be created)
    * making changes to CSS or JS might require some action indeed;
    * purge cache: your page-cache will have to be purged to make sure your changes are immediately visible. the autoptimize cache is not a must, as normally AO detects changes and will cache new files with updated CSS. you could however purge AO cache at that moment to keep the size under control.
    * you would delete CCSS rules if -after CSS updates- the CCSS somehow clashes with the CSS. if there is no “clash”, you could simply wait for the CCSS-rules to update

    hope this clarifies ๐Ÿ™‚
    frank

    That is SO awesome, thank you so much!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘No new rules’ is closed to new replies.