Web performance for LAMP developers (front end)

Web Performance for LAMP developers Sergey Chernyshev @SergeyChe

Performance? Why?User experience$$$ Money $$$• Shopzilla +7-12% conversions! & -50% operation costs• +15% (+60M) downloads for Firefox. (-1sec => +2.7% downloads)• Slowness is sticky (Google and Microsoft)SEO: Google uses sites speed in ranking

"Front-end"• Read waterfall diagrams• Measure users version of performance• Use browsers cache• "Compile" your web apps

Waterfalls

Metrics• TTFB• Time to load• Time to ﬁrst render• Above the Fold (AFT)• Your business metrics• Technical metrics (# of requests, page size, etc)

Quick wins! gzip (Apache conﬁguration)Browser Caching (Apache & PHP code)

gzipreduction of download time ~75% for text-based ~37% total

Use Browser CacheKnow your last updateNo download time is spent

Use Browser CacheNever expire speciﬁc URLUse update time as ﬁngerprint

Compile• Combine CSS and JavaScript• Minify CSS, JavaScript and even HTML• Optimize images• Version static / code URLs

Drop-in .htaccess

TrendsTrack your metrics over time

Web performance for LAMP developers (front end)

by Sergey Chernyshev on Aug 02, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Web performance for LAMP developers (front end) — Presentation Transcript