Support » Plugin: W3 Total Cache » Bigger & Slower

  • I’m very confused with this plugin after at least 20+ hours of trying to figure it out & having signed up to Amazon S3 … very frustrating. Maybe I don’t know what i am doing but i think i’ve followed the installation instructions and loads of online tutorials.

    According to – if I use minify “auto” mode the CSS breaks but my site seems really fast and the fewest requests and the size is reduced quite a bit but not drastically (I’m guessing the js won’t work either).
    If I use minify “manual” mode the css works, but the site gets bigger (1.5MB > 2.2MB) and the request increase (43 > 53).

    ….. just when i thought i am getting somewhere!!!

    Any ideas or suggestions?
    site: (excuse the mess right now)

    Any help will REALLY be APPRECIATED!!!!!!!!!!!!!!!!! 🙂

Viewing 15 replies - 16 through 30 (of 39 total)
  • @thomas,

    Looks like I have everything in place and seems to be working well….
    I managed to get the CDN working just fine now. All 10 set up. What I was doing wrong is that I was trying to create a different distribution for each CNAME. So I’ve created mulptiple CNAMES using the same distribution. PERFECT!!
    Do you know if each CNAME contributes towards a DNS lookup?

    Managed to get my YSLOW rating to A, but CDN still comes up as F – possibly something wrong with my page. I’ll need to see what it see. A few facebook widget links (LIKES) which may be causing the problem. I’ll see if I can do this manually rather than using the widget.

    Expires have improved to a C rating, so that’s good, but I’d liek to get everything to A’s – does this make a difference or is the overall Page rating (A) enough?

    But most importantly – thank you so much for all your help!!! I REALLY do appreciate it!

    @acp73 / Anthony,

    My pleasure, Anthony.

    Are you up to complete perfection? Here is one more small and quick step to do:

    Check your site with

    In “waterfall” view, check for all entries that start with . These are items in directories which are still not picked up by cloudfront for some reason.

    In order to get all pictures and elements delivered by amazon, login to your wordpress backend, go to
    performance –> CDN –> scroll down to “advanced”, look for the “custom file list box”.

    When I look at in pingdom tools, for example I see

    is still delivered from

    To change this, add

    to the custom file list box.

    Do exactly the same with all entries in pingdom waterfall-view that are still delivered via Find out in which directories those elements are located and add all those paths to bye custom file list box with a * at the end, just follow the scheme above. You will see that all files will be picked up and delivered by cloud front. This will enhance your site speed even more. (Could be that the line mentioned above catches all those entries already, please double check for yourself).

    By the way, pingdom tools gets you very good marks for your site (95/100). I do not know about Yslow grades, I don’t use them. More important to me seems the delivery speed, and pingdom says your pages are being delivered in 1,1 seconds to their Amsterdam service. This is fast. I guess you could go down even a little bit further if you follow the steps described above.

    Let me know how this works for you.

    Oh, and i personally have decided not to use official version This seems to be rather buggy. I do not think our sites will get much faster than we have got them now, anyway…. :=)))

    For all readers of this thread: I think wmiles forked version is the best, fastest, feature richest and most stable version out so far. Check the release notes here and here what the main differences of the official version are.
    Non of wmiles enhancements seem to have been introduced in the official version It is a complete mystery to me why not.


    You know what, I actually added that directory to the custom file list box this evening but in my haste I copied and pasted p-content/uploads/* instead of wp-content/uploads/* I have fixed it now.

    I noticed that some of the masthead images in pingdom show up as being from rather than from the CDN – I think this may be that they’re part of a rotating banner and maybe only the first image is recorded as loading from the CDN – Do you think this is possible?

    YEAH! I am also totally confused as to why the latest version doesnt include any of the special enhancements you mention above. I’m definitely staying with my beloved ver

    Thanks again man! YOU ROCK!

    Plugin Author Frederick Townes


    Be wary of forks, and be careful of those who make changes without working with the original developer of plugins. Every single bug report, code contribution et al are considered and discussed with folks that contribute. Everything mentioned in this thread has not been vetted by me and as a result will break in the future as further improvements, updates and security fixes are applied. The plugin is not in final release (v1.0) which means that no one has yet seen what is planned and what is to be offered to give all of you the same tools, resources and performance as major media companies (which is the intent of this project). While I appreciate that you all are working to help each other, all that I’m saying is that I’d appreciate if you wouldn’t assume that I’m not here to work through the concerns with you, I’ve been working on this for several years for a reason and it’s not because this is the end, this is actually still the beginning.

    Sorry for the challenges, again, this project is still not at final release. If you have questions the best place for those is in the support tab of the plugin, not in the forums… yet.

    @frederick > Sorry if it seems that we’re undermining your plugin. That’s not the case at all. I just had some issues when updating 9.2.6 so decided to roll back 9.2.5 after reading about more troubles when folk posted that the later version gave even more troubles.

    For my personal opinion, and maximum respect, the only person that seems we’re undermining this plugin is Frederick Townes … sorry! With WordPress 3.5.1 (latest version) all versione since was reported wrong by users vote system … sorry again!


    Plugin Author Frederick Townes


    I don’t feel undermined; this is not for me, this is all for you. It’s extremely difficult to collect feedback and actually resolve issues using these forums especially when so much needs to be said for people to have the information they need to apply proper judgement. Everyone is free to say whatever they like, as time moves forward so will W3TC. Your loyalty and clear bug reports are appreciated.

    Frederick Townes wrote:

    I don’t feel undermined; this is not for me, this is all for you.

    Personally, i am absolutely happy. Indeed, they are even happier since I left W3 Total Cache for the forked version, already at the time of i not only saved by the bug of security db cache, but also by the disaster for three different versions in just two days ( ~ 8) that apparently seem not yet work properly. And all this even if it blames the WP FileSystem … The handling of API CloudFlare does not work, and you can not give even blame the WP FileSystem. There are major problems on the management of Opcode, slow performance due to cache db, interference problems with other plugins cron, the function enanched disk only works with certain hosting very lucky, the management of tag Pragma is absolutely beyond any standard now known, the use of the tag in Public-cache control is absolutely unnecessary and not recommended even by google page speed …

    The new Dashboard in W3 Total Cache is a shareware/serviceware and not an enhachement … visible only with 1280×1024 pixel without scrolling browser!

    And all this comes from someone who immediately after installing WordPress, installing W3 Total Cache. So much the better WP Super Cache / HyperCache at least what they offer really works without compromise, and without blame the WP FileSystem or difficulty of reading the support forum. To me this seems like yet another excuse to force the service to be paid!

    I’m not going to wait for some version to discover that still does not work again … and not just me saying this, it seems: wait for the first useful version that actually works fine, and i will try his forked version, make no mistake again.!

    Regards 🙂

    To me this seems like yet another excuse to force the service to be paid!

    sLa NGjl’s, I personally wouldn’t go that far.
    Yes, I do believe that there is a business model behind Frederick Townes developing this plugin. His company w3 edge seems to fund itself offering services related to the plugins functionality to larger companies. And my guess is that this plugin helps demonstrating his competence to existing and potential customers.

    But no, I don’t think the flaws in with the latest updates were introduced on purpose. I think Frederick like any software-developer with a business-model behind a “free” version of his software would be ill-advised to put at risk what is most important for the brand of any software: Productivity, reliability and trust.

    That being said, I have one question and one request: :

        Question: Frederick stated in another post that the issues many users report in the forums lately have not appeared within the circle of his paying customers. My conclusion from this statement is that his paying customers work with different setups than a significant part of users in this forum. If this is true, wouldn’t it be an obvious idea to enlarge the beta-testing user base and make sure a larger variety of setups are being tested and considered in future beta-testing cycles?
        Request: What I really like (and can’t live without) about wmiles tweaked version of w3c total cache is the following functionality:
        Prime caching all pages and posts when server load is low (e.g. around midnight or 2am in the morning)
        Re-priming single pages or posts whenever they are changed or new ones are created
        make the prime cache process in the night independent from cron-calls to make sure all pages and posts have always been fully cached at all times 24/7.

    Frederick mentioned elsewhere this would not work in all setups and environments. Would it be at least possible to make this functionality an option to opt in or out?
    Why I am so passionate about this is because I noticed that priming allposts and pages has made my website so much faster that I am beating most of my competition in my niche when it comes to speed. And this is all what w3c total cache should be (and is, in my opinion) about.


    Looking at pingdom tools, on your staring page there are still some issues:

        is still not being picked up by cloudfront
        there are still some Amazon S3 – instances left:
        this .js file is not in your minify list yet and takes a long time to load

    All summed up, these issues take valuable load time. From what I can tell from pingdom tools, You are loosing around 50% load time (first call from Amsterdam server: 3,xx seconds at the moment).

    Sorry if i add in the queue, it is a bit of time I follow intrigued some of these posts.

    I have read many wp-fan posts who really do not understand.

    First he filled the message forum publicizing the forked version of wmiles, challenging Frederick Townes, then one day he said that he wrote wmiles via email to apply the changes to the version but had not received replies.

    Now it seems to deny wmiles guilty of not making changes requested by him, praising and licking instead Frederick Townes, challenging sLa NGjI always proper critical to W3 Total Cache.

    Make up your mind and take a position rather than acting like a pimp … :-))

    yeah strangely no matter what I do i just cant get “wp-content/upload/*” to be used by cloud front….
    Still all masthead images are detected by CDN either …:/

    Manually added the js – hope that is sorted now.
    Havent been able to get a test on Pingdom this evening……

    The problem with $hitstorms is that it is hard to see around the turd$ that are smacking you in the face right Frederick? LOL I feel your pain man as do all other plugin developers. The ups and downs of plugin development. Sigh.

    This is just a metaphor. I am not implying anything. 😉

    Plugin Author Frederick Townes


    @acp73, can you please submit a bug submission form from the support tab of the plugin?

    Done! 🙂

    I think I’ve come a long way since starting with this plugin… though I am not too technical and savvy with all this techy stuff!!!

Viewing 15 replies - 16 through 30 (of 39 total)
  • The topic ‘Bigger & Slower’ is closed to new replies.