njakobsen commented on issue #1574: prioritize_critical_css 5 minutes
clarification
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1574#issuecomment-400820969
Thanks for all your help @oschaaf!
This is an
njakobsen commented on issue #1574: prioritize_critical_css 5 minutes
clarification
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1574#issuecomment-400814920
Ha! Posted that 14 seconds before you :)
This is
njakobsen commented on issue #1574: prioritize_critical_css 5 minutes
clarification
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1574#issuecomment-400814633
What I was hoping to get clarification on was when a Pagespeed cache entry
is stale, is there a reason it _must_
njakobsen commented on issue #1574: prioritize_critical_css 5 minutes
clarification
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1574#issuecomment-400812125
We have a mix of high traffic and low traffic pages. We are trying to boost
the perceived speed for users, as
njakobsen commented on issue #1574: prioritize_critical_css 5 minutes
clarification
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1574#issuecomment-400802823
...and after the TTL it always deletes the optimization instead of checking
if the underlying page has actually
njakobsen commented on issue #1574: prioritize_critical_css 5 minutes
clarification
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1574#issuecomment-400787853
So changes to an underlying page that happen within the beacon timer do not
invalidate the Pagespeed cache? Only
