27.4 sec in total
1.4 sec
25.4 sec
609 ms
Click here to check amazing Kejimeixue content for China. Otherwise, check out these important facts you probably never knew about kejimeixue.com
Visit kejimeixue.comWe analyzed Kejimeixue.com page load time and found that the first response time was 1.4 sec and then it took 26 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
kejimeixue.com performance score
1408 ms
4264 ms
3093 ms
2861 ms
3016 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Kejimeixue.com, 36% (55 requests) were made to Cdn.kejimeixue.com and 6% (10 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (10.9 sec) relates to the external source Cdn.kejimeixue.com.
Page size can be reduced by 4.1 MB (76%)
5.4 MB
1.3 MB
In fact, the total size of Kejimeixue.com main page is 5.4 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. 55% of websites need less resources to load. CSS take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 1.1 MB
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 1.1 MB or 91% of the original size.
Potential reduce by 87.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. Obviously, Kejimeixue needs image optimization as it can save up to 87.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 548.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 548.8 kB or 64% of the original size.
Potential reduce by 2.3 MB
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. Kejimeixue.com needs all CSS files to be minified and compressed as it can save up to 2.3 MB or 89% of the original size.
Number of requests can be reduced by 91 (63%)
145
54
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kejimeixue. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
www.kejimeixue.com
1408 ms
dashicons.min.css
4264 ms
jquery-ui-dialog.min.css
3093 ms
styles.css
2861 ms
jquery.fancybox.css
3016 ms
swipebox.min.css
3118 ms
settings.css
3618 ms
js_composer.min.css
6773 ms
font-awesome.min.css
3621 ms
grid.css
5028 ms
shared.css
4318 ms
libs.css
5014 ms
header.css
5662 ms
content.css
4664 ms
sides.css
5006 ms
footer.css
5352 ms
widgets_shortcodes.css
6751 ms
visual_composer.css
6694 ms
revslider.css
5710 ms
ninjaforms.css
6549 ms
woocommerce.css
7112 ms
www.kejimeixue.com
1849 ms
embed.js
286 ms
jquery.js
6813 ms
jquery-migrate.min.js
6998 ms
jquery.swipebox.min.js
7637 ms
front.js
8018 ms
jquery.themepunch.tools.min.js
8306 ms
jquery.themepunch.revolution.min.js
7151 ms
z_stat.php
2407 ms
core.php
1196 ms
core.min.js
7176 ms
widget.min.js
8875 ms
mouse.min.js
7170 ms
resizable.min.js
7543 ms
draggable.min.js
7648 ms
button.min.js
7807 ms
position.min.js
7897 ms
dialog.min.js
10031 ms
wpdialog.min.js
8893 ms
jquery.form.min.js
9486 ms
scripts.js
5726 ms
jquery.fancybox.pack.js
6972 ms
light.js
6533 ms
comment-reply.min.js
6574 ms
all_in_one_libs.min.js
10871 ms
front.min.js
8926 ms
SmoothScroll.js
5943 ms
wp-embed.min.js
6512 ms
js_composer_front.js
6548 ms
embed.default.css
115 ms
embed.compat.js
292 ms
XMTUyNjY0NTAyNA==
1882 ms
XMTUyNTYxNTAwMA==
1886 ms
XMTUyNDM4NDM5Mg==
1918 ms
XMTUxOTcyODA4OA==
1883 ms
index.php
1454 ms
logo.png
4172 ms
weixin.png
4846 ms
youku.png
9431 ms
bilibili.png
3301 ms
douyu.png
3783 ms
iqiyi.png
4224 ms
acfun.png
7946 ms
qqvideo.png
7526 ms
hwt.js
2234 ms
hm.js
2491 ms
hwt.js
1475 ms
hwt.js
3031 ms
stat.htm
243 ms
9.gif
822 ms
vds.js
5766 ms
analytics.js
116 ms
hwt.1.7.1.test.js
2230 ms
share.js
1460 ms
9.gif
3886 ms
9.gif
1067 ms
stat.htm
233 ms
collect
57 ms
collect
112 ms
app.gif
968 ms
weiboShow.css
60 ms
skin_default.css
58 ms
gaea_1_19.js
74 ms
wb_logo16_a.png
45 ms
0
481 ms
icon_user.png
41 ms
btns_bg.png
44 ms
icon_follow.png
45 ms
app.gif
801 ms
006pqVKGjw1f2pl3vytw1j318g0ildk8.jpg
529 ms
41399761jw1f2pd0oxqkyj20c837946w.jpg
454 ms
006pqVKGjw1f2obiv92mlj30sc0iun52.jpg
67 ms
006pqVKGjw1f2o7fqlyfsj30l10dgmz0.jpg
63 ms
mb_org.gif
54 ms
suda.js
53 ms
41399761jw1f2p5zt1c0tj20jy0lu0v3.jpg
254 ms
006pqVKGjw1f2p3ikoj8dj30bw0g3405.jpg
230 ms
006pqVKGjw1f2mvuq7geaj30go09d3yu.jpg
226 ms
006pqVKGjw1f2ksgm69pej30dc08bmy4.jpg
228 ms
006pqVKGjw1f2n70io7vxj310j0lhq8h.jpg
70 ms
e2d7633cjw1f2n4q924swj20iw0iwac5.jpg
60 ms
e2d7633cjw1f2mst7lw64j20iw0eb3zz.jpg
77 ms
006pqVKGjw1f2lypx9x47j30xc0hi0yd.jpg
68 ms
0063yfcGjw1f2ijjxhwhlj30d70g3ace.jpg
67 ms
41399761jw1f2luzx2431j20pk0howep.jpg
59 ms
show.js
20 ms
bg_trans.png
30 ms
icon_tips.png
28 ms
a.gif
9158 ms
tmp.gif
1069 ms
storage.html
762 ms
storage.html
883 ms
storage.html
2579 ms
jsapi
1887 ms
hwt
782 ms
hwt
751 ms
hm.gif
306 ms
hwt
926 ms
hwt
5678 ms
play.css
844 ms
custom.json
4382 ms
custom.json
4406 ms
custom.json
4182 ms
custom.json
4544 ms
app.gif
442 ms
hwt
5009 ms
hwt
1947 ms
xplayerv4.png
629 ms
get.json
2348 ms
get.json
3157 ms
get.json
2364 ms
get.json
2370 ms
pv
4125 ms
hwt
4217 ms
style.css
2808 ms
forms.css
4416 ms
counts.json
2176 ms
slide_api.js
603 ms
slide_view.js
1192 ms
tangram.js
2329 ms
api_base.js
3655 ms
action
4756 ms
view_base.js
376 ms
0541010156FE3606641DA41CA8C353AD
858 ms
05410408570638526A0A4F1314B16B6B
3456 ms
054101015704F054641DA41CA813C5D2
830 ms
054101015703852A641DA41CA8A52786
605 ms
hwt
2005 ms
logger.js
405 ms
slide_share.css
1422 ms
r3.gif
392 ms
icons_0_16.png
826 ms
hm.gif
910 ms
kejimeixue.com SEO score
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kejimeixue.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Kejimeixue.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.
kejimeixue.com
Open Graph description is not detected on the main page of Kejimeixue. 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: