14.2 sec in total
772 ms
11.3 sec
2.2 sec
Welcome to lifan.moe homepage info - get ready to check Lifan best content for China right away, or after learning these important things about lifan.moe
Visit lifan.moeWe analyzed Lifan.moe page load time and found that the first response time was 772 ms and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lifan.moe performance score
772 ms
271 ms
239 ms
427 ms
245 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 38% of them (30 requests) were addressed to the original Lifan.moe, 13% (10 requests) were made to Ww2.sinaimg.cn and 10% (8 requests) were made to Ww4.sinaimg.cn. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source S95.cnzz.com.
Page size can be reduced by 644.9 kB (9%)
6.9 MB
6.2 MB
In fact, the total size of Lifan.moe main page is 6.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.3 MB which makes up the majority of the site volume.
Potential reduce by 79.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. 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 79.2 kB or 81% of the original size.
Potential reduce by 189.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. Lifan images are well optimized though.
Potential reduce by 153.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 153.8 kB or 63% of the original size.
Potential reduce by 222.1 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. Lifan.moe needs all CSS files to be minified and compressed as it can save up to 222.1 kB or 81% of the original size.
Number of requests can be reduced by 16 (21%)
76
60
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lifan.moe
772 ms
style.css
271 ms
responsive.css
239 ms
customcss.php
427 ms
font-awesome.css
245 ms
embed.js
1133 ms
jquery-1.10.2.min.js
2077 ms
1182 ms
s.php
1487 ms
cf.aspx
614 ms
function.js
237 ms
wp-embed.min.js
255 ms
theme.min.js
678 ms
embed.default.css
524 ms
embed.compat.js
2355 ms
lifan.moe
656 ms
c6c20fa2gw1f00giy3xx6j215o0rekcz.jpg
1605 ms
0069cEk8gw1ey6d30ndb0j30oe0g540n.jpg
841 ms
8a368c28gw1ey55knfszej20sg0ehgqc.jpg
247 ms
005ODKsIjw1f2grwgz7tlj30zq0lfgwg.jpg
729 ms
CPHOv.jpg
244 ms
81c7a228gw1esq4dfu9r0g209w05kx6q.gif
1907 ms
0069cEk8gw1ezb1l1o51aj30zm0k07ar.jpg
1236 ms
XFHUZ@LZCXWYFJR3@Q0-750x462.png
303 ms
CIMG1782_-750x500.jpg
236 ms
SW-39.jpg
300 ms
0069cEk8gw1exx3pcaosxj30xc18gwm8-690x500.jpg
235 ms
0069cEk8gw1ex9yvgaqw6j30ac0fpgmz-372x500.jpg
234 ms
27LSO9-750x485.png
1169 ms
image-pending.gif
418 ms
gravatar.png
493 ms
55f2917890504-300x225.jpeg
809 ms
lifan.moe_2016-04-04_09-28-49.jpg
986 ms
53841805_p1_master1200-375x250.jpg
860 ms
captcha-clk.png
771 ms
0065dCgmgw1f2pflce5mkj31kq2aku0x.jpg
103 ms
c6c20fa2jw1f2ph4wsk03j20dw09b765.jpg
101 ms
a6f84856jw1f2n6tzvx4qj20fk0bo76h.jpg
103 ms
0060lm7Tgw1f2jghvix7aj31kw11xwpa.jpg
114 ms
006hZq2Egw1f1rykpc221j31741lcn8y.jpg
132 ms
0065dCgmgw1f2pdsothw7j30m40gldke.jpg
980 ms
0065dCgmgw1f2p9g7kv6dj30tr0myjvr.jpg
842 ms
0065dCgmgw1f2p8i8xdy6j30xc0irgr2.jpg
826 ms
0065dCgmgw1f2ojypwyd8j30ov0dw0v8.jpg
806 ms
005ODKsIjw1f2gqwkn46pj30me0i3q8v.jpg
979 ms
c6c20fa2jw1f2ph11oofwj20fk0af76z.jpg
978 ms
006aKQPZjw1ezekq7yz2kj305y08c74r.jpg
976 ms
0069cEk8gw1eyb45yzr5lj30go0tm3zl.jpg
972 ms
006phRArgw1f1id6dyxhoj30si16oteo.jpg
1148 ms
c6c20fa2gw1euqm1l67x8j2086030t92.jpg
394 ms
fontawesome-webfont.woff
728 ms
z_stat.php
2698 ms
counts.json
1858 ms
stat.htm
224 ms
core.php
1406 ms
9.gif
1211 ms
pic1.gif
1206 ms
yp.js
409 ms
CF.aspx
317 ms
shell_v2.js
568 ms
admin-ajax.php
947 ms
api.php
1879 ms
admin-ajax.php
816 ms
81c7a228gw1esq4dfu9r0g209w05kx6q.gif
770 ms
be09e3e0gw1f1fjywi9a1j20ic0ccdjd.jpg
126 ms
0069cEk8gw1eyk7uxbcp8j30e908vmxl.jpg
82 ms
dc02d06436c1d2462e3da1732ca78630.png
779 ms
a6f84856jw1f2n6u0pjjxj20ni0hswif.jpg
185 ms
dot.png
226 ms
27LSO9-750x485.png
839 ms
0069cEk8gw1exx3pcaosxj30xc18gwm8-690x500.jpg
292 ms
01-375x250.jpg
281 ms
app.gif
929 ms
logger.js
286 ms
bds_s_v2.js
832 ms
index.htm
996 ms
admin-ajax.php
714 ms
admin-ajax.php
700 ms
bdsstyle.css
272 ms
index.htm
914 ms
lifan.moe SEO score
N/A
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifan.moe 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), while the claimed language is Chinese. Our system also found out that Lifan.moe 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.
lifan.moe
Open Graph description is not detected on the main page of Lifan. 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: