Book Image

Mobile Web Performance Optimization

By : S. S. Niranga
Book Image

Mobile Web Performance Optimization

By: S. S. Niranga

Overview of this book

With users increasingly accessing the web on mobile devices, it’s crucial to make sure your website is built to seamlessly fit this radical change in user behavior. Mobile Web Performance Optimization is designed to help you do exactly that – it’s been created to help you build fast, and mobile-user-friendly websites and applications. Featuring guidance through a range of techniques and tools essential to modern mobile development, this accessible guide will make sure you’re delivering a seamless and intuitive experience for your website’s users. Begin by exploring the fundamental components of mobile web design and website optimization, before learning how to put the concepts into practice. Featuring cross-platform solutions, insights on developing lightweight yet robust UI, and insights on how to successfully manage data, this application development book takes you through every stage in the development process – so you can be confident that you’re asking the right questions and using the best tools in the most effective way. By the end, you’ll understand implicitly what it means to ‘build for performance’- you’ll be a more confident developer, capable of building projects that adapt to a changing world.
Table of Contents (14 chapters)
Mobile Web Performance Optimization
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

HTTP 300, 400, and 500 codes


If you get a 3XX class of HTTP status code, it means that the user agent needs to take some additional actions to fulfill the request. The required action is fulfilled by the user agent without any involvement of the user, if and only if, the method used in the second request is HEAD or GET. A client needs to detect infinite redirection loops in the website because for each redirection, it will generate network traffic.

  • Receiving an HTTP 301 status code: An HTTP 301 status code specifies that requested resources by the user have permanently moved to another location. The HTTP response that carries this code needs to also include the new location, and the client should use this new URL the next time they try to get the same resource. If it's possible, a client needs to update all references to the requested URL when an HTTP 301 status code pops up.

  • Receiving an HTTP 302 status code: An HTTP 302 status code specifies that requested resources by the user have temporarily...