Tools & Wizards About Us
lvye.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lvye.org

绿野自助户外活动网站 - lvyeorg

Page Load Speed

22.1 sec in total

First Response

3.8 sec

Resources Loaded

18.1 sec

Page Rendered

172 ms

lvye.org screenshot

About Website

Visit lvye.org now to see the best up-to-date Lvye content for Cambodia and also check out these interesting facts you probably never knew about lvye.org

首页

Visit lvye.org

Key Findings

We analyzed Lvye.org page load time and found that the first response time was 3.8 sec and then it took 18.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

lvye.org performance score

0

Network Requests Diagram

lvye.org

3795 ms

xoops.css

3264 ms

style.css

3726 ms

xoops.js

1601 ms

index.htm

1850 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 41% of them (9 requests) were addressed to the original Lvye.org, 45% (10 requests) were made to Tianqi.2345.com and 5% (1 request) were made to Img.webscan.360.cn. The less responsive or slowest element that took the longest time to load (8.6 sec) relates to the external source Tianqi.2345.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 361.3 kB (74%)

Content Size

489.8 kB

After Optimization

128.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lvye.org main page is 489.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. CSS take 207.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 40.6 kB

  • Original 50.2 kB
  • After minification 47.6 kB
  • After compression 9.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 40.6 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 2.3 kB

  • Original 27.9 kB
  • After minification 25.6 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.

JavaScript Optimization

-67%

Potential reduce by 136.2 kB

  • Original 204.7 kB
  • After minification 202.2 kB
  • After compression 68.5 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 136.2 kB or 67% of the original size.

CSS Optimization

-88%

Potential reduce by 182.2 kB

  • Original 207.0 kB
  • After minification 201.9 kB
  • After compression 24.8 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.org needs all CSS files to be minified and compressed as it can save up to 182.2 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (30%)

Requests Now

20

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 20 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

lvye.org

lvye.org

3795 ms

xoops.css

xoops.css

3264 ms

style.css

style.css

3726 ms

xoops.js

xoops.js

1601 ms

index.htm

index.htm

1850 ms

f1d3a586ca53dcd27f3fb68fc62d2cf6

f1d3a586ca53dcd27f3fb68fc62d2cf6

2326 ms

logo.gif

logo.gif

466 ms

spacer.gif

spacer.gif

235 ms

line_1.gif

line_1.gif

692 ms

line_2.gif

line_2.gif

693 ms

line_3.gif

line_3.gif

697 ms

TrojanInspect.aspx

TrojanInspect.aspx

782 ms

wea_plugin_widget_v20150401130731.css

wea_plugin_widget_v20150401130731.css

5764 ms

jquery.js

jquery.js

8577 ms

common2_v20160121165649.js

common2_v20160121165649.js

6096 ms

citySelectData.js

citySelectData.js

5741 ms

smallCityName.js

smallCityName.js

1979 ms

widget_v20141205141757.js

widget_v20141205141757.js

4616 ms

tianqiplugin

tianqiplugin

5870 ms

detect2013_plugin.php

detect2013_plugin.php

380 ms

w_day.png

w_day.png

671 ms

plugin-widget.png

plugin-widget.png

992 ms

SEO Factors

lvye.org SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    CN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lvye.org can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed language. Our system also found out that Lvye.org 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.

Social Sharing Optimization

lvye.org

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: