Use Audits (debug tool)
Experience Rating:
- Avoid picture is too large to effectively display a smaller area , waste flow and drop loading speed;
- Network image resources should enable HTTP cache control , reducing the number of requests;
- Avoid request takes too , should be optimized better server processing time, packet size is reduced back, bottom load may be used;
- Avoid too many pictures request to initiate a short time , otherwise it will trigger limit browser loaded in parallel, can lead to slow loading images, users have been waiting for treatment. It should be a reasonable amount of control, consider using Sprite map technology or picture outside the screen using lazy loading;
- Avoid too many requests to initiate a short time , otherwise it will trigger small programs limit the number of concurrent requests, while too many requests may also lead to problems such as slow loading, should be the reasonable control of the number of requests, or even a request of the merger;
- Avoid setData data is too large , can not exceed more than 1M, due to the small program running on a logical thread and rendering thread, setData call will render layer data transmitted from the logic layer, data is too large to increase communication time;
- Avoid calling setData too often, calling setData interface logic involves inter-thread rendering layer by layer and, too often may lead to communication processing queue blocking, rendering the interface is not timely and lead to Caton, should avoid useless frequent calls;
- Avoid unbound variables passed in WXML setData , can be defined on the outside, reducing performance overhead due setData;
- Avoid time-consuming execution of the script is too long , took too long to make the user feel Caton, a bad experience, when this situation occurs, it is necessary to identify and optimize the logic of the script;
- Necessary to make network requests to avoid unnecessary cache request , the request for the same cache, reducing the user waiting time;
- All resource requests are recommended to use HTTPS , the security can not easily be tampered with;
- Avoid the use of obsolete interface ;
- Timer recovery following the page, when the page is destroyed or hidden, should the recovery timer;
- Avoid excessive number WXML nodes ,
- Less than 1000 WXML nodes;
- Layer 30 is less than the depth of the tree node;
- Child nodes is not greater than 60.
- The first screen to avoid too long a case can be subcontracted processing;
- Reasonable clickable elements provided region size of the response , as a button, not too small;
- Avoid using css ': active' pseudo-class to implement click state ,: active bad effect, when rolling or sliding, no click state disappears; hover-class should be used alternatively;
- Should let the picture aspect ratio of the original chart, it may cause picture distortion, unsightly, and even lead to user identification difficult. Image mode attribute may be set as the case assembly to maintain the original aspect ratio;
- Scroll inertial scrolling area can be opened to enhance the experience,
- In the default Android with inertial scrolling;
- The need for additional set `-webkit-overflow-scrolling in iOS: touch` style;
Run experience score (start), avoid excessive number WXML node and then all the pages of the operating functions, after operation (STOP), Audits will print out the performance, experience and best practice score and give optimization recommendations .
According to Audits give advice and optimization positioning to optimize.
