Today Google announced another new feature of Rich Snippets called Events. Of course it is a great idea to provide more markup to better track events of concerts, sporting events, movies, etc. However, what if Rich Snippets could be used for a slightly different reason? News updates on events or people. Let me show you what I mean with a real world example. . .
As I’ve mentioned tons of times before, I run a site called FantasySP which is a news aggregator for fantasy player news. What if for each player page, I add event data for each update? That way, when someone Google’s “Tim Lincecum”, they can at a glance quickly see his 3 latest updates right within the Google search page! I know this isn’t how Google intended it to be, but the results speak for themselves. Have a look:
Appearing right in the Google SERPS would be the 3 latest updates, including when they came in, giving the searcher a clear indication how fresh the content is. I would love to hear everyone’s thoughts and comments on utilizing Rich Event Snippets in this manner.
Everyone must of heard the news that Firefox 3.6 has finally come out. There is a video mentioning all of the new changes in 3.6. Mike Beltzner made mention of a benchmark called SunSpider and said that 3.6 had increased speed to 995 ms, down from 1188 ms. I thought to myself, now that sounds like an interesting thing to put to the test to compare Chrome and Firefox. Here are my own tests.
For this post I will be analyzing top sports websites using Firefox’s YSlow 1.5 and PageSpeed 22.214.171.124 extensions to figure out where each site stands in terms of performance to the end user. Each site’s main homepage is loaded without being logged in and the browser cache will be empty. For optimum load time for an end user, I will be using the Google Chrome browser Development builds because of it’s ability to load websites faster than other web browsers.
I will break up the listing of websites into two categories.
As you may remember, ESPN is among the few websites that has undergone a complete overhaul within about a year. This should result in better optimizations than the other sites. It may also be the most visually appealing website in the entire bunch.
Chrome Load Time
54 / 13
Overall ESPN has done a great job optimizing their website. While it’s final load time says 4.54 seconds, its readable much sooner than that. The speed at which it loads is phenomenal considering that the site is rich in video.
CBSSports has had their classic blue tinted website for years now. The question is if they have been able to update things behind the scenes to take advantage of modern browser optimizations.
Chrome Load Time
96 / 89
Overall I give CBSSports a very good rating, but could been great with a few minor tweaks.
Foxsports has a slightly different layout than the previous two sites because it has a much bigger flash app to showcase today’s top stories.
Chrome Load Time
91 / 89
As you can see, the page size is the biggest yet at 906.8k, and the cached size is nearly 250k. Any time page size is close to 1,000k for a news oriented site I consider that a bad job in optimizations unless they are offering a media rich experience that is far better than the other sites. As we can see from the YSlow! chart, the majority of page size is taken up by CSS images, followed by regular images. Weird huh?
It turns out that the majority of CSS Image size is due to the header image (at 62k) which can be reduced to 53k and the foxsports logo at 28.2k. While the foxsports logo size can’t be reduced on my end, there are several pictures on the site that can be redused in size simply by using Smush.it. The big image shown in the flash app weighs in at 230k, which can be shrunk to 218k with Smush.it. Keep in mind there are 5 stories in rotation that need to be loaded. The other 4 images aren’t factored into the initial page load time, but they still add up quick to people on slower connections.
When it comes to caching, the expiration dates for images, css, and js are today instead of far into the future. As a result, cached page load requests are much higher than they should be. It’s also important to note that they are using gizp compression. They also decided to use ETags, which some say it’s better to omit them all together and just include far into the future expiration dates to lessen HTTP requests. I agree with this mindset.
Overall I give foxsports a bad rating and they are in dire need for some optimizations.
4. Sports Illustrated
Sports Illustrated uses a similar style story spotlight app that Foxsports uses, but are they able to do a better job at the page size?
Chrome Load Time
108 / 59
Overall Sports Illustrated gets a below average rating because they have some glaring errors that need to be fixed.
As you can see, many of the websites have done a great job optimizing their sites. ESPN and CBSSports get tops in this category, with ESPN holding the top spot. This is likely due to the fact that it has gotten a recent redesign, and foruntately for us they’ve done an excellent job all around. I suspect CBS won’t be far behind when their redesign launches.
SI and FoxSports are a distant 3rd and 4th in terms of optimizations. As I previously mentioned they have a few glaring problems which result in slowdowns for the end user.
Hopefully this post shed some light on how the top sports websites go about their optimizations. I look forward to any criticism of my critiques or things I might have missed.
Very recently Mashable created a post on their site indicating 5 more reasons why “Internet Explorer 6 Must Die“. (Yeah, no shit!) I was so inspired by their post that I decided to create 5 reasons Mashable is bad for the Web. Mashable has so many bad habits incorporated into it’s site that I fear the rest of the web industry will think it’s okay to follow their footsteps.
It’s unfortunate that no industry leaders have stepped up to say how much their site blows the big ones. (Or perhaps I’ve missed them?) I implore everyone to post any site that rips on Mashable in the comments section below.
Now, onto my top 5 reasons . . .
1. It takes Over 30 Seconds to Load
For those of you unfortunate enough to have been linked to a Mashable story (my apologies), you’ll notice that it takes a LONG time to load. Precisely 38.98 seconds according to Google Chrome’s developer tools.
2. Mashable Loves Advertisements
In case you haven’t noticed, Mashable has 15 advertisements on their homepage. I have never come across a website with more advertisements than this, and I hardly even leave my house folks. I’ve tried!…(To find a similar banner ridden site.) Basically what Mashable is telling people is that it’s perfectly fine to have this many advertisements and completely kill the end user’s experience.
According to their traffic numbers and apparent influence on the modern web, you don’t give a shit.
This is the hard hitting journalism we expect from a website that reports the latest trends and news from social networking and social media sites.
4. Digg, Tweet, And Facebook THAT ONE!
Just when you thought the advertisements on Mashable were the worst thing about, they totally redeem themselves by including a Tweet button, Digg button, and Facebook button. Not those small crappy ones either, Ohhh no. We are talking those oversized ones that take up way too much room than they should. But just in case that didn’t get in your way, as a backup plan they have a “share” button and an “email” button just underneath. And, JUST TO BE ON THE SAFE side, they included a “Become a fan of Mashable on facebook” widget and a “Google Connect widget” on the right column of their site.
That’s Mashable for ya, going the extra mile every time. All for us.
5. Google is Happy, Internet Explorer is Sad
You may find yourself reading an article and all of a sudden you encounter some ridiculous smiley face. It’s like when I mention things like Apple or Google these faces randomly appear so you know what your supposed to think about them. What the fuck. How did the faces start popping up here?!?! Vista , iPhone , Mashable .
Though I have to admit, it totally works when I mentioned their site.
And please people, for the love of all that is holy. If you absolutely HAVE to go to their site, use their mobile version instead.
If you need a router with dual band support that is also gigabit, then the Linksys WRT610 is your best option. I have seen a lot of user reviews about dropped connections. This was mostly due to a lousy firmware, but users were also at fault for improperly setting up dual band. If you do not set up dual band support correctly, you will see connection dropouts. I recommend NOT installing the Linksys software it comes with. Please configure it manually with the following settings:
I have had this router for roughly 6 months or so and have never had a dropped connection using the configuration above. I also have seen Wireless N speeds at 90mbps and wired speeds at 100mbps. I am one of the few people fortunate to have Optimum Online Ultra, and I highly recommend to have it paired with the WRT610.
This router is as good as it gets folks, so don’t be discouraged by poor reviews by users from a year ago.
As you may have heard a while ago, Google decided to incorporate load time into where sites rank in terms of search results. The faster the load time, the more of a bonus they should get in SERPs. One of the things that slows down page loads more than anything are site advertisements. In this blog post we are going to look at what advertisements can do to load time, according to Google’s “Site Performance” chart in Webmaster tools.
For this analysis, we are going to look at FantasySP. FantasySP is a fantasy sports news aggregator that makes managing a fantasy team and tracking player’s much easier. I will show site performance when it had several ad networks compared to when it has just one ad network (Google Adsense).
Below you will see a chart of the performance of the site with about 3 to 4 different ad networks. The more ad networks should result in worse performance. The site load-time PRIOR to January of 2010 shows load-time with several ad networks. After January, just one ad network is used: Google Adsense.
Google says: On average, pages in your site take 3.9 seconds to load (updated on Jan 10, 2010). This is slower than 63% of sites. These estimates are of medium accuracy (between 100 and 1000 data points)
Quite a dramatic improvement isn’t it? The more ad networks, the worse your load time is, no surprise there. But let’s take this a step further. . .should we disable ads for Googlebot to artificially inflate load times in your favor? With no ads shown, FantasySP should load a lot faster. But we’ll get back to this in a bit.
Google says: “On average, pages in your site take 0.4 seconds to load (updated on Dec 7, 2009). This is faster than 97% of sites. These estimates are of low accuracy (less than 100 data points).”
The moral of the story is obvious, watch what ad networks you use for your website because it is killing your site’s load time. Not only for Googlebot’s site performance numbers, but your actual real life visitors as well. Why not offer a membership option for users to browse your site advertisement free, which is what FantasySP does.
As of 1/19/2010 I realized that the Site performance numbers are based on Google toolbar users load times. This means that while removing banner ads and unnecessary code snippets for Googlebot may be good because it can crawl faster, it won’t benefit you in any way when it comes to Site Performance numbers. Total bummer.
If you ever need to restart Apache via PHP, you’ll notice that the “passthru” command doesn’t quite work out like you thought it would. For those of you who have cpanel and WHM installed, this will be an easy solution. cpanelmatt at the cpanel forums created an XML-API PHP class to be able to handle situations like this.
After 5 long years using my own blog script, x-pose.org now uses wordpress. This means that my old blog is still alive and can be accessed (via google searches), but I won’t be spending the time to convert it to wordpress. From this point on it’s all new content.
The change to wordpress means that I will be able to make better postings and more frequently due to how easy it is. My first post on wordpress will touch on how to use EasyApache with WHM.