Tools & Wizards About Us
leguoiphone5.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

leguoiphone5.com

Page Load Speed

13.1 sec in total

First Response

923 ms

Resources Loaded

12 sec

Page Rendered

204 ms

leguoiphone5.com screenshot

About Website

Welcome to leguoiphone5.com homepage info - get ready to check Leguoiphone 5 best content right away, or after learning these important things about leguoiphone5.com

乐果i6手机：乐果iphone6手机将扼杀iPhone6于摇篮，乐果iPhone6曝光，乐果iPhone6不仅看上去很美，而且很实在，乐果iPhone6上市，乐果iphone6plus敬请期待！乐果iphone5s详细参数，乐果手机官网

Visit leguoiphone5.com

Key Findings

We analyzed Leguoiphone5.com page load time and found that the first response time was 923 ms and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

leguoiphone5.com performance score

0

Network Requests Diagram

leguoiphone5.com

923 ms

0f000nUXY-lnvwvEo9bcq0.jpg

1387 ms

15033830.js

1091 ms

o.js

926 ms

0f0007iyjEcKJHc0FI8jJ0.jpg

1381 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Leguoiphone5.com, 23% (6 requests) were made to Pagead2.googlesyndication.com and 15% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Bdimg.share.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.0 kB (31%)

Content Size

374.2 kB

After Optimization

259.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Leguoiphone5.com main page is 374.2 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. 25% of websites need less resources to load. Javascripts take 216.8 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 7.7 kB

  • Original 12.6 kB
  • After minification 12.2 kB
  • After compression 4.8 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 7.7 kB or 62% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 144.8 kB
  • After minification 144.8 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. Leguoiphone 5 images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 107.3 kB

  • Original 216.8 kB
  • After minification 216.7 kB
  • After compression 109.6 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 107.3 kB or 49% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (48%)

Requests Now

25

After Optimization

13

  • AJAX
  • Images
  • JavaScript

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leguoiphone 5. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

leguoiphone5.com

leguoiphone5.com

923 ms

0f000nUXY-lnvwvEo9bcq0.jpg

0f000nUXY-lnvwvEo9bcq0.jpg

1387 ms

15033830.js

15033830.js

1091 ms

o.js

o.js

926 ms

0f0007iyjEcKJHc0FI8jJ0.jpg

0f0007iyjEcKJHc0FI8jJ0.jpg

1381 ms

0f000PoxpmwWxDtpOn0Qa6.jpg

0f000PoxpmwWxDtpOn0Qa6.jpg

3087 ms

icon_9.gif

icon_9.gif

829 ms

gcvm

gcvm

4038 ms

shell_v2.js

shell_v2.js

849 ms

bds_s_v2.js

bds_s_v2.js

6210 ms

adsbygoogle.js

adsbygoogle.js

293 ms

logger.js

logger.js

615 ms

ca-pub-6344370739028394.js

ca-pub-6344370739028394.js

210 ms

zrt_lookup.html

zrt_lookup.html

115 ms

show_ads_impl.js

show_ads_impl.js

115 ms

ads

ads

243 ms

osd.js

osd.js

22 ms

m_js_controller.js

m_js_controller.js

75 ms

abg.js

abg.js

99 ms

favicon

favicon

101 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

101 ms

mobile_unified_button_icon_white.png

mobile_unified_button_icon_white.png

70 ms

s

s

43 ms

x_button_blue2.png

x_button_blue2.png

31 ms

j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js

j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js

11 ms

activeview

activeview

274 ms

SEO Factors

leguoiphone5.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leguoiphone5.com 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 Leguoiphone5.com 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

leguoiphone5.com

Open Graph description is not detected on the main page of Leguoiphone 5. 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: