Service Tel
service hotline
021-31056671

Company news

Current location : Home

8 Web performance improvement suggestions from engineers

2018-10-21 Hits:274

With the popularity of the Internet today, more and more online users want a safe, reliable and fast access experience. Radware has proposed the following improvements to Web site operators to help them provide users with the fastest and highest quality access experience for Web pages that are too bloated and the third script encroaches on traffic.

8 Web performance improvement suggestions from engineers

1, management page expansion page size and performance are closely related. According to the survey, the median size of the top 100 e-commerce pages reached 1492 KB, an increase of 48% over a year and a half ago.

Of the 10 fastest loaded pages in the study, the page contained 50 median resource requests and a median page size of 556 KB. Of the 10 slowest-loading pages, 141 had a median resource request and 3289KB had a median page size. In other words, the median resource of the slowest-loaded page is almost three times as large as that of the fastest-loaded page, and the page size is six times as large.

We can get more information by studying the size of the page carefully. The 10 fastest loaded pages contain a relatively dense range of resources: 15 to 72; the smallest page size is only 251KB, the largest 2003KB. The 10 slowest-loading pages contain a wide range of resources: between 89 and 373; the smallest page size is 2073KB; the largest is more than 10MB.

2. Image optimization.

Image is one of the culprits causing page expansion, usually occupying 50-60% of page bytes. Adding pictures to a page or enlarging existing pictures is an effective way to quickly capture users and improve business conversion. But this method can seriously affect the performance.

Image optimization is the simplest way to improve performance, which enables faster page loading. In order to render the image more effectively, the image must be compressed and integrated, the size and format of the image must be carefully adjusted, and the image quality must be optimized, so that the image can be loaded differently according to the importance of the image.

3, control the third party script.

In typical page server requests, requests from third-party scripts account for 50% or more of them. These third-party scripts not only increase the number of bytes on the page and cause latency, but also become the biggest potential failure point in a Web page. Unresponsive and unoptimized third party scripts reduce the loading speed of the entire network.

The solution is to delay the loading of third-party scripts, which are loaded after the key page content, and ideally after the onLoad event on the page, without affecting the search ranking of the enterprise (Google uses the onLoad event as a load time metric). For some analysis tools and third-party advertisers, if the method of delaying third-party script loading is not feasible, the asynchronous version of the script can be used to synchronize with the loading of key content. Users must know what scripts are in the site, delete those useless scripts, and continuously monitor the performance of third-party scripts.

4, truly mobile device priority

"Mobile device first" is not a completely new concept. As early as 2013, mobile devices used more than desktops, but there is still a gap between really focusing on mobile devices and the many promised mobile capabilities. For example, in November 2011, the average page size of mobile devices was 475KB, and now it has increased to 897 KB. That is to say, in just three years, the average page size almost doubled.

Despite advances in mobile devices and networks, it is still not possible to keep up with requirements for service pages that are close to 1MB in size in terms of performance. We know that page size is closely related to load time, and mobile users are particularly sensitive to slow load speed. If companies want websites to be truly mobile-first, they have to deal with these issues correctly.

5, give consideration to performance in responsive Web design.

Responsive design allows designers and developers to better control the appearance and feel of Web pages. It can make pages more beautiful across multiple platforms and devices. But there are also huge performance losses that cannot be mitigated by faster browsers, networks, and gadgets. And this will continue to deteriorate over time.

Responsive design is based on stylesheets and JavaScript. However, the performance problems of inefficient CSS and JS far outweigh the benefits of their design advantages. The stylesheet should be placed in the HEAD document to achieve progressive rendering of the page. However, stylesheets often appear in other positions of the page, which hinders the rendering speed of the page. In other words, JavaScript files should be placed at the bottom of the page or loaded after the key content is loaded.

6, real-time monitoring performance

As we all know, to solve a problem, we must first have a thorough understanding of the problem. To solve page performance problems, the enterprise must know when users can see and interact with the main page content; at the same time, the enterprise also needs to understand how performance and availability issues affect business metrics. Enterprises need to have a way to get actual performance indicators and analyze them. Real-time user monitoring (RUM) tools can capture, analyze, and record the performance and availability of a Web site in real-time from the perspective of real users.

7, do not depend too much on it.