77.3 sec in total
221 ms
76.9 sec
244 ms
Click here to check amazing Lenet content for China. Otherwise, check out these important facts you probably never knew about lenet.cc
Visit lenet.ccWe analyzed Lenet.cc page load time and found that the first response time was 221 ms and then it took 77.1 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.
lenet.cc performance score
221 ms
330 ms
609 ms
304 ms
247 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 43% of them (36 requests) were addressed to the original Lenet.cc, 6% (5 requests) were made to Vip4.rwjfs.com and 5% (4 requests) were made to C.cnzz.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Mc.funshion.com.
Page size can be reduced by 400.6 kB (39%)
1.0 MB
626.4 kB
In fact, the total size of Lenet.cc main page is 1.0 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. 35% of websites need less resources to load. Images take 500.3 kB which makes up the majority of the site volume.
Potential reduce by 26.3 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 26.3 kB or 76% of the original size.
Potential reduce by 32.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. Lenet images are well optimized though.
Potential reduce by 272.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 272.2 kB or 67% of the original size.
Potential reduce by 69.6 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. Lenet.cc needs all CSS files to be minified and compressed as it can save up to 69.6 kB or 79% of the original size.
Number of requests can be reduced by 38 (48%)
79
41
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lenet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
lenet.cc
221 ms
www.lenet.cc
330 ms
yd.js
609 ms
style_14_common.css
304 ms
style_14_forum_index.css
247 ms
common.js
332 ms
forum.js
244 ms
index.css
219 ms
duilian.js
257 ms
youxiajiao.js
403 ms
jquery-1.8.3.min.js
477 ms
atj.js
412 ms
discuz_tips.js
515 ms
17795526.js
919 ms
appios.asp
19713 ms
logo.png
200 ms
c0c8513150a73a07cf8eff55be7bc50e.jpg
529 ms
18f2b6a374d09104665d175652914072.jpg
266 ms
0c25ad15a5f4aec496e094379ce64c5b.jpg
246 ms
2dd8c056186c8ce9eb4e440703cf2760.jpg
513 ms
7c977e70c7e4e108a3f86731e9ed67a9.jpg
321 ms
collapsed_no.gif
393 ms
common_2_icon.png
455 ms
common_37_icon.jpg
437 ms
forum.gif
494 ms
common_39_icon.png
540 ms
common_44_icon.png
618 ms
common_40_icon.jpg
605 ms
common_41_icon.png
657 ms
common_54_icon.png
707 ms
common_49_icon.png
693 ms
common_50_icon.png
684 ms
common_51_icon.png
701 ms
ad_close.gif
746 ms
security.png
831 ms
icon_9.gif
580 ms
pv.jpg
190 ms
search.png
199 ms
common_extra.js
170 ms
forum_speak.png
168 ms
i2.php
1921 ms
ha0000.php
1734 ms
save_log.php
398 ms
cpv_fm_r.js
1335 ms
rich_media_show_bottom_bg.gif
909 ms
iiadlogodl.png
2281 ms
couplet_close.jpg
5398 ms
ir.ashx
15259 ms
rv1.ashx
1328 ms
tj.yule8.net
1052 ms
js
1184 ms
stat.php
1827 ms
z_stat.php
2983 ms
close.png
3654 ms
v2.ashx
859 ms
logo.png
1264 ms
stat.htm
298 ms
core.php
839 ms
320.jpg
5939 ms
9.gif
3889 ms
pic.gif
1286 ms
scrolltop.png
215 ms
stat.htm
1192 ms
core.php
685 ms
fx.htm
396 ms
Wno.html
442 ms
z_stat.php
1002 ms
z_stat.php
606 ms
stat.htm
241 ms
core.php
208 ms
core.php
400 ms
stat.htm
233 ms
index
851 ms
app.gif
4839 ms
g-39024.v-66394
727 ms
statIwt_www_new-min.js
69 ms
vasd_pv.js
10 ms
javascript
1948 ms
reportVv.js
21 ms
core-min.js
78 ms
irt
2663 ms
6224 ms
mc
19887 ms
play
379 ms
lenet.cc SEO score
EN
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lenet.cc can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lenet.cc main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
lenet.cc
Open Graph description is not detected on the main page of Lenet. 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: