51.6 sec in total
10 sec
41.4 sec
124 ms
Click here to check amazing 163 content for China. Otherwise, check out these important facts you probably never knew about 163.net
163.net是TOM旗下的VIP邮箱品牌,商务办公极速安全收费邮箱,丰富的域名邮箱格式、163vip邮箱注册登陆、海外邮件注册申请、外贸邮箱稳定性更是领先国内其他邮箱,拥有超过20年运营经验,7*24小时一对一服务,是非常好用个人电子邮箱品牌。
Visit 163.netWe analyzed 163.net page load time and found that the first response time was 10 sec and then it took 41.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
163.net performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value5.1 s
24/100
25%
Value6.5 s
39/100
10%
Value590 ms
50/100
30%
Value0.062
97/100
15%
Value7.1 s
52/100
10%
10037 ms
1398 ms
7919 ms
2103 ms
3502 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that 90% of them (18 requests) were addressed to the original 163.net, 5% (1 request) were made to Bjcgi.163.net and 5% (1 request) were made to News.tom.com. The less responsive or slowest element that took the longest time to load (12.6 sec) belongs to the original domain 163.net.
Page size can be reduced by 729.7 kB (59%)
1.2 MB
500.5 kB
In fact, the total size of 163.net main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. CSS take 581.5 kB which makes up the majority of the site volume.
Potential reduce by 15.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.3 kB or 72% of the original size.
Potential reduce by 104.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, 163 needs image optimization as it can save up to 104.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 77.3 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 77.3 kB or 66% of the original size.
Potential reduce by 532.5 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 163.net needs all CSS files to be minified and compressed as it can save up to 532.5 kB or 92% of the original size.
Number of requests can be reduced by 5 (26%)
19
14
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 163. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
163.net
10037 ms
index_201108_def.css
1398 ms
getTm.cgi
7919 ms
main_u8.js
2103 ms
jquery-1.5.2.min.js
3502 ms
jquery.cookie.js
1754 ms
extrahinfo.js
1404 ms
copyright_u8.js
354 ms
indexMain.jpg
4342 ms
indexMain.jpg
9155 ms
indexMain.jpg
2768 ms
indexPic1.gif
687 ms
bg-newsIcon.png
346 ms
bg-proX.gif
12580 ms
pd_icon.gif
692 ms
productIcon.gif
4078 ms
v2008.js
8587 ms
index_201108_1.css
3825 ms
indexBg.png
345 ms
indexMain.jpg
5891 ms
163.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
163.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
163.net SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 163.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 163.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
163.net
Open Graph description is not detected on the main page of 163. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: