Optimization requirements for developing internet products

Minimum number of requests:

• tab page asynchronous loading or lazy loading;
• merging js/css files;
• CSS Sprites CSS image map;
• Unify common js/css files;
• merging AJAX requests;
• Avoid redirection;
• Reduce the IFRAME request;
• Portrait, picture scrolling delay loading;
• An unimportant page module is loaded asynchronously;
• Multi-level cache.

Fastest Request Speed:

• Set the long-time cache;
• Try to use request cacheable;
• Cookie isolation;
• dynamic, static application separation;
• Select the appropriate Web server by type;
• Appropriate use of multi-domain to increase parallel download;
• Set gzip compression;
• Multi-IDC deployment, dynamic internal agent;
• Using a CDN network;
• Improve the positioning ability of IP library;
• Image quality compression, use PNG8;
• Picture pre-loading;
• JS/CSS confusion;
• compress the page code;
• Unified Common JS Library code and application code;
• reduce cookie size;
• Logical layer protocol merging and parallel processing;
• Data, indexed memory, SSD parallel write.

The fastest visible is available:

• First screen optimization principle;
• Reduce the number of elements, size;
• HTML, CSS, JS code to lose weight;
• JS performance optimization div+css layout;
• optimization, avoid using CSS expressions;
• CSS Sprites split screen css, JS;
• JS parallel download at the bottom of the page;
• Avoid complicated JS cycle calculation;
• Unified JS placed at the end of the page;
• Load on demand, asynchronous load, lazy load, preload;
• Output HTML code as soon as possible.
  

In the Internet age, winning or losing is really just a second, or even a few milliseconds. Your first screen opens faster than others a few milliseconds, then others will have more users than you, so good products, must be done quickly.

JS is a Web performance killer, a novice to write the JS code, or a messy emission of JS code, will overall drag your site experience;

Configure gzip compression to be able to compress up to 80, which can greatly reduce the pressure on the service side;

Lazy loading, preloading, in a nutshell, be sure to load on demand.

Optimization requirements for developing internet products