15.3 sec in total
734 ms
14.5 sec
148 ms
Visit 139.com now to see the best up-to-date 139 content for China and also check out these interesting facts you probably never knew about 139.com
139邮箱,手机邮箱,139mail,email,邮箱,移动邮箱,免费邮箱,139邮箱登录,HTML5邮箱,离线邮件,发短信,发贺卡139 wapmail,139WAP,wapmail 10086
Visit 139.comWe analyzed 139.com page load time and found that the first response time was 734 ms and then it took 14.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
139.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value3.9 s
51/100
25%
Value11.4 s
5/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value3.7 s
90/100
10%
734 ms
736 ms
1499 ms
484 ms
729 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original 139.com, 62% (16 requests) were made to Mail.10086.cn and 12% (3 requests) were made to Img.mcloud.139.com. The less responsive or slowest element that took the longest time to load (7.4 sec) relates to the external source Img.mcloud.139.com.
Page size can be reduced by 306.4 kB (43%)
715.5 kB
409.1 kB
In fact, the total size of 139.com main page is 715.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 336.1 kB which makes up the majority of the site volume.
Potential reduce by 132.1 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 132.1 kB or 77% of the original size.
Potential reduce by 22.8 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. 139 images are well optimized though.
Potential reduce by 151.4 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 151.4 kB or 73% of the original size.
Number of requests can be reduced by 5 (23%)
22
17
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 139. 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.
139.com
734 ms
mail.10086.cn
736 ms
mail.10086.cn
1499 ms
139.png
484 ms
hongbao.png
729 ms
i-wechat.jpg
1212 ms
i-hide.png
975 ms
select.png
977 ms
mail_app.png
751 ms
qrcode-error.png
982 ms
login_success.png
981 ms
codeTips.png
1008 ms
tingyun-rum.js
2174 ms
s
770 ms
1692689272801.png
4025 ms
1698285522923.png
4263 ms
png8.png
736 ms
1708658371249.jpeg
7416 ms
reported
797 ms
reported
1066 ms
md5.js
247 ms
s
242 ms
s
1024 ms
jsencrypt.js
1234 ms
iconfont.woff
244 ms
sdc_MAIL.js
1808 ms
139.com 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.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
139.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
139.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 139.com 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 139.com 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.
139.com
Open Graph description is not detected on the main page of 139. 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: