Evening @propokerhuds;
First off; are you on autoptimize 2.2.x? because that new version has some significant improvements on board to lower the impact on page load time.
Now if you are already on 2.2.x; can you do some tests on https://webpagetest.org/ and provide me with resulting URL’s so I can review?
frank
Thank you for a swift response!
Yes, we are using version 2.2.2.
Here are the test results:
https://webpagetest.org/result/170703_XV_EGH/
-
This reply was modified 8 years, 11 months ago by
ProPokerHUDs.
Hello!
I have a similar problem, the page began to load up to 8-15 seconds, before the upgrade it was not.
There is one drawback – the cache files are not removed completely, they are stuck at a certain number and a certain weight.
https://yadi.sk/i/zMyTj3Be3KhhE2
Help!!!
@propokerhuds & @olga23 regarding the long time to first byte (time for base HTML to download);
* can you share your AO settings?
* can you (as per the FAQ) try disabling the speedupper (the new optimization logic which is supposed to make things faster instead of slower);
add_filter('autoptimize_filter_speedupper','__return_false');
* would you happen to have a non-production site where we can troubleshoot?
* you can always download & install 2.1.2 which is functionally identical to 2.1.0
@olga23; as answered in your 1-star review (yeah, it stings, sorry) this is normal behavior as AO will preload the cache immediately after being cleared to make it faster for your visitors, cfr. the FAQ.
frank
You know, it’s not helping. I know that the cache needs to accumulate, but not always the same number of bytes and files constantly. I always have 20 files and the same number of bytes.
this is a bug.
I have 10 times to use the Comet Cache to speed up the operation of the site, because after 10 minutes Your plugin slow down your website to 15 seconds.
In the previous version was nothing like that. Now the number of refusals of visitors increased, since the increased load time.
By the way, now the plugin conflicts with other plugins, it gives an error 500 – this never happened before.
@olga23; well, in that case roll back to 2.1.2 (as stated here and in your review) which I created specifically for people who need or want to stay on the 2.1 branch.
the only alternative is diving in with me (& @propokerhuds) to find out what causes the delay.
merely complaining and giving 1-star reviews however, won’t help anyone.
I agree with Frank. Being aggressive doesn’t help anyone forward. We are all working towards making our products/websites better and Frank has done a lot of work to help a lot of people achieve just these goals. And all that for no pay. Let’s give him a hand and solve this.
For the time being, I have some updates. Turning speedupper off seems to have helped although things are still far from perfect. Worst first byte times are around 1.7s now. I have been using default AO settings.
First load after activating AO took 20+s but I guess that’s expected as the cache is being built.
We don’t have an offline server but I’d be willing to help and troubleshoot this on our production install. I’d need some instructions with that tho as my experience with PHP in non-existent. Will send contact details through the contact form on your site in case you are interested in pursuing this.
@propokerhuds some things to do/ try;
* can you check how many files are in wp-content/cache/autoptimize/css and wp-content/cache/autoptimize/js and how many of those are autoptimize_snippet_* and how many normal autoptimize_* files?
* can you disable “also aggregate inline CSS” and see if that changes anything?
Counted the following files with speedupper turned on as it is by default.
– js folder has 28 autoptimize_snippet_* files and 1 autoptimize_* file.
– css folder has 17 autoptimize_snippet_* files and 3 autoptimize_* files.
Disabling the that css preference didn’t change anything that I can detect.
-
This reply was modified 8 years, 11 months ago by ProPokerHUDs.
-
This reply was modified 8 years, 11 months ago by ProPokerHUDs.
Frank, as I wrote, some bug in the update. After upgrading the plugin you have every 15 minutes to clear the cache because the pages load extremely slow, almost to 1 minutes to reach. It never happened before.
ok, let’s try another approach;
* first disable JS optimization and test; does this fix the slowdown?
* if not; disable CSS optimization and test; does this fix the slowdown?
* if not; disable HMTL optimization and test; does this fix the slowdown?
based on the outcome we can decide on what the next step would be.
Here are the test results. All measurements are for first byte.
AO off: 1.6s
AO with all 3 optimizations: 8s
AO with HTML & JS: 1.8s
AO with HTML & CSS: 8s
AO with JS & CSS: 8s
I ran each test at least 3 times and waited for a while before re-running it.
OK, clearly CSS then, very interesting.
Now next tests (again, if you have time);
* AO 2.2.2 CSS only (normal setting, including inline CSS)
* AO 2.2.2 CSS only, not including inline CSS
* AO 2.2.2 CSS only, including inline CSS but with speedupper disabled (code snippet from before)
* AO 2.2.2 CSS only, but with “look only in head” active. this is a hidden option, which you can enable on wp-admin/config.php by setting autoptimize_css_justhead to on
* and finally AO 2.1.2 (so previous version + security fix) with normal settings (including inline CSS)
frank
Here are the results.
AO 2.2.2 CSS only, default settings: 8.3s
AO 2.2.2 CSS only, aggregate inline CSS unchecked: 7.6s
AO 2.2.2 CSS only, default settings, speedupper off: 1.8s
AO 2.1.1 default settings: 1.8s
There wasn’t a config.php in wp-admin. Was I supposed to add it?
It’s interesting that first byte time doesn’t improve with any settings combination compared to AO off time of 1.6s.
interesting, the speedupper clearly isn’t working as expected for you. could you also test AO 2.2.2 with both speedupper and inline CSS disabled?
There wasn’t a config.php in wp-admin. Was I supposed to add it?
no, my mistake, it’s /wp-admin/options.php 🙂
It’s interesting that first byte time doesn’t improve with any settings combination compared to AO off time of 1.6s.
not really; AO does JS/ CSS optimization, which cannot make your TTFB lower (on the contrary, there’s always some impact, cfr. the 0.2s cost you see). getting the TTFB lower can be accomplished by using a page cache plugin (which you have if I remember correctly).
