Remove 2017 Remove Benchmarking Remove Google Remove Hardware
article thumbnail

The Performance Inequality Gap, 2021

Alex Russell

TL;DR: A lot has changed since 2017 when we last estimated a global baseline resource per-page resource budget of 130-170KiB. To update our global baseline from 2017, we want to update our priors on a few dimensions: The evolved device landscape. Hardware Past As Performance Prologue. The Moto G4 , for example. Hard Reset.

article thumbnail

Progress Delayed Is Progress Denied

Alex Russell

As an engineer on a browser team, I'm privy to the blow-by-blow of various performance projects, benchmark fire drills, and the ways performance marketing (deeply) impacts engineering priorities. With each team, benchmarks lost are understood as bugs. WebGL 2 launched for other platforms on Chrome and Firefox in 2017.

Media 145
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

The Performance Inequality Gap, 2024

Alex Russell

HTML, CSS, images, and fonts can all be parsed and run at near wire speeds on low-end hardware, but JavaScript is at least three times more expensive, byte-for-byte. decoding="async" loading="lazy" /> Google spent more on the SoC for the Pixel 4a and enjoyed a later launch date, boosting performance relative to the A51.

article thumbnail

Can You Afford It?: Real-world Web Performance Budgets

Alex Russell

— Alex Russell (@slightlylate) October 4, 2017. Budgets are scaled to a benchmark network & device. Deciding what benchmark to use for a performance budget is crucial. Our metrics at Google show a conflicted picture (which I’m working to get to clarity on). Maybe "ambush by JS"?