pagespeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] jmarantz commented on issue #1543: Problem with pagespeed filters
Date Tue, 20 Mar 2018 17:54:18 GMT
jmarantz commented on issue #1543: Problem with pagespeed filters
   The trouble you are seeing is that PageSpeed does not consider it an error to serve unoptimized
content; as it's trying to optimize for end-user experience, based on an assumption that it's
faster for a client to receive an unoptimized resource than to wait for it to get optimized
on the server.
   In the same philosophy, a cache does not consider it an error to respond with a MISS if
an item previously inserted was evicted -- and these two concepts are related.
   There are, however, some things you can do to mitigate or eliminate the problem.  The one
I'd recommend is to tweak timeouts to make it very unlikely you'll see an unoptimized asset.
   Go ahead and set that to 10 minutes if you like :)  The default is 10 milliseconds.
   There's also a testing path to guarantee an optimized result, but it requires setting a
request header, which you won't be able to do in PageSpeed Insights, so I'm not going to go
down this road right now.
   The ImplicitCacheTttlMs helps avoid expiring resources out of cache, but doesn't guarantee
that they won't be evicted if the cache is too small.  So you just need to allocate enough
cache space.  Also that doesn't say anything about the first time an asset is seen.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message