188.com Site Title
188.com Meta Description
188.com Test Results
188.com Mobile Usability: 60/100
Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
VIP邮箱介绍and 3 others render only 5 pixels tall (12 CSS pixels).
Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target
<a href="http://vip.163…m=vip188_login">VIP邮箱介绍</a>and 3 others are close to other tap targets.
Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 1,009 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<img id="bg" src="http://mimg.12…8141498499.jpg">falls outside the viewport.
Your page uses plugins, which prevents portions of your page from being used on many platforms. Find alternatives for plugin based content to increase compatibility.
Find alternatives for the following Flash plugins.
188.com Mobile Speed: 61/100
Your page has 8 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
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:
https://qiyukf.com/script/2c3ce4e66d5fb98ded66967fd5f284c6.js (expiration not specified)
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 50% 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 52.6KiB (46% reduction).
Compressing http://mimg.127.net/vip/newindex/img/kf_sprite.png could save 18.8KiB (60% reduction).
Minifying http://mimg.127.net/vip/spread/js/spread.js could save 1.8KiB (12% reduction) after compression.
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 788B (56% reduction).
Compressing http://imgs.vip.163.com/popularize/spread/getbatchspread.m?aId=188&spreadTypeList=9,10&callback=jQuery18106862162728793919_1478727619431&_=1478727619434 could save 788B (56% reduction).
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 604B (11% reduction).
Minifying http://mimg.127.net/vip/newindex/css/style.css?v20160811 could save 604B (11% reduction) after compression.