Integrate with PageSpeed about webfundamentals HOT 7 CLOSED

Perhaps related to this issue, I noticed that one low-hanging fruit to improve the site's performance would be to correctly handle and serve static assets with 304 response codes.

As an example – load https://developers.google.com/web/fundamentals/css/styles.min.css in a browser, open up the devtools, and refresh. Instead of serving a 200, ideally you'd serve a 304 (if my browser sent the right If-None-Match header). Of course, this would speed up the experience a bit for small assets and a bunch for larger assets. And would particularly help over slow connections. :)

I assume PageSpeed would handle this for you if configured correctly, though it may be easier to implement this directly in your app. :)

from webfundamentals.

@PaulKinlan this sounds like two issues. Do we want to split into two?

from webfundamentals.

The issue @jeremydw mentions is #14 - I am not sure how the infrastructure handles caching...

from webfundamentals.

It's probably two issues, but integrating with PageSpeed will "kill two birds with one stone", depending on the PageSpeed config you use.

AFAIK, since PageSpeed serves as a proxy for your page's resources, even if the serving infrastructure doesn't handle caching/304s for your assets, since PageSpeed proxies all your page's resources (like the styles.min.css file that I mentioned, etc.) – the PageSpeed service will allow you to leverage caching for everything except the HTML files themselves (again, according to my experience using PSS).

from webfundamentals.

Is there any reason why we aren't using filerev in the grunt step?

If we enabled it we could probably extend the expiration?

from webfundamentals.

We don't have access to changing these on devsite.

On 12 June 2014 17:23, Matthew Gaunt [email protected] wrote:

Is there any reason why we aren't using filerev in the grunt step?

If we enabled it we could probably extend the expiration?

—
Reply to this email directly or view it on GitHub
#12 (comment)
.

from webfundamentals.

closing as we don't have access to change this :(

from webfundamentals.