45.4 sec in total
8.1 sec
36.6 sec
687 ms
Visit leeseo.cn now to see the best up-to-date Leeseo content and also check out these interesting facts you probably never knew about leeseo.cn
老李seo博客专注于分享seo基础教程培训,网站seo优化技术,解答SEO问题,让新手从零基础开始学习SEO优化技术,以及全网营销的自媒体博客。
Visit leeseo.cnWe analyzed Leeseo.cn page load time and found that the first response time was 8.1 sec and then it took 37.3 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.
leeseo.cn performance score
8101 ms
1053 ms
835 ms
2367 ms
1691 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 39% of them (27 requests) were addressed to the original Leeseo.cn, 10% (7 requests) were made to Cpro.baidustatic.com and 7% (5 requests) were made to T10.baidu.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source T10.baidu.com.
Page size can be reduced by 643.0 kB (46%)
1.4 MB
767.1 kB
In fact, the total size of Leeseo.cn main page is 1.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. 45% of websites need less resources to load. Javascripts take 574.6 kB which makes up the majority of the site volume.
Potential reduce by 45.4 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 45.4 kB or 74% of the original size.
Potential reduce by 33.5 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. Leeseo images are well optimized though.
Potential reduce by 382.2 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 382.2 kB or 67% of the original size.
Potential reduce by 181.9 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. Leeseo.cn needs all CSS files to be minified and compressed as it can save up to 181.9 kB or 84% of the original size.
Number of requests can be reduced by 28 (42%)
66
38
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leeseo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.leeseo.cn
8101 ms
wp-emoji-release.min.js
1053 ms
settings.css
835 ms
captions.php
2367 ms
bootstrap.min.css
1691 ms
font-awesome.min.css
885 ms
main.css
719 ms
logo2.png
1258 ms
002.jpg
2100 ms
a002.jpg
1993 ms
group.png
471 ms
360x300.jpg
14821 ms
c.js
1023 ms
weixin.png
2324 ms
jquery.themepunch.plugins.min.js
2434 ms
jquery.themepunch.revolution.min.js
2952 ms
jquery.min.js
4418 ms
bootstrap.min.js
6174 ms
loader.js
2604 ms
wp-embed.min.js
2543 ms
ecqm
1502 ms
fontawesome-webfont.woff
1279 ms
hm.js
4361 ms
stat.php
2035 ms
ecqm
669 ms
stat.htm
173 ms
core.php
1035 ms
adx.php
1181 ms
u=256680256,3411816341&fm=76
3391 ms
u=988591878,4277450711&fm=76
2098 ms
u=984761852,1183094972&fm=76
8438 ms
bg.png
522 ms
reduce_bd-logo1_oper.png
540 ms
u=3141504045,3714176021&fm=76
1030 ms
u=936920523,4220572131&fm=76
19621 ms
u=910505649,1254092554&fm=76
6583 ms
u=1051874307,4223640813&fm=76
3900 ms
u=1718438407,2682395325&fm=76
19619 ms
u=1163540569,58621430&fm=76
4291 ms
u=694406557,3955185580&fm=76
3315 ms
u=1372463888,1598415683&fm=76
3309 ms
u=633426203,3703652171&fm=76
6903 ms
9.gif
834 ms
pic.gif
1807 ms
main.js
749 ms
app.gif
1802 ms
hm.gif
326 ms
hammer.min.js
822 ms
lazyload.min.js
521 ms
signpop.js
498 ms
a52e72ac0ca9e225bad3b51bf4f057eb
240 ms
avatar-default.png
542 ms
thumbnail.png
519 ms
QQ%E5%9B%BE%E7%89%8720151126154505-220x69.png
566 ms
1-1506031520023W-220x150.gif
547 ms
20140308233922_33935-217x150.jpg
532 ms
u19188272064265685811fm21gp0-220x132.jpg
755 ms
5fdf8db1cb134954e00c682e544e9258d1094a6e-154x150.jpg
1008 ms
59ac7db8b5fda64741a131fa1236d9be
212 ms
0a06645114601036bfb9265256caf23e
229 ms
button_111.gif
240 ms
closefeedback.min.js
484 ms
o.htm
836 ms
reduce_promotion_oper.png
495 ms
bd_logo.png
499 ms
bg_rb.png
506 ms
hm.gif
664 ms
wh.js
732 ms
ac.js
516 ms
fp.htm
610 ms
leeseo.cn SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leeseo.cn 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 Leeseo.cn 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.
leeseo.cn
Open Graph description is not detected on the main page of Leeseo. 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: