Upgrade to Pro — share decks privately, control downloads, hide ads and more …

CSS and the critical path - CSSConf May 2014

Patrick Hamann
May 27, 2014
Programming
20
1.9k

CSS and the critical path - CSSConf May 2014

For a website to feel instant, a perceptible response to user input must be provided within hundreds of milliseconds.

This perceived speed of your website relies heavily on the browser being able to paint to your user’s screen. For this they must construct a “render tree” which consists of the DOM and the often forgotten CSSOM. The critical path which the browser takes to gather this information is the only thing standing between your server and the user’s screen.

Using new research and real world examples, Patrick Hamann will cover a range of techniques – from the controversial to bleeding edge – the Guardian are using to make the CSS of their next generation website load as fast as possible, and ultimately taking it off the critical path. Breaking the news to the user within 1000ms.

During the talk you will discover why performance matters, what are the common performance bottlenecks in the browser from networking to painting and learn how to best optimise and monitor each stage of the critical path to create fast loading websites.

Patrick Hamann

May 27, 2014
Tweet

More Decks by Patrick Hamann

See All by Patrick Hamann
CSS and the First Meaningful Paint - CSS Conf EU, May 2017
patrickhamann
15
2.2k
CSS and the First Meaningful Paint - All day Hey!, April 2017
patrickhamann
4
370
Embracing the Network — DIBI Conf, March 2016
patrickhamann
1
380
HTTP2 What, where, why, and when?! Smashing Conference, March 2016
patrickhamann
16
3.7k
Embracing the network - Web Directions
patrickhamann
4
1.4k
Embracing the network - Smashing Conf
patrickhamann
6
1.3k
Embracing the Network – ColdFront, September 2015
patrickhamann
36
4k
Building theguardian.com
patrickhamann
41
7k
Breaking news at 1000ms - Velocity EU 2014
patrickhamann
16
2.8k

Other Decks in Programming

See All in Programming
今年のアップデートで振り返るCDKセキュリティのシフトレフト/2024-cdk-security-shift-left
tomoki10
0
200
rails stats で紐解く ANDPAD のイマを支える技術たち
andpad
1
290
fs2-io を試してたらバグを見つけて直した話
chencmd
0
230
Scalaから始めるOpenFeature入門 / Scalaわいわい勉強会 #4
arthur1
1
330
快速入門可觀測性
blueswen
0
350
短期間での新規プロダクト開発における「コスパの良い」Goのテスト戦略」 / kamakura.go
n3xem
2
170
良いユニットテストを書こう
mototakatsu
7
2.2k
責務を分離するための例外設計 - PHPカンファレンス 2024
kajitack
1
650
StarlingMonkeyを触ってみた話 - 2024冬
syumai
3
270
アクターシステムに頼らずEvent Sourcingする方法について
j5ik2o
4
260
MCP with Cloudflare Workers
yusukebe
2
220
Webエンジニア主体のモバイルチームの 生産性を高く保つためにやったこと
igreenwood
0
330

Featured

See All Featured
4 Signs Your Business is Dying
shpigford
181
21k
Building Flexible Design Systems
yeseniaperezcruz
327
38k
A better future with KSS
kneath
238
17k
The World Runs on Bad Software
bkeepers
PRO
65
11k
Code Reviewing Like a Champion
maltzj
520
39k
The MySQL Ecosystem @ GitHub 2015
samlambert
250
12k
Measuring & Analyzing Core Web Vitals
bluesmoon
4
170
The Cult of Friendly URLs
andyhume
78
6.1k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
59k
GraphQLの誤解/rethinking-graphql
sonatard
67
10k
What’s in a name? Adding method to the madness
productmarketing
PRO
22
3.2k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
47
5.1k

Transcript

  1. CSS and the critical path @patrickhamann - CSSConf- May 2014

  2. next.theguardian.com

  3. 100million !

  4. " # $ 6000

  5. None

  6. 0 2.25 4.5 6.75 9 2000 2006 2009 2012 User

    load time expectations (Secs) User load time expectations are decreasing Source: Web Performance Today - March 2013

  7. 0 5000 10000 15000 20000 Jan Feb Mar Apr 10%

    Percentile Median 90% Percentile Average SpeedIndex top 10,000 websites Source: HTTPArchive - May 2014

  8. 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

  9. 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

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

  11. 1000ms

  12. Browser rendering 101

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

  14. HTTP (TTFB)
 DNS Lookup Content download Initial connection (Socket)

  15. Source: Google - Pagespeed Insights

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

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

    DOM

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

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

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

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

  22. JS CSS HTML CSS & JS § HTML async DOMContentReady

    Start render

  23. Get the CSS down as soon as possible.

  24. CSS and the critical path

  25. What is your critical CSS?

  26. Popular content ✘ Sharing ✘ Comments ✘ Related content ✘

    Commercial components ✘ Article ✔

  27. Final progressively enhanced page Initial page payload

  28. What if we inlined our critical CSS?

  29. Inline

  30. WTF%$?!

  31. None

  32. 0.9 1.0 1.1 0.9 1.0 1.1

  33. None

  34. localStorage

  35. Is modern browser? CSS in localStorage? Inject into <head> Request

    with <link> Request with AJAX localStorage space? Cache in localStorage
  36. None
  37. None
  38. None

  39. 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

  40. Use MD5 hash for cache key WTF no stylesheets?

  41. None

  42. Monitor

  43. assets radiator

  44. None

  45. speedcurve

  46. None

  47. Alternatives

  48. PageSpeed

  49. UnCSS & grunt-uncss

  50. Source: http://addyosmani.github.io/basket.js/ basket.js

  51. What does the future hold?

  52. http/2

  53.  ) HTML " ) CSS  " * HTML

    & CSS  " HTTP/1.1 HTTP/2 Server push

  54. service worker ServiceWorker

  55. ServiceWorker  " ) )

  56. Takeaways

  57. Inline critical CSS and defer all other non-critical assets to

    avoid render blocking.

  58. Where possible, cache aggressively in localStorage.

  59. Set a performance budget.
 Measure, optimise & repeat!

  60. Performance is a requirement; not a feature.

  61. Thank you. Questions? @patrickhamann - CSSConf - May 2014 g

    We’re hiring! github.com/guardian/frontend + bit.ly/css-and-the-critical-path +