A you've thrown up a pretty big, general "what if?" query here Andy, its somewhat invalid.
Speaking also, very generally, if you take those simple guidelines from Nate Cockley's presentation and apply them - your site will be as fast as it needs to be 95% of the time. Google have indeed started ranking based on response speed (stated here: http://googlewebmastercentral.blogspot.com/2010/04/using-site-speed-in-web-search-ranking.html ) On Thu, Apr 15, 2010 at 1:31 PM, Andrew Snow <[email protected]> wrote: > > > Ben Schwarz wrote: > >> I'd like to throw in two points: >> * More than 80% of performance in the browser is directly related to >> what you do on the front-end >> > > This seems to be over-generalised. What if my server-side CMS is poorly > written and some pages are taking seconds to render on the server? > > I'd imagine Google are only looking at server response time for the > purposes of ranking, and not client-side rendering or execution time. > > (Would be interesting to see them penalise sites for being > javascript-heavy, or using Flash!) > > - Andrew > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rails-oceania%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
