Yesterday we received an unexpected email and thousands across the globe got this same email which told about the shut down of Google Pagespeed service which had been speeding up a lot of sites till date. The Pagespeed service with the DNS based solution has been permanently shut down now and only the mod_pagespeed module and other open source server side packags are still available for usage for everyone.
“Announcing the Turn Down of PageSpeed Service
On July 28, 2011 we announced PageSpeed Service, an online service to automatically speed up web pages. In the last 4½ years, PSS has delivered millions of pages for thousands of sites, all for free. While a number of sites continue to enjoy the benefits of PageSpeed Service, we see much broader adoption of PageSpeed technology through our open-source products and have therefore decided to focus our efforts on improving those.
Today we are announcing that PageSpeed Service will be turned off on 3rd August 2015. Users must change their DNS to point away from the service by this time, or their sites will cease to function. We have created a migration page that includes assistance for changing DNS as well as information on other ways PageSpeed technology can be employed on websites. Please see https://developers.google.com/speed/pagespeed/service/Deprecation.
At the same time we are also announcing the deprecation of PageSpeed integration with Google App Engine. If you are using PageSpeed integration on Google App Engine, it will continue to function until 1st December 2015, after which PageSpeed optimizations will no-longer be applied to your app. No action is required on the part of App Engine users; after this date apps will continue to operate, except without the benefit of the PageSpeed optimisations. Users that wish to pre-emptively disable PageSpeed can follow the instructions at https://cloud.google.com/appengine/docs/adminconsole/pagespeed#disabling-pagespeed.
The open source PageSpeed server modules mod_pagespeed and ngx_pagespeed and the PageSpeed Optimization Libraries are unaffected by this announcement and development on these will continue.
The PageSpeed team.“
So as you can read the contents of the above mail, we gotta say good bye to Google Pagespeed service as we knew it. So what would be your new CDN solution? We and a lot of people use Cloudflare, and it’s one of the best free CDN solutions out there. Meanwhile the mod_pagespeed package is really good and still worthy of install on all of your servers in order to include the default filter set provided by Google pagespeed which solves common issues like concatenation of JS and CSS files. Minification of files, compression of images losslessly and a lot of other small common filters.
Keep visiting for more blogging tips, how to guides, lifestyle tips, and remember we cover, “Everything under the Sun!”
Follow Inspire2rise on Twitter. | Follow Inspire2rise on Facebook. | Follow Inspire2rise on Google+.
Stay Inspired to rise fellas!
Read more Blogging articles on Inspire2rise:
- How to manage your Blogging along with studies
- Unconscious blogging mistakes you are making
- Lessons learned from blogging
- You don’t need to be an A-lister to be Kick Ass blogger
What Google going to close next ?
No idea bro, I guess they are removing everything which isn’t paying them good enough! 😀
Hi Aditya,
Is there any alternate tool like Google Pagespeed service?
To some extent you can replicate the effects by using mod_pagespeed on your server (install package server side) and by using a CDN like Cloudflare to serve static content. But there’s no CDN offering almost all the functionality offered by Google Pagespeed CDN.
I think tools.pingdom.com and gtmetrix are great tools to measure speed of any web page.. By the way i think they must not shut down their services like this
Hmm, I guess they weren’t getting anything out of this free service other than the user data so they closed it down!