incubator-pagespeed-ngx

I believe the project is not maintained anymore. Github repository is archived: https://github.com/apache/incubator-pagespeed-ngx. Or has it perhaps moved to some other location?

Confusingly the project is still promoted at https://developers.google.com/speed but both of the linked GitHub repositories are now retired “due to inactivity”: - https://github.com/apache/incubator-pagespeed-mod - https://github.com/apache/incubator-pagespeed-ngx

I use the ngx_pagespeed module for Nginx for automatic image optimization. It's really good and easy to install: https://github.com/pagespeed/ngx_pagespeed I describe the whole setup step by step on my blog: https://blog.tjl.rocks/cheap-secure-and-fast-ghost-blog-set-...

Piotr is working his magic for ngx_pagespeed 1.10 https://github.com/pagespeed/ngx_pagespeed/issues/1114 just need a patch for 1.9 branch too

Cool. We're working now to make this possible. (And, in fact, to work at all when compiling against 1.9.11, since the addition of dynamic modules broke us: https://github.com/pagespeed/ngx_pagespeed/issues/1110 )

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"

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 orig

I'm curious if a lot of the customizations re:compression could be similarly achieved if the author used Google's modpagespeed for apache[0] or nginx[1], as it does a lot of these things automatically including eliding css/html attributes and generally re-arranging things for optimal sizes. It could make writing for 4k less of a chore? In any case, this is an outstanding hack. The company I work for has TLS certificates that are larger than the payload of his page. Absolutely terrific job, Daniel. [0]: https://code.google.com/p/modpagespeed/ [1]: https://github.com/pagespeed/ngx_pagespeed edit: formatting

A quick look shows that you could minify the Javascript quite a bit more (which is relatively easy, and would save a lot more than 50 bytes). You might also look at inlining all of the Javascript into the HTML directly (this is what Google does), which saves the extra HTTP requests. You could also do this with some of the persistent images on the page (logo) and inline them with base64 (but I don't think it actually helps with the page size). Finally, instead of using the browser extensions (which are helpful), get actual PageSpeed installed on the servers! Apache: https://developers.google.com/speed/pagespeed/module nginx: https://github.com/pagespeed/ngx_pagespeed Regardless, awesome stuff. Big fan. Much love.

I work on open source software on a team that doesn't handle any user data. [1] When people on other teams talk about data deletion they talk about having to make sure that when a user deletes something it really does get deleted from everywhere. I spent a couple minutes searching for a Google blog post explaining how this works and didn't find one, so rather than overpromise I just left it as "my impression". [1] https://github.com/pagespeed/ngx_pagespeed

Also useful for nginx: adding the pagespeed module https://github.com/pagespeed/ngx_pagespeed "ngx_pagespeed speeds up your site and reduces page load time by automatically applying web performance best practices to pages and associated assets (CSS, JavaScript, images) without requiring you to modify your existing content or workflow."

I applied to work at Google, got hired, and was matched to the PageSpeed team. Now I work on https://github.com/pagespeed/ngx_pagespeed It's nice working on free software, but I'd really be just as happy if I'd ended up in a different part of the company.