~/talk

Stop Guessing: Diagnosing & Fixing WordPress Performance Problems

Talkat WordCamp Seattle 2018 · 2018-11-10..11-11· [wordpress, web-performance]
links:none on file
slides:none on file

Concrete steps to stop guessing: measure your time to first byte (goal under 500 ms, ideal 50–150 ms) with WebPageTest and Chrome DevTools, profile PHP/WordPress with New Relic to find slow plugins or hooks (example: a Jetpack hook adds ~2 seconds), optimize images and HTTP/2, and only use page caching as a last resort. Migrating to a faster host can yield dramatic wins (one example becomes 5× faster with no code changes). Tools shown include a TTFB scanner, migration plugins, and automated site crawls.

AI-written summary · about

  1. 0:00Introduction and speaker background
  2. 2:32Why performance matters
  3. 7:46Measuring time to first byte
  4. 13:48Hosting providers impact on speed
  5. 18:17Migrating to optimized hosting
  6. 24:13Diagnosing server response time
  7. 29:41Profiling WordPress with New Relic
  8. 31:25Optimizing page loads beyond TTFB
  9. 35:02Understanding caching types
  10. 37:10Summary and final recommendations
  11. 37:54Live demo of performance tools
  12. 42:49Q&A session
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.