Feature Request: static page/html cache

  • if3a

    (@if3a)


    9 years ago

    Before version 2.0, every website I tried to put Autoptimize on had to be thoroughly tested to ensure the website was not broken and performance was acceptable. In most cases I would spend a lot of time picking and removing scripts but all of these problems disappeared after 2.0. You have given us a completely free plugin that does pretty much everything I could want it to do, while other developers would charge a yearly fee for. I’m truly grateful.

    To avoid hitting PHP, decrease load and increase capacity, I have to use static HTML caching. As you probably already know, static HTML cache can allow a 1 hit per second shared hosting account to serve hundreds of hits per second. The only 2 reliable plugins that do static caching best is W3 Total Cache (which is bloated) and WP Super Cache (which doesn’t work with Apache 2.4). Sometimes WP Super Cache randomly decides to clear cache even though the timeouts are set to 0 (infinite). HyperCache (your favourite) unfortunately uses PHP (the bottleneck of most servers) to serve files.

    Is there room some where down the line for you to add static caching to Autoptimize?

    On a side note:

    There’s a problem where if Autoptimize is enabled the site will time out. These are sites running on VPS’s with timeouts set for 10+ minutes. They work on some sites and won’t work on others. It’s most likely because the theme and/or plugins are heavy but I wouldn’t know where to begin. The only option I have is to not use Autoptimize on them.

    There’s one other problem (or nuisance, or feature request?) and hope I explain this properly)… say if we set autoptimize to combine all javascripts, it will generate 1 file and that will work without problems. Then you come across some pages that are specific to a plugin, like a contact form or map plugin which includes an extra resource which will then cause autoptimise to generate a completely separate cache file. Usually I visit the common types (a page, a post, archive page, specialised pages etc) and compare the most common resources and then simply set Autoptimize to skip/exclude files that aren’t loaded in every single part of the site. It can take a lot of manual work and I don’t mind putting the effort in, it’s just that on sites that use visual editors for example (js_composer), it can be extremely time consuming to go through hundreds of pages and then compare the resources they load. Is there anyway for you to build a feature/option that will scan for the common scripts and automatically exclude the non-common ones? It’s a really big ask so I’m hoping to just put it in your mind and see what happens in a few years.

    Anyway that’s all I wanted to say, many thanks for a great plugin (I’ve been using it since 0.4 or 0.5!).

    https://www.ads-software.com/plugins/autoptimize/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Frank Goossens

    (@futtta)

    Is there room some where down the line for you to add static caching to Autoptimize?

    not in the nearby future, but who knows, one day (this actually is on my wishlist) …

    WP Super Cache (which doesn’t work with Apache 2.4). Sometimes WP Super Cache randomly decides to clear cache even though the timeouts are set to 0 (infinite).

    did not know that. how specifically does wpsc not work with apache 2.4 (apart from the nuisance that can be wpsc’s .htaccess)?

    There’s a problem where if Autoptimize is enabled the site will time out. […] it can be extremely time consuming to go through hundreds of pages and then compare the resources they load [to exclude them from optimization]

    for both use cases you could hook into the whitelist filters (autoptimize_filter_css_whitelist and autoptimize_filter_js_whitelist) to tell AO what to optimize, in which case everything not in those whitelists will not be optimized?

    but nice to know you’re a long-time user (long before I took over from turl)! ??

    Plugin Author Frank Goossens

    (@futtta)

    just saw https://www.ads-software.com/support/topic/support-for-apache-24?replies=2, I know understand how wpsc doens’t work with apache … donccha can be a hard man to reach indeed.

    frank

    Plugin Author Frank Goossens

    (@futtta)

    @if3a; 2.0.1 will be out soon, do give that a spin if you have some time ??

    frank

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Feature Request: static page/html cache’ is closed to new replies.