Faster page loads and web application performance has a significant positive impact on business results. Google knows this, as do IT decision makers. However, improving page load times is far from a simple task.

A Google-led open source project and a related commercial CDN offering from Cotendo are attempting to simplify the task of improving web application performance.

The partnership between Google and Cotendo also presents another proof point to Stephen O’Grady’s claims that companies that wouldn’t traditionally meet the “software company” definition could very well disrupt traditional software vendors.

Speeding Apache 2 based websites
The newly introduced mod_pagespeed for Apache 2 module is an open source project from Google under its Page Speed family of open source projects on Google Code.

Google describes mod_pagespeed as:

an open-source Apache module that automatically optimizes web pages and resources on them. It does this by rewriting the resources using filters that implement web performance best practices. Webmasters and web developers can use mod_pagespeed to improve the performance of their web pages when serving content with the Apache HTTP Server.

mod_pagespeed includes several filters that optimize JavaScript, HTML and CSS stylesheets. It also includes filters for optimizing JPEG and PNG images. The filters are based on a set of best practices known to enhance web page performance.

Google provides additional documentation on the filter categories, the filters themselves and associated considerations before implementing the module in an Apache HTTP Server 2.2 environment.

As with most Google open source efforts, users and prospective customers are unable to purchase support or maintenance subscriptions directly from Google.

Lack of purchasable vendor support can present a barrier to adoption in enterprises without the skills or spare cycles to maintain and support mod_pagespeed themselves.

Securing a vendor contact for mod_pagespeed
This is where CDN provider Cotendo comes in.

Cotendo worked with Google on the mod_pagespeed project and jointly presented it at ApacheCon 2010 earlier this week.

Cotendo is building mod_pagespeed into Cotendo’s commercial Dynamic Site Acceleration services. As a result, enterprises gain the benefits of mod_pagespeed and also have a vendor responsible for its maintenance and support.

Cotendo claims that the use of this open source component will offer significant benefit for its customers:

This new Cotendo service will optimize caching, reduce the number of data requests, and reduce the payload size of pages, among other features. In aggregate, these code modifications, when rendered within Cotendo’s network, can reduce image size by 20% to 30% and page load time by as much as 50% on top of the acceleration already achieved by Cotendo’s existing site acceleration services including its Dynamic Site Acceleration Service.

Adopting open source projects based on productization likelihood
It goes without saying that the performance claims above likely provided significant incentive for Cotendo to leverage mod_pagespeed versus building an alternative in house.

The more important trend for IT decision makers to recognize is the fact that third-party vendors such as Cotendo are growing their product capabilities by partnering with and leveraging work from industry titans such as Google, Facebook or Yahoo – vendors that really don’t sell software or support subscriptions.

While Google, Facebook or Yahoo typically garner significant press coverage when they open source a previously internal project, it can be a risky venture for enterprises to adopt the project in question. That is, unless a third party vendor decides to productize the open source project in a fashion that can deliver and support the code for enterprise usage.

Cotendo is doing just this for Google’s mod_pagespeed project. Not all open source projects contributed by non-traditional software vendors are as lucky.

IT decision makers are encouraged to evaluate open source project announcements not just on the merit of the technology, but the likelihood that it will be productized. Doing so will help minimize risk of using an open source project that your team must support itself, or a project that struggles to attract a large user community.  It will also encourage vendors to think about partnerships and third-party productization before open sourcing a project.

Follow me on Twitter at SavioRodrigues. I should state: “The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies, or opinions.”