Tweet
Tweet

Slide 1

Slide 1 text

Breaking news at 1000ms @patrickhamann - Velocity EU - November 2014

Slide 2

Slide 2 text

theguardian.com

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

next.theguardian.com

Slide 5

Slide 5 text

110million !

Slide 6

Slide 6 text

" # $ 7000

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

Maslow's hierarchy of user needs ! % & ' We surveyed 3000 users About 17 key product drivers They rated speed 2nd most important Only after easy to find content

Slide 10

Slide 10 text

Time & user perception Delay User perception 0–100 ms Instant 100–300 ms Small perceptible delay 300–1000 ms Machine is working 1,000+ ms Likely mental context switch 10,000+ ms Task is abandoned Source: Ilya Grigorik – High-Performance Browser Networking

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

1000ms

Slide 13

Slide 13 text

A performance budget https://flic.kr/p/iQ69Kg

Slide 14

Slide 14 text

Setting a budget https://flic.kr/p/eHsirY

Slide 15

Slide 15 text

1. Core content should be delivered first 2. Core content should render within 1000ms 3. Every feature must fail gracefully 4. Every request should be measured

Slide 16

Slide 16 text

1. Core content should be delivered first 2. Core content should render within 1000ms 3. Every feature must fail gracefully 4. Every request should be measured

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

User Content API Popular Comments Article DB DB

Slide 19

Slide 19 text

https://flic.kr/p/77ZtUH

Slide 20

Slide 20 text

User Content API Popular Comments Article DB DB

Slide 21

Slide 21 text

Final progressively enhanced page Initial page payload

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

1. Core content should be delivered first 2. Core content should render within 1000ms 3. Every feature must fail gracefully 4. Every request should be measured

Slide 25

Slide 25 text

Browser rendering 101

Slide 26

Slide 26 text

Source: Google - Pagespeed Insights

Slide 27

Slide 27 text

Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM

Slide 28

Slide 28 text

Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM DOM

Slide 29

Slide 29 text

Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM DOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM

Slide 30

Slide 30 text

Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM DOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint DOM CSS CSSOM

Slide 31

Slide 31 text

Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM DOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM Network JavaScript Render tree Layout Paint HTML DOM CSS CSSOM

Slide 32

Slide 32 text

Request page Network Render GET html Build DOM response Build CSSOM Render page GET css GET js response response idle idle Async Render blocking Run JS Source: Google - Web Fundamentals

Slide 33

Slide 33 text

Request page Network Render GET html Build DOM response Build CSSOM Render page GET css GET js response response idle idle Async Render blocking Run JS

Slide 34

Slide 34 text

JS CSS HTML CSS & JS § HTML async DOMContentReady Start render

Slide 35

Slide 35 text

Get the CSS down as soon as possible.

Slide 36

Slide 36 text

What is your critical CSS?

Slide 37

Slide 37 text

Popular content ✘ Sharing ✘ Comments ✘ Related content ✘ Commercial components ✘ Article ✔

Slide 38

Slide 38 text

What if we inlined our critical CSS?

Slide 39

Slide 39 text

Inline

Slide 40

Slide 40 text

WTF%$?!

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

0.0 0.1 0.2 0.3 0.0 0.1 0.2 0.3

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

localStorage

Slide 45

Slide 45 text

Is modern browser? Requet with Request with CSS in localStorage? localStorage space? Request with AJAX cache in localStorage inject into

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

Load time First byte Start render Visually complete 3.366s 0.204s 1.113s 3.700s Before Load time First byte Start render Visually complete 3.017s 0.262s 0.759s 2.00s After

Slide 50

Slide 50 text

Use MD5 hash for cache key WTF no stylesheets?

Slide 51

Slide 51 text

Cookie

Slide 52

Slide 52 text

Initial request HTML response with inline CSS Render page Request global CSS with AJAX Set cookie Initial request HTML response with default Render page Does request contain cookie?

Slide 53

Slide 53 text

https://github.com/addyosmani/critical http://ngxpagespeed.com/ Penthouse https://github.com/pocketjoso/penthouse

Slide 54

Slide 54 text

What does the future hold?

Slide 55

Slide 55 text

http/2

Slide 56

Slide 56 text

 ) HTML " ) CSS  " HTTP/1.1 * HTML & CSS  " HTTP/2 Server push

Slide 57

Slide 57 text

1. Core content should be delivered first 2. Core content should render within 1000ms 3. Every feature must fail gracefully 4. Every request should be measured

Slide 58

Slide 58 text

Story of my life

Slide 59

Slide 59 text

Font loading 101 IE Firefox WebKit Blink Blocking ✗ ✔ ✔ ✔ Timeout – 3s – – Source: Ian Feather – Web fonts and the Critical Path

Slide 60

Slide 60 text

guardian egyptian

Slide 61

Slide 61 text

progressive enhancement https://flic.kr/p/9RDXVd

Slide 62

Slide 62 text

Is modern browser? Requet with Show fallback? Support WOFF? localStorage space? Request with AJAX cache in localStorage inject into font in localStorage?

Slide 63

Slide 63 text

Example of base64 json’ifed fonts

Slide 64

Slide 64 text

service worker Webfontjson

Slide 65

Slide 65 text

What does the future hold?

Slide 66

Slide 66 text

Font load events

Slide 67

Slide 67 text

CSS font rendering

Slide 68

Slide 68 text

service worker ServiceWorker

Slide 69

Slide 69 text

ServiceWorker  " )  " ) )

Slide 70

Slide 70 text

1. Core content should be delivered first 2. Core content should render within 1000ms 3. Every feature must fail gracefully 4. Every request should be measured

Slide 71

Slide 71 text

WARNING!

Slide 72

Slide 72 text

assets radiator

Slide 73

Slide 73 text

R.U.M. (real user metrics)

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

speedcurve

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

What does the future hold?

Slide 80

Slide 80 text

Resource Timing

Slide 81

Slide 81 text

Beacon API

Slide 82

Slide 82 text

1. Core content should be delivered first 2. Core content should render within 1000ms 3. Every feature must fail gracefully 4. Every request should be measured

Slide 83

Slide 83 text

Takeaways

Slide 84

Slide 84 text

Everyone must be involved by baking performance into your workflow from day one.

Slide 85

Slide 85 text

Deliver core content first,
 then progressively enhance the extras.

Slide 86

Slide 86 text

Set a performance budget.
 Measure, optimise & repeat!

Slide 87

Slide 87 text

Performance is a requirement; not an extra feature.

Slide 88

Slide 88 text

Thank you. Questions? @patrickhamann - Velocity EU - November 2014 github.com/guardian/frontend +