General suggestions for "slow sites". Presuming you've already checked for errors using debug mode and made certain that the site setup is optimal for CMSmadesimple (no errors or warnings during install)
First check the host, ISP and routing using traceroute (under *nix - I "think" tracert is the Windoof version)
eg.
Code: Select all
someone@work:~$ traceroute cmsmadesimple.org
traceroute to cmsmadesimple.org (207.192.69.189), 30 hops max, 40 byte packets
1 ipcop.sunnyside.home (192.168.0.1) 0.529 ms 0.567 ms 0.617 ms
2 * * *
3 * * *
4 pr.iv.at.e (private) 158.252 ms 10.176.80.2 (10.176.80.2) 160.262 ms 161.130 ms
5 10.176.81.22 (10.176.81.22) 178.079 ms 180.141 ms 308.128 ms
6 10.176.81.130 (10.176.81.130) 310.120 ms 310.520 ms 310.494 ms
<snipped>
In the above example any slowness of cmsmadesimple site should be blamed on my wireless connection provider.
Second - check your computer and browser by using another (5 dozen Firefox plugins and various av scanners and Windoof update will skew your perceptions).
When you've ruled out your everything between your screen and the host:-
1. If you have shell access, check for error messages in the logs
2. Check your access logs for site traffic which might be affecting your results
If you still haven't found the problem try 1x1 testing:-
1. Do some pages load slower than others?
2. Are the slow pages always slower? Try at least four loads with your browser cache, and debugging turned off, at two different times of day (peak and off-peak)
Analyze your test results.
If slow pages are consistently slow, what makes those pages different to other pages?
Hint: it'll most likely be images or database queries if your site caching policy is consistent.
1. Are your images loaded with height and width set?
2. Are those the correct sizes?
3. Are the slow pages pre-loading images in the background?
4. Are you using double quotes to hold strings without spaces?
If you still haven't found the problem:-
1. Disable queries 1x1 on the slow pages and observe the result.
2. Download a slow page and check the total size.
3. Validate the HTML, CSS, and javascript.
When you think you've found the problem - prove it to yourself with more tests.
Tips to reducing the problem before it occurs:-
If possible check your host before signing up (see first step) use one of their hosted sites.
the worse the host the more noise they make. Never take hosting suggestions from people who think brown makes a nice colour scheme ;-p
Develop locally using the Spartan technique - if you can make a site responsive on a resource starved machine, it should work well on production hosting.