4 ms·
Google has been testing a 'hosted' version of mod_pagespeed over the last few months. It's currently invite only but what you do is you add a CNAME record to yo
by ashray 14y ago
Google has been testing a 'hosted' version of mod_pagespeed over the last few months. It's currently invite only but what you do is you add a CNAME record to your domain and point it to google's caching servers.
So then what happens is that Google does a fetch from your server, and optimizes the response using mod_pagespeed techniques (including throwing your static assets onto their CDN and other funky stuff..).
Basically, all your CSS/JS/page-content/images get fetched through google's CDNs but this functionality relies on one critical part of the framework functioning really well - Google's connection to your origin server.
This is where it's at: https://developers.google.com/speed/pagespeed/service https://developers.google.com/speed/pagespeed/service
Also, yeah my site is for the world at large and that's why this is an issue. I can definitely see how it's useful for personal websites and small projects.
- alanctgardner2 14y agoOK, that makes more sense. Actually reading the site, I don't see why anyone would opt for that service over something like CloudFront and some manual optimization, unless it was a very small project.
- igrigorik 14y agoIf your upstream bandwidth to Google is poor, chances are, your upstream bandwidth is poor for most other users. In other words, I would consider this an issue on its own, and one definitely worth investigating. CDN's are popular for static content, but there are a number of very good reasons to proxy dynamic content through your CDN as well. The most obvious advantage is that you can terminate the TCP connection much closer to the user, and then can leverage the optimized backhaul network to fetch from origin. This alone can be a huge win, especially if you have SSL in the mix, which requires 2-3 RTT's before it can even send the request.