View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
Change behavior to influence perceptionPercieved Performance: Actual Performance:Responsive ● Optimize● Feedback ● Cache● Progressive ● Minimize● Escape or Distract ● Workflow● Describe
Low hanging fruit for WordPress:● Frontend ○ Minimize ○ Sprites● Caching ○ Asset delivery ○ Chunking● Application ○ Theme ○ Plugins● Server Setups ○ OS choice & tweaking
Battle of the brawn● Process based ● Event based● Req increase RAM ● RAM use is stable● Gobs of features ● Speed > features● More use cases ● no .htaccessLike Apache, Nginx has all the features youwould expect from a leading Web server. It isstable, secure and very easy to configure.
Real world comparisons: 9794 req/5 min 32 req/second Only site on fresh VPS install, with minimal graphics, scripts, css. 17479 req/5 min 60 req/second One of several sites on VPS, photographer portofolio, heavyStress tests by http://loadimpact.com graphics, minimal scripts & css.
Caching with static content + CDNPlugins: Benefit:● W3TC ● At least 10x improvement in site● WP Super Cache performance● Hyper Cache ● “Instant” second page● DB Cache Reloaded views ● Reduced page load time ● Improved web serverCDN: performance● Amazon S3 & ● Up to 80% Bandwidth Cloudfront savings
W3 Total Cache (setup walkthrough)1. Sign-up for Amazon S3 & Cloudfront2. Install W3 Total Cache Plugin within WordPress3. Follow W3 Total Cache Instructions within WordPress admin panel4. Log in to Cloudfront control panel and create a Distribution for your newly created bucked
CDN explained & expoundedA content delivery network or contentdistribution network (CDN) is a system ofcomputers containing copies of data placed atvarious nodes of a network.* The optimal number is somewhere between 1 and 5 hosts (1 main host plus 4hosts on which to parallelize cacheable resources). As a rule of thumb, youshouldnt use more than 1 host for fewer than 6 resources; fewer than 2resources on a single host is especially wasteful. It should never be necessaryto use more than 5 hosts (not counting hosts serving resources over which youhave no control, such as ads). (source: Google Page Speed)
What did we learn?● Build on a good foundation● Pull the weeds of unnecessary code● Optimize browser rendering● Minimize request overhead● Minimize round-trip times● Minimize payload size● Optimize caching● Change perception