Speed, Chrome and bugs. I’m not talking cars, grilles and things that stick to grilles. I’m talking about YSlow Page Speed being available for the Chrome browser, without needing an add-on, like Firebug. YSlow is a tool for webmasters that helps identify ways to speed up page load time.
Download YSlow for Chrome
————-
Source
SEO Revolution Blog
It struck a lot of Webmasters as ironic that Google made page speed a rank signal when AdSense scripts was one of the factors slowing sites down. According to Google, it slowed publisher sites by about 12%.
Gone are those days. Google developers improved the show_ads.js JavaScript needed by AdSense publishers and sped up delivery of ads. Google claims the changes will speed up publisher sites by a half second or more. After running Page Speed and YSlow tests, we’ve seen a noticeable improvement in scores. Publishers don’t have to upload new code since the change is automatic. Right now, the changes are working with Chrome, Firefox, and Internet Explorer 8, with more browsers and versions included soon.
If you need to block the new ad version, set “google_enable_async = false” for each ad slot.
————-
Source
SEO Revolution Blog
Since starting in SEO, I have followed countless numbers of blogs and read a huge amount of information (most of which I don’t understand). What I always found irritating was reading a blog post, knowing the actions you need to take but lacking the technical know-how to put those actions in place. Take site speed, for example.
Site speed is a funny old thing. Ever since Google first announced in April 2010 that they were using it as a ranking signal, everyone has known that they need to optimise it. The problem is that most people just don’t know how to do it (like me: personally, as soon as I see code, I run for the hills).
To that end, this blog post is for all those SEOs out there that know they should be improving site speed, but instructions like “combine images into CSS sprites” means nothing to them. Originally this was going to be one blog post, but after researching it’s turned into what will likely be three posts. Part one will cover the reasons behind wanting to improve site speed, part two will be getting down and dirty with all the techy code stuff and part 3 will be how you can actually get developers and customers to buy into it and how to influence change.
So let’s get started!
How Important Is It?
When looking at how important site speed is, I decided it was important to look at it from various points of view:
Let’s take these one at a time…
I think it’s fair to say that common sense applies here; people don’t like browsing at slow speeds, that’s why we don’t use dial-up any more. (Plus the dial-up noise was really annoying.)
Image Source: Here
So we already know that people prefer to surf as fast as possible, but since we are geeks, we need proof, right?
For starters, Google, and in particular Larry Page, are obsessed with speed. Have a look at this article on the BBC (from 2009). The “Fast Flip” concept is mentioned, where we Twould be to be able to flip through online content as quickly and easily as we can with a physical magazine.
Additionally, Google themselves ran a test to see if slowing down the search process effected users’ behaviour. They essentially made Google slow down very marginally for a set period of time. They had two groups: a control group, who use Google as normal, and a test group. The test group’s searching habits were monitored over a period of 6 weeks while delays between 100 – 400 milliseconds were applied to their search environment. The test simply showed that the longer the delay was, the fewer searches people were likely to do.
The impact ranged from 0.2% to 0.59%, and what’s even more interesting was that in the longer delays, even after they returned to Google’s regular fast speed, they maintained their newly modified search habits.
Put simply, the effect of a slow user experience changed their search habits for an extended period of time. Bing also found that a 2-second slowdown changed queries per user by -1.8% and revenue per user by -4.3%. That’s pretty amazing. These numbers might not seem like a big difference, but think how quick Google is already: if we were dealing with a site with delays of 4 or 6 seconds, this could have a much bigger impact.
Oh, yeah – Google also like to remind you just how quick they are every time you do a search:
So we now know that it’s better for the user, but do happier users actually make us more money? Is improved site speed worth implementing?
I dug around a little and found a great article, Velocity & The Bottom Line, which has some great case studies that are worth having a look at. I picked a couple that are great examples of how site speed can affect your bottom line.
AOL conducted experiments to see how their site speed effected the way people viewed their site. For each visitor, they monitored the average load time of the pages. They then broke this down into percentiles of the highest to lowest and examined the number of page views of each group from fastest to lowest. This showed some nice numbers across a range of industries.
Image Source: Here
As you can see from the image above, the faster the site is, the more pages the user navigates through. This is true across all the areas of the site shown. More site views on a site like AOL is very important as more page views = higher advertisement revenue.
Another site which is used as a case study in that article is Shopzilla. If you are not familiar with Shopzilla (I wasn’t until writing this), they are a product comparison site which allows you to compare prices of products and help you get the best deal. They got some great results from speeding up their site and even in some aspects that you would never expect. Before the change, their site was averaging a load time of between 4 and 6 seconds per page.
After making the changes they were averaging less than 1 second consistently, and this had a dramatic overall effect.
This proves that if your site is fast, people are:
Can you imagine the testing you would need to do to achieve a conversion increase of 7-12%? Then what about the infrastructure costs? 50% is huge, especially with a site this size. Most small businesses won’t have such high infrastructure costs, but it’s still interesting to know that money can be saved in areas you don’t expect. This is the ideal situation, as sales increase + operational costs decrease = WIN.
The short answer to this is yes. Google have publicly said it’s a ranking factor, so improvement here will definitely increase your rankings.
What’s not to clear is how high up your to-do list it should be. According to Google, in April 2010 search speed affected only 1% of queries. That’s not a huge result, but I think we can assume that this number will increase over time.
But if there’s still doubt, I always refer to common sense. Browsing at speed is better for user experience, therefore Google should prefer fast speeds. Building on that, the following is based on my opinion and has not been tested, although I welcome anyone to test and let me know the results.
Personally, I think the increase in ranking may not be a direct effect of increasing site speed. I don’t think Google place enough weight on this single factor to make dramatic rises in the SERPS. Still, consider all the positive things that happen as a secondary effect of updating the sites:
These are all excellent things from a user point of view, which is obviously Google’s number one priority.
And a close second is making money. When you look at the size of Google’s Adsense network, for example, do you think they would be in favour of getting a 25% page view increase across the network as a whole by way of increasing speed? Of course they would. Results that big could mean millions of pounds every year.
It also makes sense that Google would track site user stats as well. If a site gains all the above stats, that site deserves to rank higher.
It’s all about the big picture in my opinion.
I hope this first part in the series has given you a sense of the reasons why site speed is important. If anything, perhaps for those of you about to build a site, I’ve shown why you should future proof your site by getting site speed correct at the start.
Look out for part two in this series of “Site Speed for Dummies”. I’ll be getting into the real reason I started this post, how to actually make your site faster, side-by-side site comparisons and giving my recomendations on what to do and how to do it.
Please leave comments on your own experience with site speed and I’d love to hear about any testing which you’ve done or about to do. Get me on twitter: @CraigBradford
————-
Source
Distilled – Monitoring your Reputation Online

WordPress based websites usually have not so big number of internal pages and their audience just on rare occasions is higher than 500-1000 visitors/day. But what if you are going to create large news portal based on WordPress where is predicted to come 1000+ visitors daily? In this case the world greatest blog CMS may bring you a lot of troubles regularly stucking and making visitors disappointed in the quality of your website.
So what we can do to make WordPress faster and less resource consuming? Below I will describe 3 steps to optimize WordPress speed.
1. Database structure optimization
Firstly let`s clean our website from unnecessary records and different garbage, which are usually collected in WordPress databases. Yet you need to know WordPress database structure very much good to implement such cleaning manually through phpMyAdmin. But there is another simple solution. WP-Optimize plugin will do everything instead of you. Just install it, go to Dashboard>WP-Optimize, select options you need and click on Process button. After processing WP-Optimize will provide you with the detailed report to make you really happy about website database optimization level)))

2. Caching database requests
This approach will increase your WordPress website speed really significantly. You should know, that database requests are one of the most time consuming part of «content route» between your visitor and WordPress database. To avoid this part (at least for most cases) we need to cache database requests. For this purpose you can use DB Cache. This plugin is very easy to install and use. After installation just don`t forget to setup 777 access permissions for wp-content folder and Enable plugin (don`t forget to remove full access permissions from the wp-content folder after plugin has been enabled).

3.Wordpress Super Caching
For implementing really powerful server-based caching for your WordPress website you should use WP Super Cache. It`s installation and activation process is a little time consuming, but this plugin is just must have for large websites with big audience.
Principal of WP Super Cache work is very simple. It generates simple html pages from WordPress dynamic pages. Eventually when visitor`s browser requests any page of your website, server provides him with previously saved html version of the dynamic page. In this way server avoids running heavier and more time consuming PHP scripts.

The abovementioned approaches will make your WordPress based website really fast and ready to “take on board” tons of pages and visitors!
————-
Source
SEO Blog