Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Site-Speed That Sticks
Search
Harry Roberts
November 14, 2024
Technology
9
620
Site-Speed That Sticks
Harry Roberts
November 14, 2024
Tweet
Share
More Decks by Harry Roberts
See All by Harry Roberts
How to Think Like a Performance Engineer
csswizardry
24
1.7k
cache rules everything
csswizardry
5
3.4k
My Website Is Slow! Where Do I Start?
csswizardry
5
470
Optimising Largest Contentful Paint
csswizardry
37
3.3k
Get Your Head Straight
csswizardry
15
20k
From Milliseconds to Millions: A Look at the Numbers Powering Web Performance
csswizardry
1
2.5k
More Than You Ever Wanted to Know About Resource Hints
csswizardry
6
9.3k
It’s My (Third) Party, and I’ll Cry if I Want To
csswizardry
13
5.5k
FaCSSt: CSS & Performance
csswizardry
26
4.1k
Other Decks in Technology
See All in Technology
データ戦略部門 紹介資料
sansan33
PRO
1
3.1k
組織とセキュリティ文化と、自分の一歩
maimyyym
3
1.4k
impressions-trying-lambda-web-adapter
junkishigaki
2
140
名刺メーカーDevグループ 紹介資料
sansan33
PRO
0
760
Digitization部 紹介資料
sansan33
PRO
1
4k
kintone開発組織のDevOpsへの移り変わりと実践
ueokande
1
280
TypeScript をより型安全に扱うプラクティス #TSKaigi #TSKaigi2025_kataritai
bengo4com
0
2.1k
バクラクのモノレポにおける AI Coding のための環境整備と {Roo,Claude} Code活用事例 / AI Coding in Bakuraku's Monorepo: Environment Setup & Case Studies with {Roo, Claude} Code
upamune
7
2.7k
Java 30周年記念! Javaの30年をふりかえる
skrb
4
2.7k
libsyncrpcってなに?
uhyo
0
240
dbt Cloudの新機能を紹介!データエンジニアリングの民主化:GUIで操作、SQLで管理する新時代のdbt Cloud
sagara
0
110
Sansan Engineering Unit 紹介資料
sansan33
PRO
1
2k
Featured
See All Featured
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
123
52k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
KATA
mclloyd
29
14k
Bash Introduction
62gerente
614
210k
Automating Front-end Workflow
addyosmani
1370
200k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
180
53k
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
32
5.8k
Code Reviewing Like a Champion
maltzj
524
40k
The Cost Of JavaScript in 2023
addyosmani
49
8.3k
BBQ
matthewcrist
89
9.7k
Unsuck your backbone
ammeep
671
58k
Stop Working from a Prison Cell
hatefulcrawdad
269
20k
Transcript
site-speed that sticks
None
hi, i’m harry
None
five key topics
1. metrics 2. localhost 3. backstops 4. monitoring 5. playbook
1. metrics 2. localhost 3. backstops 4. monitoring 5. playbook
1. metrics 2. localhost 3. backstops 4. monitoring 5. playbook
1. metrics 2. localhost 3. backstops 4. monitoring 5. playbook
1. metrics 2. localhost 3. backstops 4. monitoring 5. playbook
1. metrics 2. localhost 3. backstops 4. monitoring 5. playbook
metrics
not all metrics are born equal
different metrics for different people on different occasions with different
levels of disclosure
kpis, enablers, predictors
kpis
definition + target
what are we working toward?
of interest to the business
core web vitals
‘which number on which dashboard of which service?’
“We want a one-second improvement in Largest Contentful Paint.” —
My Client
None
None
None
enablers
metrics that directly influence kpis
of interest to engineering teams
ttfb, input delay
predictors
signals of good/bad performance
highly quantitative
of interest to engineers
bundle size, long tasks, blocking css
great for root-causing and reverse engineering
localhost
localhost is: seldom live-like, pretty dang fast, un-bundled
know your tools inside out
None
None
csswz.it/perfnow25
one weird trick…
None
// plugins/delay.server.ts export default defineNuxtPlugin(async () => { await new
Promise(resolve => setTimeout(resolve, 900)) })
None
None
<head> <link rel=stylesheet href=https://slowfil.es/file?type=css&delay=800> </head>
core web vitals are too big for localhost
if you’re working locally, measure locally
bare-metal metrics
None
None
1
1 2
1 2 3
1 2 3
None
None
1
1 2
1 2 3
1 2 3
external: 1842ms inlined: 1250ms
None
these are very private metrics
backstops
…and budgets
what is the worst possible performance we will accept?
set it to the worst reading in the last release
cycle
None
this is where synthetic testing comes into it
synthetic testing; real user monitoring
when to fail a release
None
predictors as tripwires
None
budgets versus targets
budgets are backstops; targets are ambitions
target == kpi
None
monitoring
the m in rum stands for monitoring
“Insanity is doing the same thing over and over again
and expecting different results.” — Rita Mae Brown
None
🎉
?
None
None
None
None
it’s the exact same file
None
you’re monitoring variation in tests
None
only alert on your kpis
None
None
0.9952409649
None
None
always follow the numbers
playbook
“Fighting regressions took priority over optimizations […]” — Michelle Vu,
Pinterest
None
it’s all for nothing if you don’t have a plan
response = f(severity, duration)
severity
acceptable: <10%
moderate: 10–25%
severe: 25–50%
critical: >50%
duration
temporary: 24–48hr
sustained: >48hr
long-term: >1 release cycle
unresolved: many release cycles
a kpi regression of over 10% for one week requires
remediation in the next sprint
a kpi regression of over 100% for one hour requires
rollback immediately
a kpi regression of over 25% for one day requires
remediation in the current sprint
an enabler regression of over any% for any time needs
the team’s attention over the next sprint
a predictor regression of over any% for any time needs
my attention over the next sprint
you need a framework to fill in these blanks
early triage
who, what, when, where, and why?
what?
what has regressed?
when?
when did it start? is it still like that?
where?
is it a business-critical part of the site?
who?
who owns the problem?
why?
can you conduct early triage?
None
None
None
None
None
None
key takeaways
increase confidence
use the right tool for the right job
have a plan of attack
agree; commit
thank you
harry.is/for-hire