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
13
1.1k
Site-Speed That Sticks
Harry Roberts
November 14, 2024
Tweet
Share
More Decks by Harry Roberts
See All by Harry Roberts
Build for the Web, Build on the Web, Build With the Web
csswizardry
0
220
How to Think Like a Performance Engineer
csswizardry
28
2.5k
cache rules everything
csswizardry
5
3.7k
My Website Is Slow! Where Do I Start?
csswizardry
5
560
Optimising Largest Contentful Paint
csswizardry
37
3.6k
Get Your Head Straight
csswizardry
15
21k
From Milliseconds to Millions: A Look at the Numbers Powering Web Performance
csswizardry
1
2.7k
More Than You Ever Wanted to Know About Resource Hints
csswizardry
6
9.8k
It’s My (Third) Party, and I’ll Cry if I Want To
csswizardry
13
5.8k
Other Decks in Technology
See All in Technology
マルチアカウント環境でSecurity Hubの運用!導入の苦労とポイント / JAWS DAYS 2026
genda
0
490
最強のAIエージェントを諦めたら品質が上がった話 / how quality improved after giving up on the strongest AI agent
kt2mikan
0
160
Yahoo!ショッピングのレコメンデーション・システムにおけるML実践の一例
lycorptech_jp
PRO
1
200
Claude Code 2026年 最新アップデート
oikon48
10
8.2k
クラウド × シリコンの Mashup - AWS チップ開発で広がる AI 基盤の選択肢
htokoyo
2
180
PMBOK第8版は第7版から何が変わったのか(PMBOK第8版概要解説) / 20260304 Takeshi Watarai
shift_evolve
PRO
0
200
マルチロールEMが実践する「組織のレジリエンス」を高めるための組織構造と人材配置戦略
coconala_engineer
3
720
Scrumは歪む — 組織設計の原理原則
dashi
0
130
AIエージェント時代に備える AWS Organizations とアカウント設計
kossykinto
3
790
「ストレッチゾーンに挑戦し続ける」ことって難しくないですか? メンバーの持続的成長を支えるEMの環境設計
sansantech
PRO
3
650
8万デプロイ
iwamot
PRO
2
230
JAWS DAYS 2026 楽しく学ぼう!ストレージ 入門
yoshiki0705
2
150
Featured
See All Featured
Docker and Python
trallard
47
3.8k
Navigating Team Friction
lara
192
16k
WCS-LA-2024
lcolladotor
0
480
Heart Work Chapter 1 - Part 1
lfama
PRO
5
35k
Automating Front-end Workflow
addyosmani
1370
200k
GraphQLの誤解/rethinking-graphql
sonatard
75
11k
JAMstack: Web Apps at Ludicrous Speed - All Things Open 2022
reverentgeek
1
390
Java REST API Framework Comparison - PWX 2021
mraible
34
9.2k
Noah Learner - AI + Me: how we built a GSC Bulk Export data pipeline
techseoconnect
PRO
0
130
技術選定の審美眼(2025年版) / Understanding the Spiral of Technologies 2025 edition
twada
PRO
118
110k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
35
2.4k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
54k
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