Site moving very slow
Permalink
I love concrete5 as a CMS. I use it with most of my side clients, but I'm noticing that
C5 loads terribly slow. Is this just the CMS or what?
http://www.frankskikids.org is a site I recently worked on and it's unbearable. I've been considering just moving back to wordpress.
Any ideas?
C5 loads terribly slow. Is this just the CMS or what?
http://www.frankskikids.org is a site I recently worked on and it's unbearable. I've been considering just moving back to wordpress.
Any ideas?
Which version are you using? I'd really recommend upgrading to 5.5+ The speed has changed dramatically and is much much faster now.
It's on 5.4.2.2
Some hosts can be very slow in concrete5 for a variety of reasons. Typically, it comes down to how their particular setup works.
Concrete5 is not blazing fast to begin with. One thing that helps a lot is using APC for opcode caching. This helps cut down on concrete5's spinup on each serve.
Also turn on basic cache if you haven't.
Have you written any custom blocks? One slow block that is timing out on a curl request can cause the heavy slowdowns you are seeing.
You site seems pretty straight forward. My gut is that you host isn't set up in a way that deals well with concrete5.
Concrete5 is not blazing fast to begin with. One thing that helps a lot is using APC for opcode caching. This helps cut down on concrete5's spinup on each serve.
Also turn on basic cache if you haven't.
Have you written any custom blocks? One slow block that is timing out on a curl request can cause the heavy slowdowns you are seeing.
You site seems pretty straight forward. My gut is that you host isn't set up in a way that deals well with concrete5.
Check to see if your host runs sql on a separate server. Many host do and this will slow things down. If you can get a hosting account with sql on the same server, this will speed things up.
Look at the network tab of the developer console. That will tell you if any parts of pages are disproportionately slowing things down, or maybe missing.
For example, multiple loading of the same image, js or css file, or a missing image, js or css file, that the browser waits for a long time before deciding to timeout.
For example, if you have 10 missing bits of image eye-candy in an inconsequential bit of page design, thats 10 browser timeouts involved in every page load (and timeouts can't get cached)
For example, multiple loading of the same image, js or css file, or a missing image, js or css file, that the browser waits for a long time before deciding to timeout.
For example, if you have 10 missing bits of image eye-candy in an inconsequential bit of page design, thats 10 browser timeouts involved in every page load (and timeouts can't get cached)
Your page speed has a score of 77/100 to improve on this you should leverage browser caching,
Most of your cacheable resources only have a lifetime of 4 hours,
Others have no lifetime at all,
If you add this code to your htaccess file it will increase this lifetime to 2 weeks,
Most of your cacheable resources only have a lifetime of 4 hours,
Others have no lifetime at all,
If you add this code to your htaccess file it will increase this lifetime to 2 weeks,
#Increase cache time for resources ExpiresActive On ExpiresByType image/gif "access plus 2 weeks" ExpiresByType image/jpeg "access plus 2 weeks" ExpiresByType image/png "access plus 2 weeks" ExpiresByType image/ico "access plus 2 weeks" ExpiresByType text/css "access plus 2 weeks" ExpiresByType text/javascript "access plus 2 weeks" ExpiresByType application/x-javascript "access plus 2 weeks"
