43.9 sec in total
943 ms
42.5 sec
442 ms
Visit 139.cm 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.cm
海外域名注册商(www.Li.cm)提供查询海外国别域名申请注册以及新通用顶级域名注册和国际IDN域名申请注册,云服务器虚拟主机购买与企业邮箱邮局、网站防护以及域名SSL证书申请服务.
Visit 139.cmWe analyzed 139.cm page load time and found that the first response time was 943 ms and then it took 43 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
139.cm performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value3.0 s
79/100
25%
Value2.6 s
97/100
10%
Value140 ms
95/100
30%
Value0.029
100/100
15%
Value3.0 s
96/100
10%
943 ms
29 ms
1768 ms
588 ms
58 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 76% of them (34 requests) were addressed to the original 139.cm, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Li.cm. The less responsive or slowest element that took the longest time to load (19.9 sec) belongs to the original domain 139.cm.
Page size can be reduced by 769.5 kB (50%)
1.6 MB
783.3 kB
In fact, the total size of 139.cm main page is 1.6 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. 30% of websites need less resources to load. CSS take 716.5 kB which makes up the majority of the site volume.
Potential reduce by 37.2 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. This page needs HTML code to be minified as it can gain 11.8 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.2 kB or 76% of the original size.
Potential reduce by 7.7 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 122.8 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 122.8 kB or 61% of the original size.
Potential reduce by 601.8 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. 139.cm needs all CSS files to be minified and compressed as it can save up to 601.8 kB or 84% of the original size.
Number of requests can be reduced by 14 (44%)
32
18
The browser has sent 32 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 15 to 1 for JavaScripts and as a result speed up the page load time.
139.cm
943 ms
cloudflare.min.js
29 ms
production.css
1768 ms
chinese.css
588 ms
jquery.js
58 ms
commonScripts.js
48 ms
cart.js
50 ms
jquery.innerfade.js
48 ms
jquery.scrollTo.js
50 ms
homepage.js
55 ms
loading_animation.js
55 ms
footerScripts.js
56 ms
ga_event_tracking.js
56 ms
stat.php
2644 ms
bag2
257 ms
analytics.js
118 ms
getImage.php
105 ms
getImage.php
579 ms
getImage.php
587 ms
getImage.php
8438 ms
getImage.php
1214 ms
getImage.php
584 ms
getImage.php
586 ms
getImage.php
1068 ms
getImage.php
1055 ms
getImage.php
19579 ms
getImage.php
1474 ms
getImage.php
1902 ms
getImage.php
19578 ms
getImage.php
2072 ms
getImage.php
19578 ms
getImage.php
2796 ms
getImage.php
3979 ms
collect
21 ms
getImage.php
3369 ms
getImage.php
81 ms
getImage.php
197 ms
stat.htm
445 ms
core.php
2635 ms
9.gif
2675 ms
nr-460.min.js
107 ms
getImage.php
19934 ms
getImage.php
1911 ms
getImage.php
19933 ms
dda02a7efd
58 ms
139.cm 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
<frame> or <iframe> elements do not have a title
139.cm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
139.cm 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 139.cm can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 139.cm 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.cm
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: