Tools & Wizards About Us
hfls.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hfls.cn

hfls.cn

Page Load Speed

83 sec in total

First Response

8.4 sec

Resources Loaded

71.4 sec

Page Rendered

3.2 sec

hfls.cn screenshot

About Website

Click here to check amazing Hfls content. Otherwise, check out these important facts you probably never knew about hfls.cn

庐生装饰始创于2004年,本土12年装饰老品牌.装饰二级资质, 0551-63628277/677.专注于合肥家庭装饰、装修装潢、办公室装修设计施工.合肥装饰装修公司排行榜十强

Visit hfls.cn

Key Findings

We analyzed Hfls.cn page load time and found that the first response time was 8.4 sec and then it took 74.6 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 were 70 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

hfls.cn performance score

0

Network Requests Diagram

hfls.cn

8350 ms

style.css

1901 ms

zhengli.css

896 ms

common.css

896 ms

jquery.js

6756 ms

Our browser made a total of 149 requests to load all elements on the main page. We found that 72% of them (107 requests) were addressed to the original Hfls.cn, 13% (19 requests) were made to Qiao.baidu.com and 7% (11 requests) were made to P3.qiao.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Hfls.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 259.2 kB (64%)

Content Size

402.8 kB

After Optimization

143.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hfls.cn main page is 402.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. 20% of websites need less resources to load. CSS take 114.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 78.9 kB

  • Original 92.4 kB
  • After minification 74.2 kB
  • After compression 13.4 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 18.1 kB, which is 20% 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 78.9 kB or 85% of the original size.

Image Optimization

-13%

Potential reduce by 12.9 kB

  • Original 101.8 kB
  • After minification 88.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. Obviously, Hfls needs image optimization as it can save up to 12.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 72.4 kB

  • Original 93.9 kB
  • After minification 62.0 kB
  • After compression 21.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 72.4 kB or 77% of the original size.

CSS Optimization

-83%

Potential reduce by 95.0 kB

  • Original 114.6 kB
  • After minification 95.5 kB
  • After compression 19.6 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. Hfls.cn needs all CSS files to be minified and compressed as it can save up to 95.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (60%)

Requests Now

75

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hfls.cn

hfls.cn

8350 ms

style.css

style.css

1901 ms

zhengli.css

zhengli.css

896 ms

common.css

common.css

896 ms

jquery.js

jquery.js

6756 ms

swfobject.js

swfobject.js

1371 ms

global.js

global.js

1815 ms

www.js

www.js

1818 ms

kefu.js

kefu.js

2701 ms

other.js

other.js

2247 ms

jcarousellite.min.js

jcarousellite.min.js

1836 ms

index.js

index.js

2204 ms

roll.js

roll.js

2294 ms

roll_a.js

roll_a.js

2575 ms

roll_b.js

roll_b.js

2301 ms

roll_c.js

roll_c.js

2286 ms

php.js

php.js

2510 ms

yanzheng.js

yanzheng.js

2732 ms

hm.js

hm.js

784 ms

index_bg.jpg

index_bg.jpg

12982 ms

header.gif

header.gif

633 ms

logo.gif

logo.gif

4477 ms

index_bg.gif

index_bg.gif

19747 ms

tel.png

tel.png

4219 ms

menubg.png

menubg.png

5191 ms

nava_a.gif

nava_a.gif

4135 ms

index_body_bg.gif

index_body_bg.gif

4770 ms

330.jpg

330.jpg

19745 ms

225.jpg

225.jpg

19745 ms

1.jpg

1.jpg

19746 ms

13.jpg

13.jpg

19747 ms

3.jpg

3.jpg

19747 ms

352.jpg

352.jpg

19746 ms

22.jpg

22.jpg

19747 ms

24.jpg

24.jpg

19749 ms

51405e1cca6ebfa5.jpg

51405e1cca6ebfa5.jpg

19750 ms

6332b54be76079d1.jpg

6332b54be76079d1.jpg

19753 ms

979137b6de223f0c.jpg

979137b6de223f0c.jpg

19754 ms

be6da5971c76d272.jpg

be6da5971c76d272.jpg

19753 ms

index.php

index.php

19753 ms

223.jpg

223.jpg

19758 ms

80.jpg

80.jpg

19758 ms

71.jpg

71.jpg

19760 ms

58.jpg

58.jpg

19760 ms

46.jpg

46.jpg

19759 ms

36.jpg

36.jpg

19764 ms

309.jpg

309.jpg

19765 ms

146.jpg

146.jpg

19767 ms

135.jpg

135.jpg

19773 ms

284.jpg

284.jpg

19773 ms

203.jpg

203.jpg

19774 ms

168.jpg

168.jpg

19780 ms

157.jpg

157.jpg

19780 ms

57.jpg

57.jpg

19781 ms

31.jpg

31.jpg

19735 ms

stat.php

stat.php

1709 ms

1.jpg

1.jpg

20133 ms

hm.gif

hm.gif

386 ms

b.js

b.js

854 ms

bsl.js

bsl.js

1076 ms

stat.htm

stat.htm

419 ms

core.php

core.php

1440 ms

Enter.php

Enter.php

820 ms

main_icon_invite_mess_api.js

main_icon_invite_mess_api.js

1752 ms

main.css

main.css

6434 ms

fix.css

fix.css

803 ms

version.js

version.js

1099 ms

413.jpg

413.jpg

19609 ms

127.jpg

127.jpg

19528 ms

332.jpg

332.jpg

20272 ms

m-webim-lite.css

m-webim-lite.css

329 ms

m-webim-lite.js

m-webim-lite.js

5032 ms

Refresh.php

Refresh.php

424 ms

stat.gif

stat.gif

376 ms

1.jpg

1.jpg

19912 ms

348.jpg

348.jpg

19558 ms

9.gif

9.gif

11567 ms

pic1.gif

pic1.gif

1213 ms

09.png

09.png

367 ms

4.png

4.png

9175 ms

icon.png

icon.png

1356 ms

4_right.png

4_right.png

1013 ms

4_close.png

4_close.png

1083 ms

06.png

06.png

2096 ms

mess-text.png

mess-text.png

1133 ms

06_normal.png

06_normal.png

1598 ms

mess.gif

mess.gif

1675 ms

06_send_normal.png

06_send_normal.png

4768 ms

btn.png

btn.png

3645 ms

Refresh.php

Refresh.php

565 ms

button_121.gif

button_121.gif

791 ms

346.jpg

346.jpg

19768 ms

Refresh.php

Refresh.php

1955 ms

340.jpg

340.jpg

18399 ms

338.jpg

338.jpg

19997 ms

332.jpg

332.jpg

19996 ms

344.jpg

344.jpg

19288 ms

334.jpg

334.jpg

19994 ms

342.jpg

342.jpg

19994 ms

336.jpg

336.jpg

19992 ms

258.png

258.png

19992 ms

489.jpg

489.jpg

19992 ms

486.jpg

486.jpg

19991 ms

268.jpg

268.jpg

19991 ms

266.jpg

266.jpg

19992 ms

78.jpg

78.jpg

19996 ms

75.jpg

75.jpg

19991 ms

528.jpg

528.jpg

19991 ms

133.png

133.png

20017 ms

127.jpg

127.jpg

20017 ms

572.jpg

572.jpg

20015 ms

837.jpg

837.jpg

20010 ms

641.jpg

641.jpg

20008 ms

633.jpg

633.jpg

20007 ms

788.jpg

788.jpg

20000 ms

570.jpg

570.jpg

19999 ms

580.jpg

580.jpg

19998 ms

604.jpg

604.jpg

19993 ms

646.jpg

646.jpg

19992 ms

625.jpg

625.jpg

19992 ms

53.png

53.png

19991 ms

385.jpg

385.jpg

19993 ms

app.gif

app.gif

1234 ms

213.jpg

213.jpg

19989 ms

Refresh.php

Refresh.php

566 ms

215.jpg

215.jpg

19998 ms

219.jpg

219.jpg

19997 ms

main.css

main.css

7571 ms

btn.png

btn.png

3369 ms

10.jpg

10.jpg

19998 ms

419.jpg

419.jpg

19997 ms

399.jpg

399.jpg

19982 ms

Refresh.php

Refresh.php

386 ms

984.jpg

984.jpg

19272 ms

Refresh.php

Refresh.php

1616 ms

prev.png

prev.png

7497 ms

next.png

next.png

6633 ms

tc_bnt.gif

tc_bnt.gif

16766 ms

iIndent.gif

iIndent.gif

10516 ms

design_team_name_bg.gif

design_team_name_bg.gif

6397 ms

brands_bg.gif

brands_bg.gif

6870 ms

footer_cont.gif

footer_cont.gif

20018 ms

Side_float_close.gif

Side_float_close.gif

7323 ms

float_bg.gif

float_bg.gif

7783 ms

float_s.gif

float_s.gif

11250 ms

Refresh.php

Refresh.php

388 ms

Refresh.php

Refresh.php

394 ms

Refresh.php

Refresh.php

1518 ms

Refresh.php

Refresh.php

445 ms

SEO Factors

hfls.cn SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hfls.cn can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Hfls.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.

Social Sharing Optimization

hfls.cn

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