Time flies. It has been almost two years since the Yottaa team started. A key question that drove us to start Yottaa was “What Is Internet Anyway?”.  We thought about this question long and hard.

What is the Internet, anyway? Below is The Today Show’s discussion about what is Internet in 1994. Watch it, and I’m sure that you will enjoy it!

Yes, in a relatively short period of time, the Internet has come a long way. However, it still just reaching its toddler stage. If you think the previous years are about getting the Internet in place so that Today Show hosts don’t need to ask Alison to explain what Internet is, then the next phase is to get it working well and working better – faster, secure, reliable and clean. -That’s what we are up to. Besides the recent announcements of Yottaa Web Performance API and the revolutionary Content Delivery Network (CDN) service, stay tuned for a lot more to come in the near future.

Sunday’s game between Knicks and Dallas Mavs drew huge viewership both domestically and internationally – even Mark Zuckerberg came out to watch the spectacular performance from Jeremy Lin amid his busy Facebook IPO schedule:

Mark Zuckerberg is A Jeremy Lin Fan ( (surprising quality shot from a far distance)

However, success can be your worst enemy, especially for website operations.

The surprising rise of Jeremy Lin is propelling NBA and Knicks to a new height in popularity. However,  it can also mean the worst nightmare for the web operations teams. A couple of weeks ago Yottaa reported that SuperBowl AD websites went down during SuperBowl (see  http://blog.yottaa.com/2012/02/burstbowl-wrap-up-super-bowl-advertisers-website-performance), including brand names such as CokeCola and Accura.

NyKnicks Web Operations team should know it now in a bitter and sweet way: New York Knicks websites have been down  starting from the middle of the Knicks-Mav game when Yottaa initially noticed. These sites include:

1. www.nyknicks.com
2. www.knicks.com
3. http://knicksnow.com/live
4. http://www.nba.com/knicks

Knicks.com Can't Handle the Traffic from Jeremy Lin

From the the moment that Yottaa noticed sites down, it has been 65 minutes and they are still down.

Yottaa is all about making websites run well, run fast and run reliably.  So we did some analysis on why knicks.com went down and what remedies available.  The biggest problem we see about Knicks.com and nyknicks.com is that it didn’t have the infrastructure in place to support the #linsanity traffic. The sites seem to go to a single IP address, and are using old generation CDN services that aren’t designed for the modern web. As we pointed out earlier in a different post (see http://blog.yottaa.com/2012/02/introducing-yottaa-cdn-a-revolutionairy-content-delivery-network), the modern web has evolved beyond the traditional CDNs. It is time to use the new generation CDN solution like what Yottaa provides – which has the intelligence at the network layer to handle surprises like this.

At the time of this writing, these sites are still down.  Yottaa has added website monitors to monitor these sites and we’ll be able to report back when these sites are back online.

ps. At 4:20pm ET, Knicks team added an HTTP redirection to redirect all traffic to a static splash page: http://www.nba.com/knicks/splash_new_york_knicks_social_media_2012_02_15.html. However, http://knicksnow.com/live is still down.

Imagine for a moment the clichéd Valentine’s day emergency: a hurried, last minute scramble to grab a gift, which features frantic Internet searches for inspiration, and usually ends in a simple gesture like flowers or chocolate.

That’s why e-commerce sites for florists can’t rely on steady traffic in the weeks leading up to February 14^th.  Boyfriends, husbands, sons, daughters, and friends of all kinds will rush to the computer by the thousands on the 12^th, 13^th, and even 14^th to order flowers.  In fact, it is predicted that 1/5th of all flower customers will buy online, and those that do will probably choose from one of the five most visible flower websites: Teleflora.com, 1800Flowers.com, FTD.com, Proflowers.com, or Floristexpress.net.  These major flower sites must be ready for the traffic spike if they are to capitalize on their biggest holiday of the year.

Furthermore, due to competition these websites not only need to handle a flood of traffic without crashing, but need to go above and beyond by having fast page load times and a great user experience.  A Google search for nearly any flower-related keyword currently brings up 11 or more paid search results for flower websites, meaning that potential customers wont have any trouble finding a competitor if their first choice is annoyingly slow to load.

Our Benchmark 

With all this on the line, we wanted to find out which of these five flower websites is best disposed to handle the V-day traffic. Among other metrics we used Yottaa Score, a compilation of website performance factors that measures how fast a website loads from dozens of locations around the world. Our benchmark showed some pretty drastic differences.

The winner in overall Yottaa score, Floristexpress.net, was a bit of a surprise to us.  Last year when we analyzed flower websites on Mothers’ Day, this site was not noticeable enough to be included.  This year, however, we noticed a lot of paid search results leading to the site, so we included them in the benchmark.  We found that it was significantly faster than the others!  Its “time to interact”—the final stage in the loading process—was consistently faster than all other sites.   What kept it from having a Yottaa Score higher than 63 seems to have been its erratic load times in other locations around the world, what we call “global reachability.”

Teleflora made a splash in this year’s Super Bowl, with an ad starring a seductive Adriana Lima.  The ad was a departure from the company’s first Super Bowl effort in 2009, which went for a starkly humorous approach.  But despite the fact that their ad was much more visible (and saucier) than any of their flower selling competitors’, the site’s performance was just average.  It was not the worst of the Super Bowl advertisers—it didn’t crash or seriously slow down that night—nor is it the worst of the flower sellers.  But with a Yottaa score of 32 it is in the middle of the pack by rank and well below the average score of  41.  That score is in keeping with its scores for the past 2 weeks, generally in the 30’s.

At the bottom of the ranking is 1800 Flowers, a brand familiar to this writer because the site’s ads have been appearing on my Amazon Kindle for the past month.  Its slow page load times could be linked to the one major differentiator found in our benchmark: the site has FAR more assets than any other.  Generally, more assets means a slower site, and loading nearly 200 assets all but assures that 1800 Flowers would not be a fast site for anyone.

Does It All Matter?

Of course it does. E-Commerce websites need to be fast in order to achieve success in metrics like conversion rate and order size.  We don’t know yet how these sites will come out of the Valentine’s Day season in terms of business success, but it is certain that each of them, especially the bottom three, could have achieved better metrics and better marketing ROI if they’d had better performance.

Plus, think of all the time lost in office day productivity caused by slow flower websites. If you are a manager, you should hope that your employees were using Floristexpress.net!

Photo Courtesy of Dennis Mojado.

 Yottaa Launches the World’s First Modern CDN or Content Delivery Network

Content Delivery Network (CDN) technology has been a crucial component in speeding up the web over the last 15 years. The CDN industry is large and growing. According to AccuStream Research[1], the worldwide CDN market size is about $3B (US is about 65%, $1.87B) and grows at about 20% per year[1].  There are many successful companies in this industry: Akamai, Limelight Networks and CDNetworks.  Even Amazon.com entered the industry with its CloudFront CDN.

We at Yottaa, however, believe that CDNs must adapt to the modern world.  Why? CDNs lagged behind the modern web. They are failing to deliver on their promise to accelerate web applications.

That’s why we are announcing Yottaa CDN – a new generation CDN service that actually speeds up the modern web.

How Yottaa Accelerates CDN Powered Websites

To illustrate the power of Yottaa CDN for this blog post we selected some websites that are already powered by the best-of-breed CDN solutions in the market today: amazon.com and cdnetworks.com.  Amazon.com is powered by one of the best existing CDN solutions. CDNetworks.com itself is a market-leading CDN vendor.

We are applying Yottaa CDN to these CDN-accelerated websites to demonstrate how this new generation of CDN services revolutionizes the industry.

Case 1: Speeding up Amazon.com

Website: http://aws.amazon.com

	# Round Trips	Download Size(KB)	Time to First Paint(second)	Time to Display(second)
Without Yottaa	43	795	1.8	3.0
With Yottaa	30	471	1.5	2.2
Results	30% reduction	41% reduction	18% faster	27% faster

Figure 1 How Yottaa Accelerates Amazon.com - Loading Screen Capture

Case 2: Speeding up CDN Provider www.cdnetworks.com

Website: http://www.cdnetworks.com

	# Round Trips	Download Size(KB)	Time to First Paint(second)	Time to Display(second)
Without Yottaa	133	2,236	2.1	12.3
With Yottaa	75	1,307	2.1	8.1
results	43% reduction	41% reduction	-	34% faster

Figure 2 How Yottaa Accelerates CDNetworks - Loading Screen Sequence

The Web Has Evolved Beyond Existing CDN Technology

The Web has evolved.  CDNs have not.  In fact, CDN technology hasn’t changed much since it was first introduced 15 years ago.

Figure 3 CDNs were created 15 years ago for web pages that looked like this

When the CDN industry was launched, web pages were primarily text and images loaded from the same domain. There was little or no programmatic code that needed to be executed inside the browser.  The only thing a browser needed to do was to retrieve the content and render it.  No doubt, delivering the bits faster with a CDN certainly sped up overall performance for these simpler sites.

Figure 4 The same home pages above, but in 2012. Today's websites are complex applications that are executed in the browser.

Modern webpages are totally different beasts.   Today, the average webpage totals 966KB, including 175KB JavaScript, 33KB style sheets, 83KB Flash, and 604KB images (see Figure 5: Average Modern Webpage Size and Figure 6).

Figure 5 Average Modern Web Page Size and Content

More importantly, the nature of the web page has changed. With the wide adoption of interactive technologies like Ajax and JavaScript, and the explosion of 3^rd-party widgets from Facebook, Twitter and Google, modern web pages have grown to be complex creations that require browsers to perform a great deal of work. On average, a web browser makes 86 round trips requesting files from the web server, loads1MB of content, and resources from 14 different domains.  This involves parsing and applying complex styling rules, and executing 175KB worth of JavaScript from over a dozen distinct script files. In truth, a modern web page is a highly distributed program that executes inside a browser and must be assembled from tens of disparate web servers distributed over the Internet.

Figure 6 Average Javascript files and size in modern web pages [2

The problem is compounded by the growing diversity of web clients.  Ten years ago, web developers could get away with focusing almost exclusively on Microsoft Internet Explorer. Nowadays, developers need to worry about at least four desktop browsers:  Internet Explorer, Firefox, Chrome and Safari (see Figure 7: Browser Market Share). Further, the difficulty in creating a fast and consistent website is constantly increasing with the growing popularity of web browsing from smartphones and tablets (see Figure 8: Smart Phone Market Share).

Figure 7 Browser Market Share

Figure 8 Smart Phone Market Share

The Bottleneck of the Modern Web is Page Execution, Not Page Delivery

The bottleneck of the web has changed. In the early days the problem was delivery, because web page content was mostly from the same domain, and there was little execution logic on the client side. Browsers loaded up the page content and displayed it. Page load time was basically determined by how fast content could be loaded.  Speeding up the delivery of assets would certainly speed up the page load time.

The bottleneck of the modern web is the distributed execution of web pages.  Page load time is fundamentally determined by how the page is executed by the browser.  While CDN solutions can help speed up the delivery of some of the bits, they do nothing to address the challenge of this distributed execution.

Extensive research from Google, Yahoo and others has drawn the same conclusion: 80% or more of webpage performance hinges on page execution, not page delivery[4].  Figure 9  shows the page load time, the number of seconds for page delivery and the number of seconds for page execution for a few popular websites: JetBlue, MLB, CNN and New York Times. In all these cases, 90%+ is spent on page execution.

 

Site	Page Load Time(seconds)	Page Delivery (seconds)	Page Execution (seconds)	Percentage due to page execution
www.jetblue.com	7.38	0.548	6.832	92.6%
www.mlb.com	8.58	0.701	7.879	91.2%
www.cnn.com	4.96	0.372	4.588	92.5%
www.nytimes.com	5.16	0.456	4.704	91.1%

Figure 9: 80% Web Performance is Page Execution[5]

Figure 10 shows the specific details for New York Times homepage[6]:

 

Figure 10 New York Times Homepage Loading Timeline

The Truth is… the Traditional CDN Isn’t Effective Anymore

For modern webpages, using a CDN doesn’t really make a difference in page load time. Figure 11 shows a study comparing the average website speed against websites that are using CDN.  This study is based on the 50,000 websites that are tracked by Yottaa’s Website Monitoring service. Each website is measured by recording its Time to Title, Time to First Paint, Time to Display and Time to Interact. These are the four key moments in a webpage loading process that defines the loading user experience:

1. Time to Title: the amount of time it takes for the browser title bar to change
2. Time to First Paint: the amount of time that it takes for the user to see something painted in the browser window
3. Time to Display: the amount of time that it takes for the page elements to be fully displayed, but not all components have finished loading yet.
4. Time to Interact: the amount of time that it takes the page to be fully loaded and ready for user interaction.

Statistically, the averages of these four key metrics for all websites tracked compared to those that are using CDN are essentially the same. CDN usage is barely a factor in page load time for these websites.

That’s not to say that traditional CDNs are completely useless.  If your website has large assets such as video or images, CDNs can help distribute heavy traffic loads to multiple locations in order to avoid congestion on a network that could impact a user’s Internet experience. Hence, a CDN can help ensure that your content is always available to your website visitors no matter their location or the time of day.

Figure 11 Average Website Loading Performance vs. Websites that Use CDN

 Enter Yottaa CDN

The CDN industry needs to evolve to address the demands of the modern web. Existing CDN technologies have been stale for almost 10 years.  The good news is that new CDNs are emerging.

Yottaa CDN represents the first real innovation in the CDN industry. It is designed from the ground up to address the real challenges of the modern web. Yottaa CDN is built with patented cloud-routing technology on a global, hybrid cloud network spanning more than 20 strategic locations, Yottaa CDN provides an infinitely scalable network service that accelerates the distributed execution of modern web pages.

While traditional CDNs are mostly about delivering the bits, the core of Yottaa CDN is “web optimization”.  Yottaa CDN is built upon an intelligent layer of software that is smart about browsers, devices, the network, and website content. It caches assets at the edge like other CDNs, but unlike any other CDN, it also constantly applies optimizations for the purpose of speeding up the execution of web pages. Figure 12 shows a list of Yottaa CDN features.

Yottaa CDN Features	Optimize for Context	Reduce requests	Reduce Payload	Parallel processing	CachingDelivery	Traffic routing
Mobile aware	✔
Browser aware	✔
Network aware	✔
Combine CSS, JS and images		✔
Inline small images, JS		✔
HTML5 local storage		✔
Client side caching		✔
Image right sizing			✔
Lossless image compression			✔
Lossy image compression			✔
Apply GZIP compression			✔
Minify code			✔
Load scripts asynchronously				✔
Pre-fetch assets				✔
Domain sharding				✔
Optimize client and edge caching					✔
Automated edge delivery					✔
Geographic proximity routing						✔
Global load balancing/failover						✔
IP shielding and site protection						✔
HTTP and TCP Tuning						✔
Routing around congestion						✔

Figure 12 Yottaa CDN Features

Want to try Yottaa CDN on your website?  Sign-up for Yottaa and try our Site Speed Optimizer service.  You’ll get access to a 14 day trial and access to our global hybrid-cloud network of over 20 locations.  Try Yottaa today.

---

[1] AccuStream Research, “CDN Business Transformation and Market Analytics 2012 – 2014”, http://www.accustreamresearch.com/products/cdnbustrans2012-2014.html

[2] HTTPArchive, http://www.httparchive.org

[3] StatCounter, http://statcounter.com/

[4] Yahoo, http://www.yuiblog.com/blog/2006/11/28/performance-research-part-1/

[5] Yottaa, http://blog.yottaa.com/2011/09/the-future-of-the-web-is-cloud-accelerated

[6] Yottaa, http://www.yottaa.com/url/www-nytimes-com-4bdad0b4425bdb0c0300025e/page_load;

This morning we were happy to see the news that Akamai Technologies acquired mobile website performance company Blaze Software.  The move represents progress in the CDN space, where web performance optimization is taking center stage in the quest for better web acceleration as we see it here at Yottaa.

Web performance matters a great deal for businesses and consumers.  At one time Content Delivery Networks (CDNs) were a good solution to the web performance issue—but now the Web has evolved, and CDNs have not.  The fact is, CDN technology has changed little since it was first introduced 15 years ago. 

We want to congratulate Akamai for acquiring Blaze Software, because it shows that they see the future of web acceleration is in optimization, wherein “content delivery” is only a part.  Akamai’s acquisition comes less than a year after Limelight Networks acquired AcceloWeb, a similar web performance optimization company. All this activity means that it is evident where web performance is going – the future is “optimization”.

Traditional CDNs will be dead unless they make big changes and adapt to the modern web. Here at Yottaa we are focused on making the web perform better for all users – The problems are not solved and the Web is evolving rapidly. There are tremendous opportunities ahead for vendors, customers and consumers for a faster and better web. 

One of Yottaa Website Monitor users ran into some problems recently – their site has been quite slower since February. They checked into Yottaa – below is what they see for their site performance trending in the last 30 days:

Obviously you can see “Time to Interact” is significantly slower in February. The question is why? From the trending chart, if you click into details and get to see waterfall diagrams on how the page has been loaded by real browsers, they quickly found the reason:

It was caused by Facebook and Google +1 widgets.

On different days in February, both widgets had performance issues that took as long as minutes to load. Below are examples;

Below shows how Google +1 was causing problems:

Surprisingly enough, we have seem plenty of data points like this among many customer websites. The other widget that we have seen similar problems frequently is Google Analytics – from time to time, it also drags down customer websites performance by as long as one minute.

Have you seen similar problems on your site?

Oh… some many things to talk about… the game… the ads… the crashes of websites. Where should I begin? I think that everyone knows the score now New England 17 – NY 21. Fuck! Even from Beijing this one hurts for me. As someone here at Yottaa’s Beijing office explained to me; today was America’s Spring Festival (Food, drinking, gambling, parties, family). You can feel this game coming to the wrong conclusion. Even at the start of the 3rd quarter, I got an eerie feeling of the outcome. It was the same feeling I had watching the Super Bowl commercial’s websites.

All day Sunday the Yottaa monitored 46 Superbowl Ad websites to see which one would experience downtime or significant slowdowns. In some ways, it was as much fun as watching the game. Next year, we will need cameras in all IT departments for each website and watch them work like crazy trying to resolve their site crashes.

There were 3 big losers on Sunday:

cokepolarbowl.com

Oh the polar bear lovers really took this website offline for quite some time. You can checkout the following screen shots to see the damage.

Here is the Facebook.com for the Coke Polar Bowl app, you can see that it can not be found. Then shortly afterwards the company put up this maintenance page.

actofvalor.com

This site was fun to watch because before and after the game the site performance was quite good.

But look at the chart above. You can clearly see from this graph the site was having significant problems during the Super Bowl. Every time their ad would play, the site would go down. We detected at least 6 outages of 5 minutes. One of the other things to note on this site is that during the Super Bowl the site was 5 x slower. During the non-Super Bowl hours the sites average load time was 3.2 seconds (not too bad), but when it was game time the site slowed to a grueling 13.9 seconds. So much money spent on all those ads just drove people to a dead or slow website.

www.acura.com

With the Yottaa Website Monitor service at yottaa.com you could easily detect the outage they were experiencing using our “Check now” button to collect the data instantly. Even though Acura’s homepage was not that crashing, the call to action link was. The launch of their new performance car was met with poor performance from their website.

You can see 4 out of 5 agent locations have reported that the site timed out just trying to download the HTML file. With an ad spend of $3.5 million plus production costs  for 30 seconds of a commercial, leaving visitors with a bad experience is not the way to launch a new car.  Acura’s website needs to be up, even during a traffic spike.

Overall Traffic Conclusions

During the Super Bowl traffic to the websites slowed by 6%, highlighting the importance of web performance. Website performance is critical. For example, Amazon reports that a 100 millisecond delay on their website equates to a 1% drop in revenue.

81 failed page loads – each problem lasted at least 5 minutes. These numbers are striking, our Yobots are patient… they will wait up to 2 minutes to load the page; Super Bowl viewers… not so much. I am betting Super Bowl watchers will wait about 3 seconds before drinking more beer or needing to wipe chicken wing sauce off their iPhone.

Conclusion

Oh, wait . . . my predictions for our #BurstBowl competition. I forgot to mention them and there is a good reason for it… they sucked. Cars.com, TaxACT.com, GoDaddy.com and History.com all fared really well during the Super Bowl. I predicted the sites crashing as well as I  predicted the release date of the Yottaa Site Speed Optimizer.

This blog post is simply a recap what happened and an offer of how to fix website performance. But, if I had give one piece of advice it would be… “live load testing”. Every one of these websites should have run a load test against their production system. Every one knew the visitors were coming, there was no reason to leave it to chance.

The fun isn’t over. #Superadmonday is just as important. Most people will log on and look over all the ads one more time, vote on their favorites, morning shows will replay them… We will keep tracking these sites and let you know if any website joins the #BurstBowl hall of fame, just like my dreams of running through Beijing yelling “Viva La New England”.

Bob (Buffone)

What those eager viewers actually find when they go online, though, is another story.  When a customer visits a website that is slow (or even down), they leave or form a poor perception of the brand.  They don’t hear the message, they don’t share the story, and they don’t come back. Site speed and website reliability matter.

#BurstBowl 2012

Here at Yottaa we are passionate about website speed and reliability.  In celebration of the biggest advertising and sporting event of the year we decided to have our own Bowl: the #BurstBowl.  We’ve been tracking the performance of all known Super Bowl advertisers’ home pages for weeks, and we’ll continue to do so throughout the game and afterward.  If any sites slow down or go down, we’ll know right away.

We’ve already made some predictions about which sites that will perform best (we see you, Kia.com), and which will crash and burn (ah hem, Cars.com), based on their current performance metrics.  To judge the sites we use the Yottaa Score, our very own performance metric that’s a compilation of the most crucial factors in site performance.  [See more about the Yottaa score below.] 

After the Super Bowl we will announce the winners and losers of the #BurstBowl—but in the meantime Tweet at us with your own predictions.  What sites do you think are going to crash or slow down significantly?  Use the Yottaa performance chart on burstbowl2012.com to help you make your predictions.  Predict correctly and you could win an Amazon Kindle Fire!

We hope the horrible fate of crashing doesn’t befall any of the advertisers in thisyear’s Super Bowl (just kidding, we kinda do).  But regardless we’ll say: Play fair, and may the best site win!

The Yottaa Score factors in how fast the site displays the page title, the time it takes for core content to appear and the time it takes for the page to be fully usable (“time to interact”.) The score ranges from 0 to 100. A higher score means a better page load user experience. Looking at the chart we can clearly see that sites vary greatly in their web performance.

Remember, visit www.burstbowl2012.com and place your vote!

Today is an exciting day at Yottaa. We’re announcing the launch of three – yep, three! – new APIs. These APIs provide developers and partners with access to our massive amounts of web performance data, and support integration of Yottaa with all kinds of web applications.

Our clearly documented APIs provide access to massive amounts of web performance data

Every day, our “YoBots” (real browsers in the cloud) collect detailed performance metrics for over 70,000 websites, from locations all around the globe.  That means TONS of highly-valuable data on how websites perform. (It’s literally hundreds of gigabytes per day.)  Since we are big supporters of open data and open applications, we came up with some new ways for developers easily and efficiently to access website performance data and to interact with Yottaa accounts.

Which API is for you?

The Partner API, User API, and Public API collectively support a very broad range of uses. With the Partner API, Yottaa’s business and alliance partners (such as Acquia and hosting companies that run cPanel) are now able to provision new Yottaa accounts on behalf of their clients. They can then immediately pull website performance metrics (e.g. page load time) for their customers’ sites into their applications and control panels.  The User API provides developers of 3rd party apps and dashboards with programmatic access to individual Yottaa user accounts (via OAuth) in order to integrate all kinds of Yottaa functionality. We can’t wait to see the creative uses developers come up with for it. The Public API is for any and all developers to access Yottaa’s public data, which includes free site speed tests, public benchmarks, and other reports.

JSON, REST, Documentation: We built these APIs the way we like them

Our APIs use the latest methods to help you consume our rich data. They’re RESTful and use standard authentication schemes appropriate to their use.  They all support JSON responses.  They are straightforward and clearly documented.  If you can’t tell already, we really like providing easy access to our data.

“So What?” — How to Use Yottaa’s Data

Yottaa’s rich data can tell a lot about a website.  Some users can find benefits in publishing the data through a customized dashboard for others to look at and interact with.  Some users will go a step further and integrate performance statistics from websites into their Business Intelligence (BI) tools.  This can provide increased visibility and help teams tie website operations data to business metrics.  Yottaa’s live website performance data can also be used to jump-start DevOps projects, be they for testing a new system or seeing early warning signs of issues with existing systems.  We look forward to seeing developers and users get creative to leverage the huge resources we’ve created!

The Next Step

If you’re not already a Yottaa customer, create a free account with Yottaa to gain immediate self-service access to the Public and User APIs. You can read all the API documentation here (with code samples):

• API Overview
• Partner API documentation
• User API documentation
• Public API documentation

Finally, if you’re interested in becoming a partner, or just want to learn more about how Yottaa works with companies to make their websites faster, visit our partner page or email sales@yottaa.com.

We look forward to your comments and questions!

We’re pleased to announce that Yottaa and Acquia are teaming up to offer Acquia subscribers a webinar titled “How to Make Your Drupal Site’s Pages Load Faster with Yottaa Site Speed Optimizer” on January 31, 2012.

The webinar follows the announcement today that Acquia, the enterprise guide to Drupal, has integrated Yottaa’s Site Speed Optimizer with its Acquia Network Services marketplace. Acquia subscribers will benefit from Yottaa’s cloud-based service that automatically makes Drupal sites load dramatically faster.

Click through for more information and to register for the webinar.

Webinar: “How to Make Your Drupal Site’s Pages Load Faster with Yottaa Site Speed Optimizer”

Date: Tuesday, January 31st at 1:00pm ET.

Presenting: Bryan House, VP of Marketing from Acquia and Coach Wei, CEO and co-Founder of Yottaa.

Attendees will learn how to:

- Assess website performance problems

- Fix your website performance problems yourself

- Improve your website performance with Yottaa Site Speed Optimizer

To register for the Webinar please go to:

Acquia and Yottaa Webinar Registration