Why Your Site is Slow
summary
Site slowness traces to concrete causes: uncacheable HTML because of varnish misses driven by poor cache-control headers and lacking block-level metadata; expensive backend work (examples: Redis + entity cache reduce repeated node loads, one homepage once ran 1,000 queries on a homepage); heavy front-end assets and third‑party widgets blocking parsing. Tools and fixes used include Drupal 8 cache metadata, New Relic for per-deploy profiling, Chrome devtools and Web Profiler, and BigPipe to stream main HTML quickly — most fixes require changing architecture or org decisions, not magic.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:38Making a website
- 2:09Clients and servers
- 2:49What a website does
- 5:06What does Varnish do?
- 6:29Varnish relies on HTTP headers
- 7:22Drupal core settings
- 11:00Cache metadata in render arrays
- 12:39Solved problems
- 15:02Web Profiler in Drupal 8
- 16:34Caching, caching, caching
- 17:32Views module: A leaky abstraction
- 18:56Turn on the timer!
- 21:28Can you have too many modules?
- 22:53Treat "slow" like a bug
- 25:38What's on the agenda?
- 26:56Look behind the numbers
- 28:31Delete CSS with confidence
- 30:48Attach libraries to render arrays
- 32:55Where is the decision implemented?
- 38:38When you're in a meeting do you...
- 40:00AMP: history repeating
- 40:41Going with the flow - 2016
- 42:18Solving the problem of too many features... with another feature
- 42:29Feature creep finds a way
- 43:09How quickly can you get to a usable site?
- 44:18You are moving in the right direction when...
