Tools & Wizards About Us
lelink.ecare365.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lelink.ecare365.com

联想看家宝服务官网

Page Load Speed

21.5 sec in total

First Response

1.2 sec

Resources Loaded

20.1 sec

Page Rendered

235 ms

lelink.ecare365.com screenshot

About Website

Click here to check amazing Lelink Ecare 365 content for China. Otherwise, check out these important facts you probably never knew about lelink.ecare365.com

无论身处何处，您都可以通过联想看家宝服务随时方便的了解家中的情况，捕捉您关心的事情，获得安心的生活。

Visit lelink.ecare365.com

Key Findings

We analyzed Lelink.ecare365.com page load time and found that the first response time was 1.2 sec and then it took 20.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

lelink.ecare365.com performance score

0

Network Requests Diagram

lelink.ecare365.com

1162 ms

style.css

964 ms

css.css

1454 ms

setupGuide.css

477 ms

jquery-1.6.min.js

1637 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 74% of them (53 requests) were addressed to the original Lelink.ecare365.com, 14% (10 requests) were made to Qiao.baidu.com and 4% (3 requests) were made to S.qiao.baidu.com. The less responsive or slowest element that took the longest time to load (12.3 sec) belongs to the original domain Lelink.ecare365.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 229.3 kB (24%)

Content Size

944.8 kB

After Optimization

715.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 10.2 kB

  • Original 14.8 kB
  • After minification 12.9 kB
  • After compression 4.6 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. This page needs HTML code to be minified as it can gain 1.9 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 10.2 kB or 69% of the original size.

Image Optimization

-8%

Potential reduce by 56.6 kB

  • Original 714.9 kB
  • After minification 658.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. Lelink Ecare 365 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 72.6 kB

  • Original 106.8 kB
  • After minification 99.7 kB
  • After compression 34.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 72.6 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 89.8 kB

  • Original 108.2 kB
  • After minification 88.9 kB
  • After compression 18.4 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. Lelink.ecare365.com needs all CSS files to be minified and compressed as it can save up to 89.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (32%)

Requests Now

71

After Optimization

48

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lelink.ecare365.com

lelink.ecare365.com

1162 ms

style.css

style.css

964 ms

css.css

css.css

1454 ms

setupGuide.css

setupGuide.css

477 ms

jquery-1.6.min.js

jquery-1.6.min.js

1637 ms

common.js

common.js

536 ms

rating.min.js

rating.min.js

607 ms

logo.gif

logo.gif

266 ms

nav_left.jpg

nav_left.jpg

302 ms

nav_bg.jpg

nav_bg.jpg

272 ms

nav_line.jpg

nav_line.jpg

274 ms

nav_right.jpg

nav_right.jpg

265 ms

slide_btn_cur.gif

slide_btn_cur.gif

263 ms

slide_btn_normal.gif

slide_btn_normal.gif

502 ms

banner_02.jpg

banner_02.jpg

10010 ms

banner_01.jpg

banner_01.jpg

8781 ms

banner_04.jpg

banner_04.jpg

7278 ms

banner_03.jpg

banner_03.jpg

3318 ms

bit.gif

bit.gif

1942 ms

slide_l_02.png

slide_l_02.png

2211 ms

slide_l_03.png

slide_l_03.png

2542 ms

login_bg.png

login_bg.png

2446 ms

validatepng.php

validatepng.php

2698 ms

mod_btn.png

mod_btn.png

4189 ms

download_bg.png

download_bg.png

3173 ms

android_download.png

android_download.png

3412 ms

iphone_download.png

iphone_download.png

3613 ms

code.jpg

code.jpg

3678 ms

ios.jpg

ios.jpg

3901 ms

tips.png

tips.png

4162 ms

tips1.png

tips1.png

4202 ms

gonggao_bg.png

gonggao_bg.png

4442 ms

left.png

left.png

4497 ms

right-click.png

right-click.png

4485 ms

coll.jpg

coll.jpg

5649 ms

flow-chart1.png

flow-chart1.png

4755 ms

pic1.gif

pic1.gif

7498 ms

btn-next.png

btn-next.png

5030 ms

flow-chart2.png

flow-chart2.png

6160 ms

pic2.gif

pic2.gif

7587 ms

btn-pre.png

btn-pre.png

6450 ms

flow-chart3.png

flow-chart3.png

7059 ms

pic3.gif

pic3.gif

7961 ms

h.js

h.js

2284 ms

flow-chart4.png

flow-chart4.png

7959 ms

pic4.gif

pic4.gif

12306 ms

btn-thanks.png

btn-thanks.png

7905 ms

popup_bj.png

popup_bj.png

8013 ms

ico_close.jpg

ico_close.jpg

8153 ms

ico_pre.jpg

ico_pre.jpg

8200 ms

21.gif

21.gif

648 ms

b.js

b.js

847 ms

hm.gif

hm.gif

1530 ms

ico_bg.jpg

ico_bg.jpg

7857 ms

ico_right.jpg

ico_right.jpg

6328 ms

bsl.js

bsl.js

3038 ms

Enter.php

Enter.php

801 ms

main_icon_invite_mess_api.js

main_icon_invite_mess_api.js

6186 ms

main.css

main.css

668 ms

fix.css

fix.css

2587 ms

version.js

version.js

2101 ms

right.png

right.png

702 ms

left-click.png

left-click.png

271 ms

01.jpg

01.jpg

5100 ms

m-webim-lite.css

m-webim-lite.css

434 ms

m-webim-lite.js

m-webim-lite.js

3410 ms

Refresh.php

Refresh.php

402 ms

iconbg.jpg

iconbg.jpg

589 ms

icon.png

icon.png

1960 ms

icon_close.png

icon_close.png

2542 ms

stat.gif

stat.gif

886 ms

main.css

main.css

610 ms

SEO Factors

lelink.ecare365.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GBK

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

Social Sharing Optimization

lelink.ecare365.com

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