Your SlideShare is downloading. ×
0
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Optimising your web application
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Optimising your web application

481

Published on

Praveen Umanath, Product Manager at BigRock conducts a session on how to optimise web applications at httpX 2013, New Delhi

Praveen Umanath, Product Manager at BigRock conducts a session on how to optimise web applications at httpX 2013, New Delhi

Published in: Technology, Design
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
481
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Optimizing your Web Application
  • 2. But Why? • 47% of consumers expect a web page to load in 2 seconds or less. • 40% of people abandon a website that takes more than 3 seconds to load. • A 1 second delay in page response can result in a 7% reduction in conversions. *Source = http://blog.kissmetrics.com/loading-time/
  • 3. Two Sides to Optimization Increase Speed Reduce Errors
  • 4. Alright , lets get cracking
  • 5. Not so fast there, buster…
  • 6. First, we need to monitor
  • 7. Application and Website Monitoring
  • 8. NewRelic “Real User Monitoring”
  • 9. What makes up Page Load Time? • Request queuing – wait time between App and Web Server • Network – Latency/Round trip time • Web Application – time spent in application code • DOM – parsing and interpreting HTML • Page Rendering – displaying HTML, inline JS and images
  • 10. Capturing Errors
  • 11. JavaScript - ErrorCeption
  • 12. PHP - NewRelic
  • 13. Functional Tests • We’ve implemented over 50 functional tests using watir def search_for(domain) @watir.text_field(:id => 'field_domains-input').set(domain) @watir.span(:class => 'tlds-dd').click @watir.button(:id => 'go_btn').clickswitch_to :search_results_page end
  • 14. I feel the need…the need for Speed!
  • 15. Serve Resources from sub-domains *Source = StackOverFlow - http://stackoverflow.com/questions/11185618/whats-themaximum-number-of-simultaneous-connections-a-browser-will-make
  • 16. Mod_pagespeed • The best thing since sliced bread! • Open source module made available by Google • Works with Apache • Contains 40+ optimization filters which can be switched on/off
  • 17. Mod_pagespeed • The best thing since sliced bread! ModPagespeedEnableFiltersmove_css_to_head,combine_c ss,rewrite_css,fallback_rewrite_css_urls ModPagespeedEnableFiltersrewrite_javascript,inline_ css,inline_javascript,rewrite_images,convert_jpeg_t o_progressive • https://developers.google.com/speed/
  • 18. And One more thing…

×