Jump to content

Web performance

From Wikipedia, the free encyclopedia
(Redirected from Website performance)

Web performance refers to the speed in which web pages are downloaded and displayed on the user's web browser. Web performance optimization (WPO), or website optimization is the field of knowledge about increasing web performance.

Faster website download speeds have been shown to increase visitor retention and loyalty[1][2] and user satisfaction, especially for users with slow internet connections and those on mobile devices.[3] Web performance also leads to less data travelling across the web, which in turn lowers a website's power consumption and environmental impact.[4] Some aspects which can affect the speed of page load include browser/server cache, image optimization, and encryption (for example SSL), which can affect the time it takes for pages to render. The performance of the web page can be improved through techniques such as multi-layered cache, light weight design of presentation layer components and asynchronous communication with server side components.

History

[edit]

In the first decade or so of the web's existence, web performance improvement was focused mainly on optimizing website code and pushing hardware limitations. According to the 2002 book Web Performance Tuning by Patrick Killelea, some of the early techniques used were to use simple servlets or CGI, increase server memory, and look for packet loss and retransmission.[5] Although these principles now comprise much of the optimized foundation of internet applications, they differ from current optimization theory in that there was much less of an attempt to improve the browser display speed.

Steve Souders coined the term "web performance optimization" in 2004.[6] At that time Souders made several predictions regarding the impact that WPO as an "emerging industry" would bring to the web, such as websites being fast by default, consolidation, web standards for performance, environmental impacts of optimization, and speed as a differentiator.[7]

One major point that Souders made in 2007 is that at least 80% of the time that it takes to download and view a website is controlled by the front-end structure. This lag time can be decreased through awareness of typical browser behavior, as well as of how HTTP works.[8]

Optimization techniques

[edit]

Web performance optimization improves user experience (UX) when visiting a website and therefore is highly desired by web designers and web developers. They employ several techniques that streamline web optimization tasks to decrease web page load times. This process is known as front end optimization (FEO) or content optimization. FEO concentrates on reducing file sizes and "minimizing the number of requests needed for a given page to load."

In addition to the techniques listed below, the use of a content delivery network—a group of proxy servers spread across various locations around the globe—is an efficient delivery system that chooses a server for a specific user based on network proximity. Typically the server with the quickest response time is selected.

The following techniques are commonly used web optimization tasks and are widely used by web developers:

Web browsers open separate Transmission Control Protocol (TCP) connections for each Hypertext Transfer Protocol (HTTP) request submitted when downloading a web page. These requests total the number of page elements required for download. However, a browser is limited to opening only a certain number of simultaneous connections to a single host. To prevent bottlenecks, the number of individual page elements are reduced using resource consolidation whereby smaller files (such as images) are bundled together into one file. This reduces HTTP requests and the number of "round trips" required to load a web page.

Web pages are constructed from code files such JavaScript and Hypertext Markup Language (HTML). As web pages grow in complexity, so do their code files and subsequently their load times. File compression can reduce code files by about 40 percent[9], thereby improving site responsiveness.

Web Caching Optimization reduces server load, bandwidth usage and latency. CDNs use dedicated web caching software to store copies of documents passing through their system. Subsequent requests from the cache may be fulfilled should certain conditions apply. Web caches are located on either the client side (forward position) or web-server side (reverse position) of a CDN. Web browsers are also able to store content for re-use through the HTTP cache or web cache. Requests web browsers make are typically routed to the HTTP cache to validate if a cached response may be used to fulfill a request. If such a match is made, the response is fulfilled from the cache. This can be helpful for reducing network latency and costs associated with data-transfer. The HTTP cache is configured using request and response headers.

Code minification distinguishes discrepancies between codes written by web developers and how network elements interpret code. Minification removes comments and extra spaces as well as crunch variable names in order to minimize code, decreasing files sizes by as much as 60%. In addition to caching and compression, lossy compression techniques (similar to those used with audio files) remove non-essential header information and lower original image quality on many high resolution images. These changes, such as pixel complexity or color gradations, are transparent to the end-user and do not noticeably affect perception of the image. Another technique is the replacement of raster graphics with resolution-independent vector graphics. Vector substitution is best suited for simple geometric images.[citation needed]

Lazy loading of images and video reduces initial page load time, initial page weight, and system resource usage, all of which have positive impacts on website performance.[10] It is used to defer initialization of an object right until the point at which it is needed. The browser loads the images in a page or post when they are needed such as when the user scrolls down the page and not all images at once, which is the default behavior, and naturally, takes more time.

HTTP/1.x and HTTP/2

[edit]

Since web browsers use multiple TCP connections for parallel user requests, congestion and browser monopolization of network resources may occur. Because HTTP/1 requests come with associated overhead, web performance is impacted by limited bandwidth and increased usage.

Compared to HTTP/1, HTTP/2

  • is binary instead of textual
  • is fully multiplexed instead of ordered and blocked
  • can therefore use one connection for parallelism
  • uses header compression to reduce overhead
  • allows servers to "push" responses proactively into client caches[11]

Instead of a website's hosting server, CDNs are used in tandem with HTTP/2 in order to better serve the end-user with web resources such as images, JavaScript files and Cascading Style Sheet (CSS) files since a CDN's location is usually in closer proximity to the end-user.[12]

Metrics

[edit]

In recent years, several metrics have been introduced that help developers measure various aspects of the performance of their websites. In 2019, Google introduced metrics such as Time to First Byte (TTFB), First Contentful Paint (FCP), First Paint (FP), First Input Delay (FID), Cumulative Layout Shift (CLS) and Largest Contentful Paint (LCP) allow for website owner to gain insights into issues that might hurt the performance of their websites making it seem sluggish or slow to the user. Other metrics including Request Count (number of requests required to load a page), [13] DOMContentLoaded (time when HTML document is completely loaded and parsed excluding CSS style sheets, images, etc.), [14] Above The Fold Time (content that is visible without scrolling), [15] Round Trip Time, [15] number of Render Blocking Resources (such as scripts, stylesheets), [16] Onload Time, Connection Time, Total Page Size help provide an accurate picture of latencies and slowdowns occurring at the networking level which might slow down a site.[17][18][19]

Modules to measure metrics such as TTFB, FCP, LCP, FP etc are provided with major frontend JavaScript libraries such as React,[20] NuxtJS[21] and Vue.[22] Google publishes a library, the core-web-vitals library that allows for easy measurement of these metrics in frontend applications. In addition to this, Google also provides the Lighthouse, a Chrome dev-tools component and PageSpeed Insight a site that allows developers to measure and compare the performance of their website with Google's recommended minimums and maximums.[23]

In addition to this, tools such as the Network Monitor by Mozilla Firefox help provide insight into network-level slowdowns that might occur during transmission of data.[17]

References

[edit]
  1. ^ "Google Adds Site Speed To Search Ranking". Retrieved 4 December 2012.
  2. ^ Sharon, Bell. "WPO | Preparing for Cyber Monday Traffic". CDNetworks. Retrieved 4 December 2012.
  3. ^ Souders, Steve. "Web First for Mobile". Retrieved 4 December 2012.
  4. ^ Bellonch, Albert. "Web performance optimization for everyone". Retrieved 4 December 2012.
  5. ^ Killelea, Patrick (2002). Web Performance Tuning. Sebastopol: O'Reilly Media. p. 480. ISBN 059600172X.
  6. ^ Frick, Tim (2016). Designing for Sustainability: A Guide to Building Greener Digital Products and Services. Boston: O'Reilly Media. p. 195. ISBN 1491935774.
  7. ^ Frick, Tim (2016). Designing for Sustainability: A Guide to Building Greener Digital Products and Services. Boston: O'Reilly Media. p. 56. ISBN 1491935774.
  8. ^ Souders, Steve (2007). High Performance Websites. Farnham: O'Reilly Media. p. 170. ISBN 0596529309. Archived from the original on 8 March 2019.
  9. ^ Sakamoto, Yasutaka; Matsumoto, Shinsuke; Tokunaga, Seiki; Saiki, Sachio; Nakamura, Masahide (February 2015). "Empirical study on effects of script minification and HTTP compression for traffic reduction". IEEE. pp. 127–132. doi:10.1109/DINWC.2015.7054230. ISBN 978-1-4799-6376-8.
  10. ^ "Lazy loading - Web Performance | MDN". developer.mozilla.org. Retrieved 2022-03-15.
  11. ^ "HTTP/2 Frequently Asked Questions". HTTP Working Group. Retrieved 14 April 2017.
  12. ^ "HTTP/2 – A Real-World Performance Test and Analysis". CSS Tricks. Retrieved 14 April 2017.
  13. ^ Mobile Web Performance Optimization. 2015. ISBN 9781785284625.
  14. ^ The Web Performance Collection. 2018. ISBN 9781492069805.
  15. ^ a b Performance Optimization: Techniques And Strategies. ISBN 9783944540948.
  16. ^ Responsive Web Design with HTML5 and CSS. 2022. ISBN 9781803231723.
  17. ^ a b "Measuring performance - Learn web development | MDN". developer.mozilla.org. Retrieved 2023-01-09.
  18. ^ "Measuring Web Performance in 2023: The Definitive Guide". Request Metrics. Retrieved 2023-01-09.
  19. ^ "Front-End Performance Checklist 2021 (PDF, Apple Pages, MS Word)". Smashing Magazine. 2021-01-12. Retrieved 2023-01-09.
  20. ^ "Measuring Performance | Create React App". create-react-app.dev. Retrieved 2023-01-09.
  21. ^ "@nuxtjs/web-vitals". npm. Retrieved 2023-01-09.
  22. ^ "vue-web-vitals". npm. Retrieved 2023-01-09.
  23. ^ "User-centric performance metrics". web.dev. Retrieved 2023-01-09.

 

Retrieved from "http://en.wiki.x.io/w/index.php?title=Web_performance&oldid=1262186038"