Bloomberg Front Office Discontinued?

According to various users of FantasySP, it appears that the Bloomberg Front Office product is no longer offered to consumers.

One user emails me:

I don’t think Bloomberg sent out an email about FO (at least I didn’t get one), but I contacted them when it was getting close to the season and nothing showed up on their site.  They wrote back that it had been discontinued but offered no explanation.

If you know more about the decision to discontinue the Front Office product, then please comment below or email me.

It seems as though Bloomberg now focuses on draft related tools instead of in-season management.  Since when are draft tools more important than in-season team management?

In any case, I encourage all Bloomberg Front Office users to switch to the Fantasy Assistant.  A free seven day trial is available for all new users.

The Fantasy Assistant provides a multitude of features including:

  • High Risk and Low Risk waiver wire suggestions.
  • Category based waiver wire suggestions (perfect for roto leagues)
  • Position based team analysis.
  • Daily team ratings and rankings with charts.
  • Player based analysis and stats.
  • Player news from hundreds of sources.
  • And lots more!
guide how-to SEO sports

Fantasy Sports Sites Need to be Faster

The web is a mighty big place and the fantasy sports market has grown by leaps and bounds over the past 5 years.  All of that growth spawned many sites that have come and gone, in the news one day and no where to be found 6 months later.  Some of today’s best fantasy sites are having record traffic numbers, and for good reason, because they provide incredible fantasy insight.

What people often forget about, is the technology behind these sites.  Are fantasy sports sites up to date using the latest technology and do they spend time optimizing the sites for speed?  I will be tackling the latter category in this blog post: speed.    The speed at which a website loads is a huge factor in end user satisfaction.  Below you will find the best known names in fantasy sports news and I will compare them to the big boys to see how they stack up in speed.  As most of you know by now, I developed a site called FantasySP and will also show you how FantasySP compares to these sites in terms of speed.

In order to test each website’s performance, I will be using Firebug 1.7.2 with YSlow 2.1.0 under Firefox 4.0.1. I will load each site’s homepage with advertisements shown and advertisements blocked (using AdBlock Plus).  I will also be using Pingdom’s Site Speed tool to test load times. This should give a fair comparison on the speed of each site.

#1) Rotoworld

Rotoworld needs no introduction as it is the premier site when it comes to fantasy news and analysis.  However, does the same hold true when it comes to page speed and size?

Rotoworld with Advertisements

With advertisements shown, you see 228 HTTP requests and a size of almost 2 meg on initial page load.  Your second page load has 212 HTTP requests and 104k in size.  Without a question, they do a terrible job at optimizing their site for speed.

Rotoworld - No Advertisements

Without advertisements, loading Rotoworld has 214 HTTP requests and around 1.8 meg in size.  The second pageload is at 202 HTTP requests and page size is about 40k.  Blocking advertisements at Rotoworld will save you a little bit of time, but not much since their site is in desperate need of optimization.

Pingdom Load time: 9.5 Seconds

2) Rotowire

Perhaps the second biggest name when it comes to fantasy news is Rotowire.  Are they any better when it comes to load times?

Rotowire with Advertisements

Rotowire has 165 HTTP requests and the size of the page is 1.6meg with advertisements. Second pageload will see 134 HTTP requests and around 150k in size.  Slightly better than Rotoworld, but still quite poor.

Rotowire without Advertisements

Without advertisements Rotowire has 103 HTTP requests at 1.3 meg in size.  The second pageload has 88 HTTP requests and 70k in size.  Rotowire has room for improvement, but it seems most of the extra requests and bloat come in the form of advertisements.

Pingdom Load Time: 4.8 seconds.

3) Kffl

kffl is another top fantasy news site in the industry, perhaps they can do a better job when it comes to speeds?

kffl with Advertisements

As you can see HTTP requests with advertisements are at 97 and the size of the page is around 1 meg.  Second page load shows 88 HTTP requests and 75k in size.  So far kffl does a much better job in terms of speeding up the site and minimizing requests and size of the page.

kffl without Advertisements

With no advertisements, initial page load has 83 HTTP requests with the size of the page at around 820k.  Second page load has 74 requests with 77k in size.  Not too bad at all.  In fact, if they fixed the amount of images that load and the amount of javascript files then they would be a lot closer to 50 http requests.

Pingdom Load Time: 10 seconds.  (Why 10 seconds? My guess is that their server isn’t as expensive as the other two and they are in desperate need of a CDN to help with load time)

4)  RotoInfo

RotoInfo isn’t a huge name, but Fanball is no more and these guys were the only other ones I could come up with for good fantasy analysis and news.  So let’s have a look at how they perform.

RotoInfo with Advertisements

Initial page load with advertisements has 158 HTTP requests and weighs in at a hefty 3.2 meg.  Second page load has 46 HTTP requests and 80k in size.  Looks like we have a new winner for total page size thanks to their enormous added size in images.

RotoInfo without Advertisements

With advertisements blocked, it has 147 HTTP requests at 3.1 meg.  Second page load has 35 HTTP requests at 72k.  They are pretty much as bad as Rotoworld and Rotowire.

Pingdom Load Time: 14.1 seconds.

Lets Pause for Reflection

Looking at the past 4 fantasy news websites, it is blatantly obvious that these guys aren’t the best when it comes to speeding up their sites. kffl is the best at keeping HTTP requests down and page size low, but that didn’t seem to translate to a fast page.  Rotoworld, Rotowire, and RotoInfo are remarkably bad at utilizing modern techniques to make sure their sites are as fast as they can be.  Some are lacking a CDN, others are riddled with too many HTTP requests, and most have both problems.  All of these things are fixable, and I urge them to fix these problems.

So you might be wondering, how does FantasySP fit in all of this?  FantasySP was built from the ground up to be fast.  It was built because I wanted a centralized location to keep an eye on player news and manage my fantasy teams.  What FantasySP does is grab news from your favorite fantasy sites (listed above), blogs, and newspapers and presents the information to you as fast as possible.  When you read something interesting, you head over to the source site to get the full scoop.

Before I show you how fast FantasySP is, let me show you how fast ESPN and CBSSports are since they are the best in the business with an unlimited budget.


ESPN is one of the premier sports sites on the internet and they have recently undergone a major redesign.  Perhaps they need to show us how to create a speedy website?

ESPN with Advertisements

With advertisements, ESPN has 88 HTTP requests and weighs in at 800k.  The second page load has 26 HTTP requests with 62k in size.  Clearly, these guys know what they are doing.

ESPN without Advertisements

Without advertisements, ESPN has 76 HTTP requests and is 674k in size.  The second page load has 15 HTTP requests and 60k in size.  They do a fantastic job at minimizing HTTP requests, making sure the size of the page is small, and utilizing a CDN.  Even with their embedded video on the front page and interactive scoreboard, their site does a fantastic job at keeping things speedy.  Perhaps the only thing they could do to further improve things is to create a CSS sprite for some of their images.

Pingdom Load Time: 2.5 seconds. (Using the best techniques with the best hardware results in super fast load times, no surprise there)

2) CBSSports

How does CBSSports compare to ESPN?  Let’s find out.

CBSSports with Advertisements

CBSSports has 51 HTTP requests with 700k in total size with advertisements.  Second page load has 10 HTTP requests at 48k in size.  These are extremely impressive numbers considering they have advertisements shown.

CBSSports without Advertisements

Without advertisements CBSSports has 45 HTTP requests and about 700k in size again.  Second page load has 6 HTTP requests with 46k in size.  If they combined their javascript and created a CSS sprite then they would save even more HTTP requests and perhaps get it down to about 30 or 40.

Pingdom Load Time: 2.9 seconds.


I’ve talked a lot about load times and speed, so hopefully my site runs more like ESPN and CBSSports and less like Rotoworld.  Let’s find out:

FantasySP with Advertisements

With advertisements FantasySP has 55 HTTp requests at 358k in size.  On the second page load, 25 HTTP requests at 42k in size.  Clearly one of the best sites in terms of HTTP requests and the smallest in size.  This sounds great, but keep in mind that some of the other sites such as ESPN, CBSSports, and Rotoinfo have a richer user experience by including videos and/or interactive scoreboards. This is the main reason why I am able to keep page size so small.

FantasySP without Advertisements

Without advertisements FantasySP has 38 HTTP requests at 241k in size.  On the second pageload there are 9 HTTP requests with 29k in size.  When it comes to reading fantasy news, the end user might prefer FantasySP over any other fantasy site listed here based on speeds alone.  In fact, new signups to FantasySP get advertisements disabled to speed up their experience and they are replaced with Player Trends.  Hows that for enticing?

Pingdom Load Time: 1.0 seconds.

FantasySP utilizes modern techniques to improve the end user’s experience.  I use Cloudflare to speed up DNS, block bad traffic, and a whole bunch of other nuggets.  I use Amazon as my CDN. I minify and combine my javascript and css files.  I also use a CSS sprite to reduce HTTP requests.  For the backend I installed NewRelic so I can keep track of realtime performance and fix inefficiencies with the site.  I also automatically redirect mobile visits to my uber fast mobile site.  You could say I am addicted to speed, and I hope you are too.  I did all of this myself, so imagine if I actually had a team of developers and a group of people that share my vision. HINT HINT!

So What’s Your Point?

The point of this whole post is to inform sites in the fantasy news space to spend the time to improve the user experience.  The size of your homepage should not be near 3 meg in size with 150+ HTTP requests.  Your products and news are great, and all you need are some fine tuning.  Major sports sites like ESPN and CBSSports are highly optimized and well oiled machines.  There is no reason why Rotowire, Rotoworld, Kffl, and RotoInfo can’t follow their lead.  I am a HUGE fan of these sites and FantasySP would not exist without them, so please use what I’ve talked about in this post and improve your sites.

Questions?  Comments? Glaring mistakes?  Please let me know.

UPDATE:  Here is a handy spreadsheet with speed data. Light green denotes best performing, dark green good performing, orange is bad performing.

UPDATE #2: As per request, I’ve taken a look at DraftSharks.  They have also been added to the spreedsheet above.


DraftSharks with Advertisements

DraftSharks with advertisements has 80 HTTP Requests at 1.1 meg in size.  The second pageload has 6 HTTP Requests and 38k.  This puts DraftSharks on par or better than kffl.  Completely respectable job optimizing the site for speed.  Much like all the other sites, if they combined js files and created a CSS sprite then HTTP requests would be even lower.  It also wouldn’t hurt if they looked into a CDN solution if it fits in their budget.

DraftSharks without Advertisements

Without advertisements DraftSharks have 79 HTTP requests at 1.1 meg.  Second page load has 5 HTTP Requests at 38k.  Not much of a difference, mainly because most of their ads aren’t blocked by default by AdBlock Plus.

Pingdom Page Load: 7.2 seconds.  (The pageload slowdown is likely due to Pingdom adding 80 or so EXTRA images that I did not see based on my testing.)


Top Sports Websites Analyzed for Speed

Have you ever stopped to wonder how some of the biggest sports websites compare when it comes to speed and modern optimizations?  A lot of todays websites are using cutting edge features and embracing new technology, whether it be modern Javascript frameworks or a mesh of flash and embedded videos.  While it’s great to use these things to make each site appealing to visitors, it can also lead to increased load and rendering time.

For this post I will be analyzing top sports websites using Firefox’s YSlow 1.5 and PageSpeed 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.

In terms of what I am looking for to make sure a website is properly optimized are things that every web developer should be looking at.  I am checking each website for gzip compression with javascript, css, and html.  I am checking each website for the caching of images, css, and javascript.  I am also checking to see if it uses ETags, the percentage of files cached, and the length of time each file stays cached.  I am also looking at how many HTTP requests per page load, end user page load time via Chrome, and size of the page upon first load / cached loads.

I will break up the listing of websites into two categories.

The first category of websites are the top tier major media outlet sites including: ESPNCBSSportsSports Illustrated, and FoxSports.

The second category of websites I will include at fantasy sports and social media websites including: RotoworldFanballRotowireKfflYardbarker,Bleacherreport, and FantasySP .  (This will be in its own follow up post)


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.

Page Size Cached Size HTTP Requests Server YSlow PageSpeed Chrome Load Time
473.7k 61.0k 54 /  13 Microsoft-IIS/6. 61 74 4.54

The overall size of the page is quite good at under 500k and the HTTP requests number is great at just over 50.  The lack of HTTP requests is a remarkable number considering what is going on with the page.  The fewer the requests, the faster the page load.  This is a great benchmark that the other sites in the category should strive to match or come close to.  In terms of website optimizations, ESPN hits just about every optimization that’s possible for the website. They support gzip compression on javascript, css, and html.  Their javascript and css is minified.  Their images, css, and images are all cached with the majority in a future date.

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.

2. CBSSports

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.

Page Size Cached Size HTTP Requests Server YSlow PageSpeed Chrome Load Time
335.8k 174.5k 96 / 89 Apache 56 74 5.697

Page size for an initial load is an astoundingly small 335.8k, which is even better than ESPN.  Unfortunately this does not carry over to a primed cache, and the size is a little high at 174.5k with 89 requests.  CBSSports utilizes GZip compression for HTML, CSS, and Javascript.  They also minify CSS and Javascript, but they could have combined the Javascript into one file instead of several smaller files to reduce HTTP requests.  They also have quite a few images to load on every page load which accounts for an increased HTTP request count.  Some images have a cache time of today, while others have a cache time of 24hrs.  I would suggest changing all cached times to a date further into the future to reduce HTTP requests and decrease the size of a cached page load.

Overall I give CBSSports a very good rating, but could been great with a few minor tweaks.

3. FoxSports

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.

Page Size Cached Size HTTP Requests Server YSlow PageSpeed Chrome Load Time
906.8k 241.8k 91 / 89 Apache-Coyote/1.1 57 65 5.72

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  The big image shown in the flash app weighs in at 230k, which can be shrunk to 218k with  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?

Page Size Cached Size HTTP Requests Server YSlow PageSpeed Chrome Load Time
887.8k 338.7k 108 / 59 Apache 57 65 5.72

Page load size is what I feared, just about on par with FoxSports at 887.8k.  On the bright side, SI was able to create pictures that are much smaller in size for their featured stories.  So where does all the pagesize go?  The majority are images and javascript files.  Oddly enough, their biggest javascript file at 108k is not gzipped!  Many of their images have expiration dates of today or tomorrow, which results in the large cached load size.  They do have gzip compression enabled for javascript, html, but NOT CSS.  Interesting.  They also have too many separate javascript files that are not cached far into the future and should be combined if at all possible.

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.