Remove 2017 Remove Google Remove Hardware Remove Traffic
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

How We Improved SmashingMag Performance

Smashing Magazine

After the latest redesign in late 2017, it was Ilya Pukhalski on the JavaScript side of things (part-time), Michael Riethmueller on the CSS side of things (a few hours a week), and yours truly, playing mind games with critical CSS and trying to juggle a few too many things. The performance distribution for Largest Contentful Paint in 2020.

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

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

Alex Russell

— Alex Russell (@slightlylate) October 4, 2017. Our metrics at Google show a conflicted picture (which I’m working to get to clarity on). We now have everything we need to create a ballpark perf budget for a product in 2017. Maybe "ambush by JS"? 75% of of connections occur on either 2G or 3G. First Load.

article thumbnail

Front-End Performance Checklist 2019 [PDF, Apple Pages, MS Word]

Smashing Magazine

For Mac OS, we can use Network Link Conditioner , for Windows Windows Traffic Shaper , for Linux netem , and for FreeBSD dummynet. On the other hand, we have hardware constraints on memory and CPU due to JavaScript parsing times (we’ll talk about them in detail later). Lighthouse , a performance auditing tool integrated into DevTools.