--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ngx-pagespeed-discuss/c57b8a84-a8a4-4056-93bd-5f3dd4c0d41e%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ngx-pagespeed-discuss/c57b8a84-a8a4-4056-93bd-5f3dd4c0d41e%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ngx-pagespeed-discuss/3e12bccc-01ac-40fe-a569-bc9efc0830b1%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ngx-pagespeed-discuss/d4721018-d48f-4a50-811c-9abc4628559b%40googlegroups.com.
I agree -- Chromium headless sounds like the way to go...I was not aware that was now an installable product. You would still need to get it to run in all the modes you want pre-optimized for your users. For example, if you are using responsive images you'd need it to run at all the required resolution breakpoints. It's not a very easy path.
On Thu, Apr 16, 2020 at 5:43 AM Longinos <longinos.in...@gmail.com> wrote:
--Chromium headless is like Google Chrome but w/o any user interface.The rpm provides an executable (headless_shell), this executable have a bunch of parameters, to set the size of viewport, to se the UA string, to create a image from the fetched url, to execute the javascript, to save to a file the dom.....The rpm is a Fedora project, but maybe there is a deb package./usr/lib64/chromium-browser/headless_shell --disable-translate --disable-background-networking --safebrowsing-disable-auto-update --disable-sync --disable-default-apps --disable-software-r
asterizer --single_process --disable-features --disable-extensions --disable-setuid-sandbox --no-sandbox --disable-gpu --tls1.3 --window-size=412,732 --enable-ipv6 --user-agen
t="USER AGENT STRING" --disable-features=NetworkService --enable-tcp-fast-open --disable-zygote https://URL_TO_FETCHThis a example.Mos of the parameters are the same from chrome executed in a command line.
El jueves, 16 de abril de 2020, 8:32:50 (UTC+2), Krunal Jariwala escribió:Can you share, how does this work?
On Thursday, 16 April 2020 01:12:02 UTC+5:30, Longinos wrote:HiAn other option to warm the pagespeed cache is using chromium headles. Almost for Centos distro you can find rpm to install it from the EPEL repo.(chromium-headless)Chromium headless execute the javascript and the beaconing works and have a parameter to change the UA.
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.