noahcollins

My team's approach has been to automate real devices and report on any regressions in terms of JavaScript evaluation, layout, paint, garbage collection, etc. Shameless plug: the team is growing and we're hiring an experienced front-end dev. https://nordstrom.taleo.net/careersection/2m/jobdetail.ftl?j...

Nordstrom | Multiple positions | Seattle, WA | Full-Time | Onsite | $100-$150k

Join the Nordstrom.com Web Performance Team! We believe that with our talented engineers, smart technology, and passionate customers we can deliver the best retail experience on the web. We’re looking for UI, Fullstack, & Node engineers to help us re-architect and refine our customer-facing UIs and supporting services. If it has performance impact, we care about it. You’ll enhance our existing applications and help drive the future direction of the stack and architecture that powers nordstrom.com.

UI Engineer https://nordstrom.taleo.net/careersection/2/jobdetail.ftl?jo...

Node.js Engineer https://nordstrom.taleo.net/careersection/2/jobdetail.ftl?jo...

Interesting note on the impact of image size variation on queue, thanks for elaborating.

Serving those resources from the 99designs domain is worth a look. I considered the cookies and security trade offs as well. I found H2 compressed cookies enough to perform better than a separate cookieless domain for static assets, due to the DNS savings. DNS times can be bad at high percentiles. Reflected XSS addressed with a Content Security Policy. But I'm fortunate to have user base that supports CSP well.

Good point if you're using push for page content that varies, like images in the the 99designs portfolio and gallery. That gets into dynamic caching territory.

As a first step, I'm focused on using push to cut latency between TTFB and processing of render-blocking static assets. Serving those from same domain as the base page, it should be easy for origin to supply edge with the list of resources push. Either in the HTML or with the `link` response header. It also means my critical assets are not longer behind a separate DNS lookup.

In the design gallery, this type of push approach could help you regain control of loading priority and get your fonts loading before that wall of images.

Thanks for posting your findings - very useful data. It would be interesting to see the Webpagetest waterfalls in greater detail if you're able to share that.

You planning to use your resource hints to enable server push at CDN edge?