As far as I can tell you’re not using autoptimize mantis64, so I’m not sure how I could help?
Hi, thanks for coming back to me. I am using autoptimize, but there is something strange going on since I changed some of the settings to try and fix my footer issue. Now I am getting significantly worse pagespeed scores.
I also have Litespeed cache with their quic.cloud CDN enabled, could this be the issue on why you can’t see I’m using autoptimize?
I have messed around with the settings further and the pagescore is back to what it was before, so hopefully you can see that I’m using autoptimize.
Could you please have another look to see if you can help me?
Thanks again in advance.
I also have Litespeed cache with their quic.cloud CDN enabled, could this be the issue on why you can’t see I’m using autoptimize?
indeed; it looks like Litespeed is overriding Autoptimize, possibly resulting in conflicts. I would suggest to either disable AO or disable JS/ CSS optimization in Litespeed first and foremost?
But with both plugins on I get a great pagescore. If I disable AO the footer issue does not occur, however when I turn it back on the footer issue comes back. Could you please help me identify what I need to exclude?
I turned off all the CSS and JS optimising in LS and the pagespeed is really bad now 🙁
OK; First and foremost try to identify what is breaking the footer by just disabling CSS or JS or HTML or Image optimization (incl. lazyload). Based on that we can see what the next steps need to be 🙂
frank
I have been trying various things, but everytime I try something my pagespeed drastically drops. Could you please visit the site and look at the developer tools console for the errors to see if you can see anything wrong or find a way we can exclude whatever is messing with my footer.
the goal of my earlier question is to isolate the specific setting we need to focus on. as this is not the final step, it is too early to run pagespeed tests 🙂
so forgetting about scores for now; which of the above steps (if any) made the “footer reveal” work?
Its hard to say as it seems to be a bit random so don’t know if the cache is getting properly cleared. However I think I have narrowed it down to the JS in litespeed. Turning all of the optimisations for JS in litespeed seems to solve it. However my http requests shoot up. Also if I leave all the optimizations for JS in litespeed and turn off AO, the footer works fine.
OK, so what happens if you leave all the optimizations for JS in litespeed and turn off JS optimization in AO (but keeping AO active)?
Yes I just did this, if I turn off ‘Aggregate JS files?’ the footer seems to work as it should.
OK, now in the JS optimization exclusion field, can you try excluding one of below each line and report back?
* wp-content/themes
* OR wp-content/plugins
* OR wp-includes/js
Unfortunately I don’t think it was that, since I disabled and enabled LS again, the issue is back I have not changed any of the settings. I will keep trying.
Ok the issue seems to be with the ‘Aggregate CSS files?’ option. If I turn this off, it seems to work but I have loads more http requests, so really would like to turn this on.
Also if I turn this on with also turning on ‘Also aggregate inline CSS?’ it messes up my header and some pages just don’t load properly at all.
But with the ‘Also aggregate inline CSS?’ some pages don’t load properly such as the /cookie-policy/ page. But strangely turning on ‘Inline all CSS?’ fixes the issues on this page and it loads correctly.
I think the only solution is just not to have this reveal footer. Looks nice but not worth the time and effort!
Ok the issue seems to be with the ‘Aggregate CSS files?’ option. If I turn this off, it seems to work but I have loads more http requests, so really would like to turn this on.
assuming you’re on HTTP/2 which has great multiplexing, the amount of requests is not an issue any more really. so I would only worry about aggregating CSS if you were on the old HTTP 1.1 in which case I would propose you talk to your host to get that fixed 🙂
I think the only solution is just not to have this reveal footer. Looks nice but not worth the time and effort!
it does seem … inconvenient 😉