163.com Site Title
163.com Test Results
163.com Mobile Usability: 100/100
163.com Mobile Speed: 54/100
Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
Avoid landing page redirects
Your page has 3 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 15% of the final above-the-fold content could be rendered with the full HTML response.
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 47.8KiB (52% reduction).
Losslessly compressing http://img2.cache.netease.com/f2e/wap/touch/trunk/common/images/no_papa.png could save 17.6KiB (54% reduction).
Reduce server response time
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://temp.163.com/special/00804KT2/wap_ad_sy.js (10 minutes)
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 1.6KiB (84% reduction).
Compressing http://temp.163.com/special/00804KT2/wap_ad_sy.js could save 1.6KiB (84% reduction).