Google PageSpeed Service

I have both set up and so far have had no problems, the speed gain has been incredible

I ran some tests with PSS and super cache as well as autopmiser and Use Google libraries, comparing the speeds of various combinations of these plug ins with PSS. Out of the seven tests the clear winner was wp super cache (mod rewrite) with Autopmiser. Google libraries seemed to add to the time needed.
Original PSS
Test 1 7.778 3.063 No Add-Ons
Test 2 6.998 8.665 With Autopmise
Test 3 11.065 3.877 Google Libs plus Autopmise
Test 4 7.188 3.563 Autopmise, Google Libs + wp sc
Test 5 2.924 1.191 Autopmise,Google Libs + wp sc (mod)
Test 6 2.955 1.068 Autopmise + wp sc (mod re)
Test 7 1.45 1.272 wp super cache only

I would probably need to do the tests several times to give them any real validity and note the odd result of Test 2 but I thought it might be useful for anyone thinking of using PSS alongside super cache

What about W3 Cache? And What are u use?

I only tested wp super cache, but on the Google PSS faq pages they mention W3 by name and say it will work with PSS without any problems

Why would you want to run WP Super Cache (or W3TC) in addition to PageSpeed service. Just curious.

Forgive my ignorance, but what is Autopmise?

Gary,

WPSC makes, at its best, php and mysql queries redundant in serving the page – it offers a static file, which hugely saves server resources.

PageSpeed module does other things – it handles minifying, image progression (lossless compression), etc.

So you could say WPSC minimizes the server-side load, while PageSpeed module optimizes the client-side payload.

That’s the simple way of looking at it, I suppose.

As for the PageSpeed Service (not to be confused with the module): PSS is a Content Delivery Netowork (CDN) solution that, with the huge benefit of Google global points of presence, hugely cuts down the distance between the end user and the delivery server. So a) response time is much faster; b) service uptime is guaranteed no matter what traffic you got; and c) security is warranted (no DDoS attacks and such).

Thanks Biranit. I use Google PageSpeed Service on a number of WordPress Sites and it perform minification, caching etc. i.e. all that W3TC and WP Super Cache does (and more) hence my question why someone would run W3TC/WP Super Cache in addition to Google PageSpeed Service.

I think people are confused around the terminology:

Google PageSpeed Tools: This is a set of guidelines and tools that speed up WebPage load times.
Google PageSpeed Service: A Service offered as part of Google PageSpeed Tools. Google PageSpeed Service delivers content via the Google CDN and also performs optimization to images, minification etc. (similar to CloudFlare).
PageSpeed module for NGINX and Apache HTTP Server: Caching and other Web page optimization performed on the Webserver. Part of Google PageSpeed Tools.

There are a number of other tools and services as part of Google PageSpeed Tools.

But PSS is not the origin. It pulls its content from the origin server – why would you not want to run wpsc there? The speed difference is huge. And the end user feels it.

We don’t use PSS but we do serve our entire site via CDN, and there is no doubt the combination – wpsc on the origin with CDN for front end – is the perfect solution.

Google PageSpeed service optimizes and caches and then delivers via its CDN.
Try Google PageSpeed Service; I’ve tried WP Super Cache (with and without AWS CloudFront CDN and MaxCDN), W3TC (with and without AWS CloudFront CDN and MaxCDN), CloudFlare Pro etc and Google PageSpeed service (without the Plugins) is, in my opinion, far superior.

Although the layout of the table in my post above became a little confused in the post, the results show a marked improvement when using PSS in conjunction with a caching program and the minification plug-in (in my case the Autopmise plug-in). To better understand the table note that the first number after the test number is the time to deliver the page without PSS switched on, the second is with PSS switched on. From this admittedly not-too-scientific exercise the clear winner was PSS +autopmiser + wp super cache.

Google itself recommends using a local cache program prior to PSS

Gary, I’m sorry but what you say just does not make sense, because you’re ignoring the pullzone. The processing and delivery speed of the origin has a major effect on overall delivery speed. WordPress is a dynamic web application, using some of the most resource-thirsty (not to mention slow) processing there is. Without something like wpsc it makes the origin very slow and will therefore affect the delivery. Of course, if all you got is a single installation of vanilla Twenty-Twelve / no plugins / no nothing / one post a day, then the benefits are somewhat diminished. But with 4 million visitors a month and some 50,000 articles, wordpress alone – even with PSS – is not good enough and certainly not as fast as it is with wpsc.

Steveb123: Could I get a link to Autopmise please? I can’t find this plugin anywhere. In fact, the only results on Google are you mentioning it – and I’m very curios about it. Thanks ??

Biranit, You mention that I’m ignoring the Pullzone. This isn’t correct; Google PageSpeed Service isn’t merely a CDN … it caches and optimizes content from the Website as well as delivering via a CDN i.e. uploads from the origin then optimizes (as W3TC and WP Super Cache do) and then delivers (effectively delivering a static file). Using Google PageSpeed Service means that the cached Pages (stored by Google PageSpeed Service) are delivered to Web browsers.
To be honest, I’m just commenting on my experience using W3TC, WP Super Cache, CloudFront, CloudFlare, Google PageSpeed Service etc. I don’t believe that there is any ‘one size fits all’. I have clients using one or combinations of the various Plugins and Services and alot depends on budget, needs etc.

@biranit

https://www.ads-software.com/plugins/autoptimize/

Oops typo in original post….Sorry

Thanks, Steve ??