Title: Future Features   General Question
Last modified: August 21, 2016

---

# Future Features General Question

 *  Resolved [afem1010](https://wordpress.org/support/users/afem1010/)
 * (@afem1010)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/future-features-general-question/)
 * I know you’ve made a note of the cache issue the plugin has; went over that blog
   post you wrote. Any chance of that being a future feature to the plugin where
   it will have an in-built caching system? I did notice my cached files coming 
   towards the 500mb front, but am not 100% sure how to follow your blog post steps.
 * On a general front, do you know a solution to the recurring Google PageSpeed 
   Insights query point:
 * > Your page has 3 blocking script resources and 3 blocking CSS resources. This
   > causes a delay in rendering your page.
   >  None of the above-the-fold content 
   > on your page could be rendered without waiting for the following resources 
   > to load. Try to defer or asynchronously load blocking resources, or inline 
   > the critical portions of those resources directly in the HTML.
 * Now, i personally don’t find it an issue as I don’t care too much about the insights
   points (I like to see a live, fast running site). My GTMetrix score being good
   too. However, is there a solution to that via the plugin?
 * Nice work on this plugin btw! I think if the caching system were to be fitted
   automatically, this would be the cleanest and most efficient wordpress plugin
   out there.
 * [https://wordpress.org/plugins/autoptimize/](https://wordpress.org/plugins/autoptimize/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Frank Goossens](https://wordpress.org/support/users/futtta/)
 * (@futtta)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/future-features-general-question/#post-4802139)
 * Hi afem1010;
    The cache size issue can only be solved by excluding offending (
   non-static) JavaScript and CSS from being aggregated. If you disable autoptimize
   and compare two blogposts that are similar, you should be able to spot which 
   javascript (or CSS) is changing (tip; look for “nonce” in your HTML source).
 * Although it currently is not on the roadmap, including page caching functionality
   is on my wish-list. It just might take time to get around to that.
 * Regarding blocking resources; if do not ‘force js in head’ and if you don’t exclude
   js from being optimized, it will not be blocking. This is, however, not always
   possible (e.g. a lot of jquery-heavy themes don’t work that way). CSS is somewhat
   less obvious, but [this blogpost of mine explains what can be done](http://blog.futtta.be/2014/02/13/should-you-inline-or-defer-blocking-css/).
 * hope this helps,
    frank

Viewing 1 replies (of 1 total)

The topic ‘Future Features General Question’ is closed to new replies.

 * ![](https://ps.w.org/autoptimize/assets/icon-256X256.png?rev=2211608)
 * [Autoptimize](https://wordpress.org/plugins/autoptimize/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autoptimize/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autoptimize/)
 * [Active Topics](https://wordpress.org/support/plugin/autoptimize/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autoptimize/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autoptimize/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Frank Goossens](https://wordpress.org/support/users/futtta/)
 * Last activity: [12 years, 1 month ago](https://wordpress.org/support/topic/future-features-general-question/#post-4802139)
 * Status: resolved