May 1, 2013 at 8:40 am #38750
I need a little help, my site at http://camcorderchris.com is loading very slowly and I don’t understand why. When I clear my cache, then open a new Chrome window it takes nearly 10 seconds for my site to load. Here’s what I’ve done so far to try to speed things up:
-installed wp-optimizer database plugin to try to clean up / make the database efficient
-installed wp smush it to compress images to make them smaller
-reduced listing of widgets that exist on the home page to reduce database queries
-installed and tried changing w3 super cache plugin settings to increase performance
-implemented cloudflare for my server
-cleaned up the site post / page previous drafts
I have the current version of wordpress installed, and with the Genesis Framework and the Associate Theme from studiopress installed.
The site has 10 published pages, 56 published posts, 2 sticky posts and 57 draft posts
I have these plugins installed:
Better WP Security
Google analytics for wordpress
Jetpack for wordpress.com
Visual Form Builder
W3 Total Cache
I’d love the feedback from any wordpress experts on what I can do to increase the site load time. I want to get to a point of having 2-3 seconds load time.
The server is hosted on bluehost. I have another site that I designed through a different bluehost account using the same theme, that has more graphics that loads in 3 seconds, so I don’t know why mine is so slow.
Thanks for your input.
Chrishttp://camcorderchris.comMay 1, 2013 at 9:18 am #38754
Interesting tricky question. When you described slowness, I was conjuring up the usual suspects I see around here: photos that are much too big, Facebook crud being pulled in that everyone seems to want, and really bad hosting that people like to buy because it’s advertised and cheap. You have none of those, congrats!
I get very good response in Firefox, but yes, I get pretty bad performance in Chrome, too. I do have one idea. I wonder if something in your site triggers Chrome’s Predict Network. You can test that by trying this out.
Click the Chrome menu Chrome menu on the browser toolbar.
Click Show advanced settings.
In the “Privacy” section, deselect “Predict network actions to improve page load performance.”
Even if that’s true, one can’t assure that one’s visitors are willing to shut that off.
That’s my best guess. Beyond that, maybe one of your plugins is fighting Chrome somehow.
Good luck, Dave
May 1, 2013 at 3:15 pm #38831
Thanks for your thoughts. I was able to improve performance quite a bit, by doing a few things:
1. Disabling and Deleting Jet Pack
3. Implemented Amazon S3 for a CDN service
The combination of those three things really sped up the performance of the site and took me from a pingdom score of 81 to 92.
I did follow a great post by Yoast a while back that talked about statically defining resources inside of your code, so that it doesn’t have to do a database query each time for that resouce. Here’s the post:
I was using either the 2011 theme or a theme from organic themes and I was able to follow the content of the post exactly and that made a huge difference in load time for my site. The problem is, the examples don’t line up to code inside of Genesis now, so I don’t know how to change things now. Any thoughts?
ChrisMay 1, 2013 at 6:16 pm #38851
I’m afraid you’re ahead of me on all that fancy optimization stuff. I avoid having an opinion where I have little knowledge.
Although I suppose if you elaborate on what you mean by “examples not lining up”, I may be able to offer a thought. For instance, there are some hooks that are less publicized than the official documentation stuff that can come in handy for shoehorning things in here and there.
May 2, 2013 at 2:37 am #38895
magnify28ParticipantPost count: 13
I have the same issue as Chris, similar plugins and same slow site load speed, about 10 secs. Did similar things to optimise like adding cloudflare, deleting jetpack and have w3 total cache.
Has not helped very much at all. Will add the CDN and see if that helps any.August 14, 2013 at 1:40 pm #56380
I have found the solution for this issue. The issue was with the database for bluehost. To fix the issue, I had to login to the bluehost control panel, under Database Tools, go to phpMyAdmin, then I determined which database was for my site by clicking on the database then going to the wp_options table and looking at the first table entry for siteurl. Once I had the right database, I selected all of the tables of the database, then under the tables list there is a drop down dialogue box, choose Optimize Table, then hit Go, and it optimizes all of the tables.
This made a dramatic improvement in performance.
Also one thing a Bluehost rep said to me is that for standard hosting accounts, theythrottle the cpu utilization and if there’s too much cpu utilization (which can happen a lot with certain caching plugins like W3 total cache) the quota is exceeded and your site will slow down from throttling. The proposed solution is to implement the WP Super cache plugin or Quick Cache plugin as an alternative. A third option is to upgrade to a Pro account or VPS server which you give you a lot more resources and efficiency.
I hope that helps everyone.
ChrisAugust 14, 2013 at 2:06 pm #56389
That’s wild. I used to routinely recommend that back in the day, and frequently did it myself. One symptom was seeing an enormous error log file that was too big to even open. But I rarely think of that anymore because recent WordPress has made strides in avoiding that from the get-go. I don’t recall the minutiae, but if memory serves, it has something to do with improvements in the handling of file locking when doing database updates.
Of course, some hosts may vary. It may be worth seeing how up-to-date your PHP and MySQL setup is – some hosts are way behind the curve for that sort of thing. I remember seeing amazingly old versions of things on Liquidweb and Namecheap (hosting, not their domain management). Or if you have a monster-sized table, frequent care and feeding is probably a good idea.
In any case, glad you fixed that.
You must be logged in to reply to this topic.