Autloaded Data

evening @kbowson;
I’ll tell Jonas you were happy ??

Regarding;

Autoptimize inline and defer… was AUTO loading something like 740,000, on every page

I’m not entirely sure what you mean really. autoloading is a term used when talking about WordPress options (which by default auto-load), is that what you’re referring to? And are you referring to the Autoptimize core “inline & defer”, or to the “Autoptimize criticalcss.com Power-Up” that Jonas distributes and which extends AO core?

frank

Yes sir!

I’m talking about wp-options autoloading. I’ve found that by reducing the amount of data that the page HAS to autoload, we’ve significantly reduced our load time. It also improves out object cache.

Here is what it is showing, as well as the bytes that are being autoloaded:

72574 autoptimize_css_defer_inline

ah, that’s the amount of bytes that are being autoloaded, now I understand.

well, the amount of bytes would directly relaated to the size of your “critical css”, so there’s not a lot that can be done there I’m afraid (although 70KB does seem like a lot of data tbh, but I guess you’re combining critical css for different pages?).

frank

Oh, that is critical css? My bad. I may be translating the amount of autoloaded data incorrectly. That line was bigger than any other single item by 2x. Yeah, we have like 6 different page-styles, so have 6 different critical CSS options.

Would making it so this does NOT autoload adversely affect anything?

Would making it so this does NOT autoload adversely affect anything?

well, it would slow down the creation of the HTML-with-critical-css a bit, as the option would not be autoloaded so it would have to be loaded on demand (from the db). so from that point of view having it autoload does seem like the correct thing to do really.

Hey Frank, alright, that makes sense. Will try to cut down the number of different pages that are autoloading. Thanks a lot for the help.

Happy holidays!

• This reply was modified 6 years, 11 months ago by kbowson.