Why would just changing the css of a page block something like that?
the only logical explanation would be the inline CSS is that big (or has code in it that changes, busting AO’s cache) that the site is slow/ times out/ goes in server error @sguerreiro. try not aggregating inline CSS to see if that fixes things to confirm?
@futtta
Actually now that you mention that, I had to split the initial css file in order to create the critical path css. Could having that much CSS cause that kind of damage?
It _could_; css minification is rather costly (hence the importance of AO being able to use cached minified code).
if I were you, I would:
* uncheck “aggregate inline CSS” to see if this solves the problem
* check “aggregate inline CSS” but exclude specific blocks of inline CSS that could bust the cache, using (semi-)unique strings in the specific block you’re trying to exclude
* try switching to the legacy minifiers (see FAQ) to see if this performs better
frank
I’ve unchecked the “aggregate” option and the problem disappeared but it didn’t influence the speed at all.
Is there a way to find out what CSS could potentially be breaking it? There’s a lot of css so going through and testing blocks would be very time consuming.
If i switched to the legacy minifier, would i retry with the aggregate checked?
it didn’t influence the speed at all.
do you mean you didn’t see a drop in Pagespeed score (which is good) or that you didn’t see your get faster after the drop in performance when experimenting with AO CSS settings?
Is there a way to find out what CSS could potentially be breaking it? There’s a lot of css so going through and testing blocks would be very time consuming.
Afraid there’s no easy way, but if the problem indeed is with AO’s cache getting busted, you could look for CSS-selectors that have “random” names?
If i switched to the legacy minifier, would i retry with the aggregate checked?
yes, you could. easy enough to switch, so ..
do you mean you didn’t see a drop in Pagespeed score (which is good) or that you didn’t see your get faster after the drop in performance when experimenting with AO CSS settings?
I tried it without the aggregation and above the fold css, it was 91. With aggregation and above the fold, it went up to 97. But seemed to slow down in my browser. So i took aggregation off and left above the fold on and it’s back down to 91. But isn’t loading slowly in my browser now.
-
This reply was modified 9 years, 2 months ago by
sguerreiro.
Just tried with legacy minifier. Same issue. Google says 97 but takes forever to load in a browser.
hmmm … can you share your URL so I can have a quick look?
Sure. The URL is https://www.clicklockroofing.com
I have the aggregation on right now so the Google speed is up.
Sorry if you haven’t checked it yet. Had to remove the aggregation so that i could run some tests on it. I’m not sure how accessible it is with it on.
hey @sguerreiro; had a look, it seems like you have *something* (a plugin or an option in your theme?) inlining all CSS? can you disable that so that only *real* inline CSS is inlined, allowing AO to kick in?
frank
Hey @futtta,
I’ve noticed that before. I believe it’s the theme. it seems to generate all the assets using inline css. I’m assuming this is a bad practice for a site?
Well, if this is the theme then it’s doing a very invasive job, as it also inlines the CSS of all plugins. If I were you, I would search for info on how to stop this behavior (with an option or a filter maybe).
now you got me curious; what theme are you using @sguerreiro? 🙂
Hey @futtta,
The theme is called Sarraty.
