Comment by jdmarantz | Hacker News Reader

Comment by jdmarantz | Hacker News Reader

Hello from the PageSpeed team.

Image compression and device-sensitive transcoding are important for mobile and emerging markets, and are somewhat challenging to deploy on your own. For larger sites we acknowledge there is some tuning & thought that must be applied, and we'd be happy to help via the discussion groups (mod-pagespeed-discuss, ngx-pagespeed-discuss). We are also working on a new release that will make this easier. For smaller sites, things should work out of the box. As with all PageSpeed issues, please let us know if they don't, or you think there's something specific to improve.

We've heard user concerns about SEO, and are happy to report that this should be improved with our latest beta release (1.0), which adds 'link canonical' attributes to image response headers. This allows search engines to point back to the origin image.

Please give us a shout on our discussion group or bug-list and we'll try to help sort through any others issues that you see: https://github.com/pagespeed/ngx_pagespeed/issues?q=is%3Aope...

its really tricky for people to figure out how to build this and deploy it production.

I have a nginx build script with pagespeed that I use for my docker images. I dont think I leverage pagespeed enough - it would be great if you could point out what needs to change (and others could learn from it)

https://gist.github.com/redcarpetup/e52cbddb907effe70bd0

EDIT: in fact that the first bug I see on your bug list is https://github.com/pagespeed/ngx_pagespeed/issues/1106 "Nginx cannot find module when building inside Docker container"

Better yet, an nginx .deb repo with pagespeed already compiled in. Like the one nginx provides[1].

I'm very reluctant to use anything that doesn't come packaged. Compiling your own software only really works when you're constantly maintaining the same project and its stack. In every other situation, it's a hassle, and I always fall behind.

[1] http://nginx.org/en/linux_packages.html

hey jdmarantz love ngx_pagespeed been using it for years now integrating into my Centmin Mod LEMP stack installer's Nginx server http://centminmod.com/nginx_ngx_pagespeed.html. The benefits of ngx_pagespeed are truly amazing :)

How much do you think of this is nowadays obsolete (or let's say: Less important) with HTTP-2? I'm using pagespeed with Openresty.

not obsolete at all I benchmarked http/2 vs http/2 + ngx_pagespeed and the http/2 + ngx_pagespeed is still faster http://centminmod.com/http2-versus-spdy-nginx.html#http2vers...

if you think about it, http/2 allows requests over one tcp connection but each page element is still around the same size.

ngx_pagespeed can optimise those page elements css/js and reduce image sizes i.e. png to webp conversion on the fly so each page element is smaller in size.

Utlimately reducing the size of each page element = smaller data transfers = faster page loads :)

I'm also using Google's ngx_brotli https://github.com/google/ngx_brotli + ngx_pagespeed for even better performance https://community.centminmod.com/threads/brotli-compression-...

Reply on news.ycombinator.com