49.1 sec in total
1.1 sec
47.3 sec
643 ms
Welcome to lvye.info homepage info - get ready to check Lvye best content for China right away, or after learning these important things about lvye.info
绿野户外论坛是国内驴友长期聚集活跃的户外运动社区,也是绿野网旗下主打的旅游论坛。绿野为用户提供户外知识资讯,自助游线路,旅行装备评测,活动发起,户外旅行保险等服务
Visit lvye.infoWe analyzed Lvye.info page load time and found that the first response time was 1.1 sec and then it took 48 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 36 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lvye.info performance score
1085 ms
5409 ms
956 ms
727 ms
2370 ms
Our browser made a total of 170 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lvye.info, 28% (47 requests) were made to Static03.lvye.com and 25% (42 requests) were made to Static02.lvye.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Static02.lvye.com.
Page size can be reduced by 429.5 kB (39%)
1.1 MB
663.3 kB
In fact, the total size of Lvye.info main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 582.7 kB which makes up the majority of the site volume.
Potential reduce by 79.5 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.5 kB or 80% of the original size.
Potential reduce by 10.9 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. Lvye images are well optimized though.
Potential reduce by 338.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 338.8 kB or 58% of the original size.
Potential reduce by 300 B
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. Lvye.info needs all CSS files to be minified and compressed as it can save up to 300 B or 67% of the original size.
Number of requests can be reduced by 42 (33%)
129
87
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lvye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
lvye.info
1085 ms
www.lvye.cn
5409 ms
jquery-1.8.3.min.js
956 ms
common.js
727 ms
messenger.js
2370 ms
skin.css
477 ms
forum.js
524 ms
portal.js
677 ms
header_20130101.css
722 ms
lvyepic_embed.js
783 ms
common.css
1013 ms
commond.css
974 ms
page2.css
974 ms
style.css
1067 ms
jquery-1.8.3.min.js
1885 ms
jquery.svg3dtagcloud.min.js
1199 ms
newheader.js
1204 ms
bdSlide.js
1354 ms
home.js
1366 ms
ds.js
737 ms
t.js
907 ms
m.js
762 ms
discuz_tips.js
686 ms
t.js
19380 ms
ip.lotour.com
1350 ms
zhuge-lastest.min.js
8506 ms
lvye_logo.png
250 ms
1459940556.53.jpg
9711 ms
1459160503.43.png
20085 ms
1459411966.67.jpg
15137 ms
1459746255.61.jpg
11020 ms
1460104340.73.jpg
14673 ms
1458900003.85.jpg
8471 ms
1459411089.04.jpg
11666 ms
1458900457.96.jpg
14490 ms
1458900667.62.jpg
11373 ms
1458901349.88.jpg
14452 ms
1458901296.49.jpg
12671 ms
1459135592.16.jpg
14577 ms
1459136578.64.png
17898 ms
1459135937.19.jpg
15454 ms
1459137114.57.jpg
18254 ms
1459137722.57.jpg
17951 ms
1459137368.87.jpg
15862 ms
1459321289.06.png
19927 ms
1459934646.77.jpg
18015 ms
1460010765.36.png
20077 ms
1460013048.16.jpg
20078 ms
1459395933.86.png
19310 ms
1460111790.8.jpg
19061 ms
1459846821.2.jpg
20078 ms
1459821333.93.jpg
20080 ms
1460093735.36.jpg
20080 ms
1460100213.11.jpg
20081 ms
1460098822.86.jpg
20082 ms
1459822688.93.jpg
20082 ms
1459823094.91.jpg
20081 ms
1460099237.82.jpg
20082 ms
1459823859.88.jpg
20082 ms
1459131510.75.jpg
20081 ms
1459132774.89.jpg
20082 ms
1460080623.79.jpg
20082 ms
1460009936.8.jpg
20083 ms
1460011630.88.jpg
20083 ms
down_7-4.png
237 ms
down_phone.png
236 ms
nav_icon.png
236 ms
activity_icon.png
238 ms
sixfoot.png
244 ms
trip_icon.png
464 ms
sixfoot_icon2.png
471 ms
ewmicon.jpg
466 ms
1458900094.7.jpeg
11130 ms
1459160421.05.jpg
10806 ms
1459135804.61.jpg
9121 ms
1459136796.0.jpg
11028 ms
1459138023.6.jpg
10303 ms
1459138424.05.jpg
13398 ms
1459158320.19.jpg
11675 ms
1459422264.31.jpg
18047 ms
1459481623.62.jpg
20079 ms
1459936959.32.jpg
15090 ms
1460011966.07.jpg
15872 ms
1459506115.34.jpg
16467 ms
1459235310.33.jpg
16631 ms
1460017795.35.jpg
17317 ms
1460096937.2.jpg
18138 ms
1459996545.31.jpg
19667 ms
1460019337.74.jpg
18724 ms
1459849509.73.jpg
20076 ms
1459851692.8.jpg
20077 ms
1459827259.53.jpg
20077 ms
1460094508.3.jpg
20080 ms
1459131681.45.jpg
20080 ms
1459131837.43.jpg
20080 ms
1459132123.33.jpg
20081 ms
1459132552.51.jpg
20081 ms
1460011511.22.jpg
20080 ms
1460012657.0.jpg
20081 ms
1460012719.86.jpg
20082 ms
1459132811.11.jpeg
20082 ms
1459133851.21.jpg
20083 ms
1459330881.39.jpg
20084 ms
1459143638.57.jpg
20084 ms
1459143476.25.jpg
20084 ms
1459221875.52.png
20084 ms
1459221271.75.jpg
20085 ms
lcrm
912 ms
0f0000oxkZwT1cL-KP9xP6.jpg
965 ms
lcrm
462 ms
0f000rzcPecs1aWvTxfuK6.jpg
543 ms
lcrm
452 ms
bg_hd.png
257 ms
0f000rgmXjTF5xKXoyuAof.jpg
735 ms
lcrm
448 ms
1802 ms
send_icon.png
247 ms
0f0007ZRkmBhEdEeqBwkf0.jpg
506 ms
lcrm
446 ms
0f000jlWjw7XR9NGPvRHl6.jpg
1579 ms
lcrm
445 ms
trouble.png
240 ms
0f000jPKoPspjLZCQTCVAs.jpg
1569 ms
slider_nav.jpg
240 ms
top_icon.jpg
239 ms
ewm2.jpg
242 ms
aboutus.png
241 ms
helpicon.png
253 ms
toolicon.png
481 ms
guanzhuicon.png
488 ms
hm.js
1297 ms
a2.js
932 ms
style.css
2119 ms
jquery-1.7.2.min.js
1714 ms
uvstat.js
166 ms
hm.gif
1238 ms
1457078378867342.jpg
1572 ms
webdig.js
5241 ms
1460012215.23.jpg
15018 ms
3
2890 ms
1460085128.17.jpg
12887 ms
1459146210.5.jpg
9870 ms
1459146893.4.jpg
9560 ms
1.gif
1485 ms
gs.js
4912 ms
1.gif
794 ms
1459332230.11.jpg
10744 ms
1459331677.55.jpg
9188 ms
1459143556.8.jpg
7402 ms
1459221433.75.jpg
9610 ms
gs.gif
5192 ms
hm.gif
1293 ms
referrer.js
5641 ms
getstatus.php
307 ms
1780 ms
1459995766.26.jpg
4007 ms
1460008468.98.jpg
2843 ms
1460014761.1.jpg
8205 ms
1460008617.86.jpg
9005 ms
1460009845.91.jpg
8831 ms
1460009761.48.jpg
6791 ms
1460013248.26.jpg
4789 ms
1460013888.83.jpg
4550 ms
1460008184.66.jpg
4917 ms
empty.js.gif
479 ms
o.htm
8308 ms
hm.gif
901 ms
ac.js
507 ms
wh.js
805 ms
fp.htm
604 ms
lvye.info SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lvye.info can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Lvye.info 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.
lvye.info
Open Graph description is not detected on the main page of Lvye. 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: