80.2 sec in total
4.8 sec
72.9 sec
2.5 sec
Click here to check amazing Cankaoxiaoxi content for China. Otherwise, check out these important facts you probably never knew about cankaoxiaoxi.com
Visit cankaoxiaoxi.comWe analyzed Cankaoxiaoxi.com page load time and found that the first response time was 4.8 sec and then it took 75.4 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. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
cankaoxiaoxi.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value6.7 s
7/100
25%
Value9.7 s
11/100
10%
Value10 ms
100/100
30%
Value0.024
100/100
15%
Value5.9 s
65/100
10%
4790 ms
2060 ms
16617 ms
2751 ms
2750 ms
Our browser made a total of 200 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Cankaoxiaoxi.com, 42% (83 requests) were made to Upload.cankaoxiaoxi.com and 8% (15 requests) were made to Img.cankaoxiaoxi.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Pos.baidu.com.
Page size can be reduced by 789.5 kB (15%)
5.3 MB
4.5 MB
In fact, the total size of Cankaoxiaoxi.com main page is 5.3 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. 70% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 180.6 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 32.8 kB, which is 15% 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 180.6 kB or 82% of the original size.
Potential reduce by 447.6 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. Cankaoxiaoxi images are well optimized though.
Potential reduce by 133.7 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 133.7 kB or 64% of the original size.
Potential reduce by 27.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. Cankaoxiaoxi.com needs all CSS files to be minified and compressed as it can save up to 27.5 kB or 75% of the original size.
Number of requests can be reduced by 60 (32%)
190
130
The browser has sent 190 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cankaoxiaoxi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
cankaoxiaoxi.com
4790 ms
www.cankaoxiaoxi.com
2060 ms
stats
16617 ms
common.css
2751 ms
index.css
2750 ms
index.js
2753 ms
jquery.js
2961 ms
k.js
5688 ms
wb.js
105 ms
index0728.css
2750 ms
index_140728.css
2739 ms
slideFn.js
2853 ms
o.js
1120 ms
config.js
2852 ms
jquery.cookie.js
2853 ms
stat.php
1538 ms
x.js
4613 ms
count.png
1884 ms
1418953814895.gif
2907 ms
logo0728.png
121 ms
1460087109669.jpg
2910 ms
1460084601104.jpg
2905 ms
1401936299355.png
2904 ms
1460117119821.jpg
3202 ms
1460073086465.jpg
3203 ms
1460074724478.jpg
3222 ms
1459996511121.jpg
3225 ms
1460086175683.jpg
3590 ms
1460071020758.jpg
3198 ms
1460099610309.jpg
3310 ms
1460071602443.jpg
3311 ms
1460107074811.jpg
3311 ms
1460110293313.jpg
3320 ms
1460108697444.jpg
3322 ms
1458210528231.jpg
3345 ms
1460086022691.jpg
3346 ms
1456918263543.jpg
3341 ms
1460104672630.jpg
3421 ms
1460020525287.jpg
3420 ms
1459413663614.jpg
3450 ms
1460009529459.jpg
3447 ms
1459417278395.jpg
3457 ms
1458733522479.jpg
3555 ms
1459837405874.jpg
3553 ms
1459147643762.jpg
3509 ms
1459147533199.jpg
3509 ms
thumb_100_75_1460122118244.png
3515 ms
1460081474573.jpg
3686 ms
1459986115475.jpg
3679 ms
1459990313296.jpg
3691 ms
1458025554974.jpg
3766 ms
1457670904878.jpg
3767 ms
1460076974657.jpg
3849 ms
1459298586360.jpg
3850 ms
1459133341518.jpg
3869 ms
ecum
1137 ms
ico0728.png
130 ms
ico.png
149 ms
nav_2.png
496 ms
dotline-1.gif
484 ms
icon2.png
484 ms
ecum
448 ms
ex
988 ms
ecum
458 ms
1459321190178.jpg
974 ms
1459992764100.jpg
974 ms
1457418572883.jpg
896 ms
1450241512858.jpg
1036 ms
ex
1101 ms
ecum
519 ms
1449107572173.jpg
767 ms
1458090214967.jpg
797 ms
1447056178915.jpg
1700 ms
1442390772915.jpg
1324 ms
1459415548263.jpg
1159 ms
1459415440533.jpg
868 ms
1459415580509.jpg
923 ms
1460077158375.jpg
962 ms
1460030497793.jpg
1051 ms
1459946741200.jpg
1052 ms
tanxssp.js
450 ms
1460083680326.jpg
1027 ms
1460002400642.jpg
1080 ms
1460077499686.png
1042 ms
1460010852151.jpg
1012 ms
1460010932645.jpg
991 ms
1460077851683.jpg
1022 ms
1459927321427.jpg
1072 ms
1459906133940.jpg
1075 ms
1460034654514.jpg
1059 ms
1459951522600.jpg
1063 ms
1460017765956.jpg
1093 ms
1459984771653.png
1105 ms
1459983865122.jpg
1058 ms
1459897739923.jpg
1141 ms
1459990724269.jpg
991 ms
1459862670628.jpg
1029 ms
1417512613150.png
977 ms
ex
3887 ms
ecum
531 ms
1403748818848.png
954 ms
1403749358852.png
953 ms
privacy.js
67 ms
ex
1203 ms
1402023461506.png
873 ms
1365324486734.png
906 ms
1365324811300.png
901 ms
1411958091457.jpg
947 ms
1406619863987.png
912 ms
1406619693672.png
891 ms
1411977247725.jpg
913 ms
1439782590714.jpg
856 ms
1406623764721.jpg
883 ms
ex
7196 ms
1406625796481.jpg
701 ms
1429064000357.png
628 ms
1429175024934.jpg
647 ms
ex
2373 ms
ecum
2316 ms
1401958684652.jpg
566 ms
1429065369192.png
535 ms
x.gif
429 ms
acbeacon2.html
452 ms
TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png
146 ms
TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png
143 ms
TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png
143 ms
TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png
143 ms
TB1XQ0HIFXXXXbIXXXXO04pFXXX.html
414 ms
t.gif
1249 ms
t.gif
942 ms
bl
935 ms
cm.gif
522 ms
app.gif
991 ms
T2WZQPXdpaXXXXXXXX_!!0-2-newland.png
249 ms
T2n4.PXbVXXXXXXXXX_!!0-2-newland.png
350 ms
T2krG1XgdXXXXXXXXX_!!0-1-newland.gif
292 ms
tanxclick.js
111 ms
T24.wOXltXXXXXXXXX_!!0-2-newland.png
317 ms
ex
10308 ms
ex
1273 ms
ecum
8383 ms
TB1bjWwGXXXXXcSXXXXcplJIVXX-76-48.gif
191 ms
t.gif
1090 ms
um.js
512 ms
img
5571 ms
ex
10089 ms
cms.gif
1103 ms
um.json
2859 ms
getDeviceInfo
1256 ms
TB1XQ0HIFXXXXbIXXXXO04pFXXX.html
73 ms
bl
1079 ms
TB29XIPcXXXXXX1XpXXXXXXXXXX_!!0-0-newland.jpg
63 ms
T2hyKzXj8bXXXXXXXX_!!0-1-newland.gif
98 ms
T2rnTwXgJbXXXXXXXX_!!0-2-newland.png
528 ms
T2guO0XftaXXXXXXXX_!!0-1-newland.gif
167 ms
getDeviceInfo
1383 ms
TB1XQ0HIFXXXXbIXXXXO04pFXXX.html
64 ms
bl
20072 ms
T26piLXjRaXXXXXXXX_!!0-0-newland.jpg
43 ms
T2YGZPXhtXXXXXXXXX_!!0-2-newland.png
62 ms
T2kWsQXbhXXXXXXXXX_!!0-2-newland.png
20 ms
T26scJXiBaXXXXXXXX_!!0-2-newland.png
540 ms
ex
3991 ms
ecum
559 ms
T2I_CMXcRXXXXXXXXX_!!0-0-newland.jpg
121 ms
T2Vv.NXglaXXXXXXXX_!!0-2-newland.png
122 ms
T2COUiXXlbXXXXXXXX_!!0-2-newland.png
115 ms
T2GYGLXdhbXXXXXXXX_!!0-1-newland.gif
119 ms
a.htm
1597 ms
ex
4271 ms
cmp.htm
1457 ms
TB1XQ0HIFXXXXbIXXXXO04pFXXX.html
104 ms
t.gif
10274 ms
bl
1047 ms
hm.js
1269 ms
stat.htm
653 ms
core.php
1489 ms
T2tKIPXglXXXXXXXXX_!!0-2-newland.png
108 ms
T2fzkOXolXXXXXXXXX_!!0-2-newland.png
54 ms
T2uup0XlFdXXXXXXXX_!!0-2-newland.png
343 ms
T20yiOXaXaXXXXXXXX_!!0-1-newland.gif
340 ms
ex
1022 ms
hm.gif
396 ms
loading1.gif
89 ms
bundle.js
907 ms
TB1XQ0HIFXXXXbIXXXXO04pFXXX.html
130 ms
bl
1032 ms
TB1XQ0HIFXXXXbIXXXXO04pFXXX.html
186 ms
t.gif
2145 ms
bl
2047 ms
T22EaMXnFXXXXXXXXX_!!0-0-newland.jpg
134 ms
T2x2W0XglaXXXXXXXX_!!0-1-newland.gif
132 ms
T2Rk_mXgdaXXXXXXXX_!!0-1-newland.gif
376 ms
T2Hu5MXllaXXXXXXXX_!!0-0-newland.jpg
121 ms
chain
1594 ms
cms.gif
328 ms
bg_2_03.png
2657 ms
o.htm
20483 ms
search_03.png
2652 ms
hm.gif
404 ms
cankaoxiaoxi.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Links do not have a discernible name
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.
cankaoxiaoxi.com 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cankaoxiaoxi.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cankaoxiaoxi.com 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 Cankaoxiaoxi.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.
cankaoxiaoxi.com
Open Graph description is not detected on the main page of Cankaoxiaoxi. 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: