[Plugin: W3 Total Cache] – Beginner questions
-
Hi there, I’m testing the plugin and trying to get the most out of it, but as I am a bit confused about it, I’m posting a sort of F.A., may be good in the future as a small reference!
1) What does “Primed Cache” means? Is it a server side cache (enabled with the plugin) or a client/browser side cache (benefits after subsequent page loads) ?
2) What is the best trade off about far-future expiration headers? My site is in a initial,deep-development phase; how can I cope far-future expiration headers ensuring users will get hourly/daily updates & changes to page layout?
3) I have enabled “minifying by template”, and manually added some external javascript scripts, however YSlow is still reporting a bad grade on “Make fewer HTTP requests” because the site still has some 21 external javascript files. Doesn’t W3TC caches and minifies those external files, when those external files are manually added in the minify list?
4) I do get a bad grade also on “Put JavaScript at bottom”; I have moved all the possible javascript code in the footer, however some code will not work if moved there (social icons sharing like facebook, digg, etc). Those snippets of code are scattered around the page AFTER WordPress standard header, however once the page is rendered, part of the javascript code related to those snippets is moved into the HTML header! Is W3TC doing this for some reasons or it is a well-known WP behavior? Workarounds?
5) I get a warning in “Minify JavaScript and CSS”, as there are 2 components that can be minified:
* Inline script tag #7
* Inline script tag #8What does this “inline script” means?
6) Is there any benefit in using W3TC on shared hosting providers? Is there any chance that caching data on disk will be slower somehow in this kind of hosting solution?
Thanks fro clarifying
- The topic ‘[Plugin: W3 Total Cache] – Beginner questions’ is closed to new replies.