Jump to content

Google page speed service


Recommended Posts

Posted

Does anybody have any experience using Google's program called page speed service https://developers.g...espeed/service. ?

We all know the key to anything on the internet is speed. However, I don't know if Google speed works in a lot of cases because I think a lot of speed problems are associated with the database not the page elements like images, CSS or HTML. That stuff is tiny. Slow site speed may be more associated with a database that may be sluggish. However, I did see some efficiencies when running my url through their test http://www.webpagetest.org/compare

Also, I am not sure how popular it would be to point your dns to google. I would be interested in the opinions of anyone that has tried the service.

Posted

I've been testing Pagespeed on one of my development forums. However, I'm actually using Pagespeed as an NGiNX module. Meaning, my server does all the processing. There's no using Google as a third party. Essentially I believe they offer the same services.

I use the following filters on my development forum, and I believe it's made a notable difference.

  • Combine CSS
  • Defer Javascript
  • Rewrite CSS
  • Fallback Rewrite CSS URLs
  • Lazyload Images
  • Local Storage Cache
  • Move CSS to head
  • Outline CSS
  • Outline Javascript
  • Collapse Whitespace
Posted

I use the following filters on my development forum, and I believe it's made a notable difference.

Do you have before and after WebPageTest results that we could see?

robert

Posted

Do you have before and after WebPageTest results that we could see?

SPDY disabled - PageSpeed disabled:

http://www.webpagetest.org/result/130330_YN_W89/

SPDY disabled - PageSpeed enabled:

http://www.webpagetest.org/result/130330_CR_W8K/

SPDY enabled - PageSpeed disabled:

http://www.webpagetest.org/result/130330_X8_W5R/

SPDY enabled - PageSpeed enabled:

http://www.webpagetest.org/result/130330_NR_W77/

It makes a notable difference to the raw page loading speeds without SPDY enabled. Which considering you probably don't have this enabled on your server, that's what really matters to you. Even if you're one of the few taking advantage of the experimental protocol, it will still help boost the page loading times of Internet Explorer users, who are unable to currently take advantage of SPDY. So you can see it does make a difference. Now, whether or not you will have the same results with Google's PageSpeed service (not web server module), I don't know.

However, aside from the raw page loading speed differences, PageSpeed also offers filters to improve the user experience on your website. With filters such as deferring Javascript and lazyloading images automatically, it can make your site feel faster and more responsive to the end user.

Posted

Well, it's worth noting that the PageSpeed module for NGiNX is defnitely not ready for production use.

I did some production tests moments earlier, and the module is unable to copy under heavy load. You'll constantly get errors that the server returns an empty response.

It's an alpha module though, so it's nothing surprising and nothing to blame on anyone. Just noting my results here for anyone else that might be insane enough to try. :P

The PageSpeed module for Apache, however, is likely fine to use. I haven't tested it in a long while, but I remember it had serious problems with the image filters at one point, but that was maybe a year or so ago. It's likely stable enough for production use now. I'd still recommend being careful with some of the filters though.

No opinions on the PageSpeed service. If you give it a try, feel free to share your results! I'm a little curious as well, even though I know I won't be using it.

  • 2 weeks later...
Posted

In the rewriter "Prioritize Content", did you set "Cache and prioritize visible content"?

Wiht that enabled the site is faster, but this problem happens: "some users are seeing admin panels or personalized content for other users, your specification of non-cacheable portions is incomplete. You need to mark those portions as non-cacheable."

How did you fix it?

  • 2 weeks later...
Posted

I'm using Page Speed for a while now, and it's working pretty damn good. My hosting is GoDaddy - I know most of you hate them but I never went into problems.

The point is, in my case, the south part of Brazil have a really bad leading ISP, they have several problems when visiting international websites due to packet losses.

Google Page Speed fixed that problem, not to mention the load speed.

But since then my "quick edit" button on IPB doesn't work. It doesn't load the html editor.

Does anyone knows how to handle this?

Posted

Paulo could you tell us what your settings are with google pagespeed? I run into an issue where users are appearing as other people. Its very weird, but then after a refresh they show back as there original user.

Posted

I have no idea that is why I asked you. I dont know what "Non-Cacheable Parts" you would want to use. I disabled google pagespeed till I could find a way to fix that.

Posted

There's another issue about IPs. IPB always get the same IP for everyone when you're using pagespeed.

Yes, here is how to fix that:

System Settings > System > Security and Privacy

Enable X_FORWARDED_FOR IP matching

Set "Yes" and you will be good. The real IP will be shown.

Posted

In the rewriter "Prioritize Content", did you set "Cache and prioritize visible content"?

Wiht that enabled the site is faster, but this problem happens: "some users are seeing admin panels or personalized content for other users, your specification of non-cacheable portions is incomplete. You need to mark those portions as non-cacheable."

Ae9803,

You mean the one above? No, for that I had to set "Cache and prioritize visible content" OFF.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...