Example of a finished Concrete 5 site that is not slow

Permalink
Does anyone have an example of a well optimized for speed Concrete site. Just so as I know that it is something that I am doing. What is an example of fast loading Concrete built website.

The one that I was working (although needed a few tweaks in the image optimization ) scored really low for page speed ( 40% ) using Google Page Speed test- my sites that I regularly build score in the 90s%. I know we can say "Who cares about Googles Page Speed test" but I think if Google has invested that much effort and money into this, there is a good chance that a slow speed result in their algorithm could mean bad user experience and reflect how you place in the Google SERPs

INTcommunications
 
Blenderite replied on at Permalink Reply
Blenderite
Here is a page that has some good suggestions to speed up your site:
http://www.concrete5.org/documentation/how-tos/developers/five-easy...

Also you can try this:

1. Go to Dashboard > System & Settings (way down at the bottom) > Optimization > Cache & Speed Settings. Then turn off all the cache settings on that page.

2. Go back to Optimization and click Clear Cache.

If these fail, let us know!
INTcommunications replied on at Permalink Reply
INTcommunications
I have read that - I just want to see a site that someone perceives as optimized so I can have an idea just how much can be done or what to shoot for.

I am not certain the logic in the building of the site as to loading or not loading at runtime. Even queries that go no where ( js, css, files etc. ) that run a query just to return that they are not needed - is basically not needed - I don't understand why the js and css to run the editing doesn't just get loaded when someone logs in. End users that are not editors should not have those queries run.

Also, what happens if Concrete is on a Windows Server. Is any of the speed optimizing happening then?

Just curious.
Steevb replied on at Permalink Reply
Steevb
I always aim for high score and have a couple that are okay. Nothing fancy in design, just lightweight and to the point:

http://www.mindandbodyfusion.co.uk/...

http://thundridge-wadesmill.co.uk/...

http://blackdoggames.co.uk/

http://mmwelding-fabricationltd.co.uk/...
frz replied on at Permalink Reply
frz
Windows = bad.

http://www.mini.co.uk/ seems pretty fast.
so doeshttp://www.plannedparenthoodaction.org/...



best wishes

Franz Maruna
CEO - concrete5.org
http://about.me/frz
Blenderite replied on at Permalink Reply
Blenderite
Planned Parenthood ... A despicable organization!!!
MysteriousCleon replied on at Permalink Reply
MysteriousCleon
If there would be a Like button, I would like obc's post.
frz replied on at Permalink Reply
frz
way to stay on topic gang.
frz replied on at Permalink Reply
frz
Mini's suck too.
So do Hummers.

Betcha my plumber hates my tastes in music.
INTcommunications replied on at Permalink Reply
INTcommunications
Thank you 55webdesign- site speeds are 97 out of 100 - Maybe simple but it shows me that the chassis ain't broken. Thanks again

Franz - both of those sites rate in the 70s - I would consider that slow. Their problems seem to be with images though so again - thank you at least I see that higher page speeds are obtainable.
frz replied on at Permalink Best Answer Reply
frz
yeah PP's action site is actually a concrete5 instance running through Varnish so I threw it in there to mess with ya. It's concrete5, but Varnish does complete HTML caching on everything - and is blisteringly fast. So as far as the world is concerned its actually faster than Apache and static HTML files.

Goes to prove that the whole "my site is 70 out of 100" thing is a bit goofy at best.

Not to say there isn't "waaaay tooooo slow" but I think this is one of those diminishing returns issues as you get above 60%
dsdev replied on at Permalink Reply
Hi Franz,

We have a site that is using Varnish. We have had to open a port that isn't cached so that admins can do their changes to the site. Is there a way that you can do the same without having to do that. For example, have it so that when logged in, then don't cache.
We have gotten to this place, because users would be making changes and then they wouldn't be able to see anything changed unless the cache was cleared, which regular content editors don't have access to. Makes it difficult when there are about 50 people updating the site.
jshannon replied on at Permalink Reply
jshannon
ds: we've got a c5 site that's being heavily cached too (though probably not by varnish). We had to set a c5_is_editor_or_admin cookie on login, and configure the cache to bypass itself for those users.
Steevb replied on at Permalink Reply
Steevb
Most sites will hit good scores with the right server settings and design.

A few obvious 'Page Speed' requirements:
Leverage browser caching
Optimize images
Specify a Vary: Accept-Encoding header
Specify a character set
Specify image dimensions
Serve resources from a consistent URL
Minimize redirects
Enable Keep-Alive
Enable compression
Avoid CSS @import
Avoid bad requests
Put CSS in the document head