41.3 sec in total
1.3 sec
39.5 sec
464 ms
Visit lvye.cn now to see the best up-to-date Lvye content for China and also check out these interesting facts you probably never knew about lvye.cn
绿野网成立于1998年,是户外旅行活动信息网络平台,早期以BBS论坛形式出现,汇集了全国各地的户外爱好者,随着时代的变迁,目前主要业务是为户外旅行的商家、领队及出行用户提供活动发布、报名、出行的信息服务平台。
Visit lvye.cnWe analyzed Lvye.cn page load time and found that the first response time was 1.3 sec and then it took 39.9 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lvye.cn performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.3 s
68/100
25%
Value9.8 s
10/100
10%
Value70 ms
99/100
30%
Value0.018
100/100
15%
Value3.4 s
93/100
10%
1342 ms
6335 ms
1189 ms
846 ms
1687 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Lvye.cn, 57% (78 requests) were made to Static01.lvye.com and 22% (30 requests) were made to Bbs.lvye.cn. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Cbjslog.baidu.com.
Page size can be reduced by 492.1 kB (28%)
1.8 MB
1.3 MB
In fact, the total size of Lvye.cn main page is 1.8 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 79.7 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.7 kB or 82% of the original size.
Potential reduce by 147.3 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, Lvye needs image optimization as it can save up to 147.3 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 247.0 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 247.0 kB or 64% of the original size.
Potential reduce by 18.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. Lvye.cn needs all CSS files to be minified and compressed as it can save up to 18.1 kB or 76% of the original size.
Number of requests can be reduced by 32 (24%)
133
101
The browser has sent 133 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 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lvye.cn
1342 ms
bbs.lvye.cn
6335 ms
style_12_common.css
1189 ms
style_12_forum_index.css
846 ms
jquery-1.8.3.min.js
1687 ms
common.js
3622 ms
messenger.js
1747 ms
skin.css
1704 ms
m.js
1084 ms
forum.js
998 ms
header_20130101.css
1932 ms
lvyepic_embed.js
1499 ms
common.css
1590 ms
page2.css
2853 ms
newheader.js
1993 ms
t.js
352 ms
discuz_tips.js
477 ms
t.js
1470 ms
zhuge-lastest.min.js
5674 ms
102604mumqcjjmdku7nunb.jpg
7622 ms
lvye_logo.png
896 ms
down_7-4.png
423 ms
down_phone.png
559 ms
collapsed_no.gif
1164 ms
ad_close.gif
545 ms
ewmicon.jpg
1441 ms
gotop.png
879 ms
152930is70232vxu7hs2ha.jpg
12082 ms
111415tuehczpe9979aewi.jpg
5314 ms
092011e1ed4eejb314j616.jpg
6980 ms
152746t1kamm0z09260ia9.jpg
6916 ms
094542ccf2vagvngangxy3.jpg
6506 ms
common_7_icon.png
5809 ms
common_2_icon.png
6841 ms
common_351_icon.png
7789 ms
common_8_icon.png
7373 ms
common_12_icon.png
7453 ms
common_15_icon.png
7489 ms
common_354_icon.png
9191 ms
common_2547_icon.png
8842 ms
common_26_icon.png
8796 ms
common_1559_icon.png
8007 ms
common_19_icon.png
8811 ms
common_88_icon.png
8460 ms
common_1841_icon.png
9279 ms
common_2326_icon.png
9831 ms
common_1561_icon.png
10445 ms
common_359_icon.png
10783 ms
common_1923_icon.png
10809 ms
common_1868_icon.png
10438 ms
common_21_icon.png
10859 ms
common_3212_icon.png
10840 ms
common_355_icon.png
11544 ms
common_3194_icon.png
11350 ms
common_31_icon.png
11893 ms
common_3048_icon.png
11929 ms
common_2268_icon.png
12181 ms
common_361_icon.png
12471 ms
common_2243_icon.png
14377 ms
common_2196_icon.png
13741 ms
common_346_icon.png
14043 ms
common_1882_icon.png
13662 ms
gcrm
702 ms
0f0000-_pWC4NWCj_VTKs0.jpg
2924 ms
gcrm
393 ms
0f000KauWE1G3D6P3cD1ls.jpg
1081 ms
search.png
428 ms
pt_item.png
453 ms
common_extra.js
3036 ms
gcrm
353 ms
dot.gif
4713 ms
0f0002sMj3F7oy0mNXP81s.jpg
1094 ms
title.png
485 ms
titlebg.png
1119 ms
gcrm
399 ms
log
20175 ms
gcrm
342 ms
0f000nKXyzaOI_0qjAVu0f.gif
3950 ms
aboutus.png
472 ms
helpicon.png
482 ms
toolicon.png
608 ms
guanzhuicon.png
609 ms
hm.js
1595 ms
hm.gif
1606 ms
scrolltop.png
739 ms
referrer.js
2779 ms
getstatus.php
3928 ms
hm.gif
422 ms
empty.js.gif
377 ms
common_1881_icon.png
7911 ms
3
3988 ms
common_2249_icon.png
7791 ms
common_1884_icon.png
7254 ms
common_2194_icon.png
8640 ms
common_2245_icon.png
7287 ms
common_2251_icon.png
9047 ms
common_1939_icon.png
7759 ms
common_2207_icon.png
7002 ms
common_78_icon.png
7247 ms
common_345_icon.png
7835 ms
common_2244_icon.png
8861 ms
common_2166_icon.png
7248 ms
common_2208_icon.png
7164 ms
common_2206_icon.png
6995 ms
common_2247_icon.png
7861 ms
common_36_icon.png
7724 ms
common_2218_icon.png
8013 ms
common_2250_icon.png
7069 ms
common_2252_icon.png
6695 ms
common_1842_icon.png
6927 ms
common_2190_icon.png
6573 ms
common_2248_icon.png
6281 ms
common_2253_icon.png
6222 ms
common_1830_icon.png
6343 ms
common_2014_icon.png
9541 ms
common_2195_icon.png
6065 ms
common_2221_icon.png
6024 ms
common_2741_icon.png
6465 ms
common_2696_icon.png
7540 ms
common_2681_icon.png
5822 ms
common_2682_icon.png
5624 ms
common_2683_icon.png
5864 ms
common_1872_icon.png
6289 ms
common_1892_icon.png
5321 ms
common_2473_icon.png
5178 ms
common_2476_icon.png
5637 ms
common_2518_icon.png
6103 ms
common_2725_icon.png
6168 ms
common_366_icon.png
6196 ms
common_2414_icon.png
6087 ms
common_365_icon.png
5836 ms
common_350_icon.png
7326 ms
o.htm
2716 ms
hm.gif
1632 ms
ac.js
1696 ms
wh.js
2978 ms
fp.htm
614 ms
lvye.cn accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lvye.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lvye.cn SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document doesn't use legible font sizes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lvye.cn 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.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.
lvye.cn
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: