djvdorp
Forum Replies Created
-
Forum: Plugins
In reply to: [Autoptimize] How to disable the automatic Autoptimize CriticalCSS Queue?officially this is not possible, but here’s the but; after rules have automatically generated and you’re happy with them, click on “edit” and make a tiny change and save the rule. this will change the rule from “auto” to “manual”, stopping further updates 🙂
That’s some cool hidden functionality! Then it would be a matter of generating one proper example of all types of content we have and applying the above trick! That would have to be done via auto-queueing then though I would suspect?
Forum: Plugins
In reply to: [Autoptimize] How to disable the automatic Autoptimize CriticalCSS Queue?@optimizingmatters sorry for the delayed reply, but you seem right again!
The only reasonable explanation for the server load would be a ridiculously big wp_option entry for the autoptimize_ccss_queue WP option and improper caching or the HTTP requests directed towards CriticalCSS taking too long and/or timing out.However, if I am not mistaken, creating a good manual ruleset (covering most/ all conditional tags) would mean that I have to manually add the critical CSS in these cases, which wouldn’t really be ideal? At least, the field seems to say so:
> Custom Critical CSS:
> For path based rules, paste your specific and minified critical CSS. If you want to create a rule to exclude from critical CSS injection, enter “none”What I was expecting to find in terms of functionality was something that would allow us to come up with a good manual ruleset, that would then automatically generate the critical CSS for it using the criticalcss.com service (but only once per match, in strong contrast to how the automatic queueing would create N different lines in the queue for N times that the same page template was used). Thus allowing us to benefit of the best of both worlds, without manual work 😀
Forum: Plugins
In reply to: [Autoptimize] Multiple requests outNo, but could you try this commit from the beta-branch instead? 🙂
Absolutely, we just did so, I am expecting this to be an excellent, even better fix, but if not, I will definitely report back. Thanks again for your help Frank!
Forum: Plugins
In reply to: [Autoptimize] Multiple requests outI can’t think of anything that would actually block these external requests, and can also not find any trace of them not succeeding — that is the weirdest thing. But we are currently investigating some more erratic behavior from W3TC and since that is providing our object caching layer (which might also cache options), I suspect that the problem is actually present in persisting output into the option and/or retrieving it afterward to get it back in the check you linked on line 56.
Right now, we are not using imgopt nor criticalcss (the other 3rd party service that is mentioned in autoptimize_service_availablity.json, so I would definitely vouch for a solution where this check is only done if either of the above is active!
In the meanwhile, would it hurt if we keep line 56 commented out on our site?
Forum: Plugins
In reply to: [Autoptimize] Multiple requests outThanks again @optimizingmatters — I guess the New Relic information was not super accurate, but your reply definitely is! So this is greatly appreciated.
1. unfortunately did not help, tried that multiple times in the past already
however,
2. did the trick and made the number of requests drop to 0 (as was expected)Is there a (slightly more) proper way to disable these requests, while I am obviously continuing on my investigation on why W3TC is causing these issues?
I couldn’t happen but notice you did something similar here on the beta branch of autoptimize on github, that was for mocking though 🙂 https://github.com/futtta/autoptimize/commit/ea825b43f4c84443e68b39f7d43a37fd00e90c89
Forum: Plugins
In reply to: [Autoptimize] Multiple requests outHi @optimizingmatters !
Unfortunately, it is not letting me drill down to that, but I suspect the former instead of the latter, as it also mentions that there is an X amount of time spent on
#autoptimizeCriticalCSSBase::setupbefore it seems to mentionmisc.optimizingmatters.com - all, and I assume the latter is only used when accessing the main settings screen, the contents of the little text carousel top right is also fetched (and only if you access the AO settings) like you wrote ?However, if there is an issue with storing this in a transient, that might help explain things slightly more, as we are talking about roughly 1500 calls (requests) per minute in the last 60 minutes, which is a crazy high amount 😀
Forum: Plugins
In reply to: [Autoptimize] Multiple requests outWe’re seeing similar behavior, I was just about to open my own separate topic for this. Just so this gets indexed properly by search engines, this is about:
misc.optimizingmatters.com has address 87.230.15.219
(It shows up often in New Relic as External service: misc.optimizingmatters.com)
I obviously can not answer the question for @tititoto above, but we definitely do not have transients off, but we do run W3TC object cache, which might affect transients behavior?
Forum: Plugins
In reply to: [Autoptimize] How to disable the automatic Autoptimize CriticalCSS Queue?Thanks again frank! Also for already providing the exception regarding WP Pages.
How would one go with custom post types and other types of custom pages that are not filterable via conditional tags though, as our site is rather complex here?
I suspect that we would need something like path/rule-based matching for that, which does not require conditional tags, but just path-based filtering with wildcards? If that is possible we could come up with a good manual ruleset 🙂
- This reply was modified 4 years, 5 months ago by djvdorp.
Thanks! That would be this one, right?
Eliminate render-blocking CSS?
Inline “above the fold CSS” while loading the main autoptimized CSS only after page load. Check the FAQ for more info. This can be fully automated for different types of pages on the CriticalCSS tab.
Forum: Plugins
In reply to: [Autoptimize] Autoptimize with CriticalCSS.com vs RapidLoad.ioThanks! I also got a similar answer back from the RapidLoad team, just sharing it here in case it would be useful for others searching for this as well:
CriticalCSS.com
– Generates critical css (above the fold css)RapidLoad.io
– Removes unused css
– Generates critical css (above the fold css)The advantage of CriticalCSS.com is they are in the field for long time and more battle tested. It doesn’t mean RapidLoad doesn’t perform well. RapidLoad has edge over providing 2 services together. If CriticalCSS generated on RapidLoad it should also have a similar results in page speed insights.
The advantage of RapidLoad.io is that it provides 2 services together which helps gain more scores and improves the overall speed by applying critical CSS and loading only the used CSS in the background.
Thanks @ampforwp, just emailed you.
Issue still present in v0.9.96 when combined with W3 Total Cache.
See also here: https://wordpress.org/support/topic/call-to-undefined-function-ampforwp_is_non_amp/We need to solve this publicly.
Issue still present in v0.9.96 when combined with W3 Total Cache.
See also here: https://wordpress.org/support/topic/amp-for-wp-not-compatible-with-w3-total-cache/We need to solve this publicly.
will be fixed on next check-in! thanks for your suggestion