Autoptimize does not cache pages, it only optimizes JS, CSS, HTML, Google Fonts & Images (all depending on configuration off course).
hope this clarifies,
frank
Hi Frank,
Thank you for the swift reply!
Just one more clarification:
Why under your FAQ does it say this? “It concatenates all scripts and styles, minifies and compresses them, adds expires headers, caches them”
Apologies for the layman question. I just want to make sure my geo-ip location shortcodes aren’t affected by this unique cache.
Thanks again!
because it caches the optimized JS/ CSS for re-use, but the page (HTML) is not cached 🙂
Hi Frank,
I understand some people have had issues with the cache building up.
Are you familiar with ‘Kinsta hosting’ or the ‘GeneratePress’ theme? Does this plugin play well with them? I have no other plugins. I have my cache disabled on kinsta and cloudflare.
My website gets around 50,000 visitors a day and I want to make sure I don’t run into an issue where the cache size fills up and crashes the site. 🙂
What are your thoughts?
Thanks
cache buildup happens when plugins (or pagebuilders) inject non-static JS or CSS code inline in the HTML. it’s a matter of properly configuring AO not to aggregate those to avoid the cache to fill to fast.
and Kinsta & GeneratePress are great products and do work well with AO! 🙂
Hi there,
Thank you for your swift reply. I’m not a developer, so this is tough for my to understand.
I have 1 plugin that generates a dynamic geolocation:
https://wordpress.org/plugins/geoip-detect/
I use a shortcode syntax in my pages.
For example:
Top 10 Pizzas in [geoip_detect2 property=”mostSpecificSubdivision.name”]
That shortcode changes to the user’s state based on their ip address.
For example:
Top 10 Pizza in New York.
Question:
Does it seem like this Geo location plugin is injecting non-static JS or CSS code inline in the HTML? What are your thoughts?
Thank you!
can’t say really, depends on how the logic is implemented. and even if it were the case, it does not _have_ to cause issues, (re-)configuring AO to exclude inline CSS/ JS is sufficient to stop cache size issues from happening 🙂
I understand. Can you please take a quick look at the screenshots on this guide:
https://generatepress.com/fastest-wordpress-theme/
Which settings should I leave UN-checked to avoid this inline issue?
Apologies for the layman questions. I am not a developer. I want to be sure I do this right.
Thank you!
start with those (those are sound defaults) and if a problem with cache size does occur you might have to untick “also aggregate inline CSS”.
thank you so much..
What do you think about “Async JavaScript” ? Should I download and use that too? Is it a good plugin for GeneratePress + Kinsta?
depends; when using AO most JS is deferred already, AsyncJS would only be useful if you have externally hosted JS that is render-blocking.
