Tools & Wizards About Us
qumei.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

qumei.com

曲美家居官网-专业定制家具,曲美橱柜,曲美定制衣柜,曲美家居商城

Page Load Speed

39.2 sec in total

First Response

2.3 sec

Resources Loaded

36.2 sec

Page Rendered

687 ms

qumei.com screenshot

About Website

Visit qumei.com now to see the best up-to-date Qumei content for China and also check out these interesting facts you probably never knew about qumei.com

曲美家居官网-全国1000+线下体验店，提供风格定制、橱柜定制、衣柜定制、全屋定制家具免费测量服务、0元设计。让您网上买家具更安全,更方便，更省钱！

Visit qumei.com

Key Findings

We analyzed Qumei.com page load time and found that the first response time was 2.3 sec and then it took 36.8 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 14 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

qumei.com performance score

0

Network Requests Diagram

qumei.com

2340 ms

global.css

1075 ms

page.css

1553 ms

fix.css

1788 ms

jquery-1.8.3.min.js

1853 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 80% of them (100 requests) were addressed to the original Qumei.com, 5% (6 requests) were made to Hm.baidu.com and 3% (4 requests) were made to Static.soperson.com. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Qumei.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 989.6 kB (17%)

Content Size

6.0 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qumei.com main page is 6.0 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. 40% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 75.5 kB

  • Original 93.0 kB
  • After minification 73.5 kB
  • After compression 17.5 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 19.4 kB, which is 21% 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 75.5 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 496.7 kB

  • Original 5.4 MB
  • After minification 4.9 MB

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. Qumei images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 209.2 kB

  • Original 295.1 kB
  • After minification 262.7 kB
  • After compression 86.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 209.2 kB or 71% of the original size.

CSS Optimization

-85%

Potential reduce by 208.2 kB

  • Original 244.9 kB
  • After minification 229.0 kB
  • After compression 36.7 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. Qumei.com needs all CSS files to be minified and compressed as it can save up to 208.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (31%)

Requests Now

108

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qumei.com

qumei.com

2340 ms

global.css

global.css

1075 ms

page.css

page.css

1553 ms

fix.css

fix.css

1788 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1853 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

952 ms

fun.js

fun.js

1430 ms

global.js

global.js

1278 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

1795 ms

jquery.mousewheel.js

jquery.mousewheel.js

1593 ms

jScrollPane.js

jScrollPane.js

2517 ms

lyc.js

lyc.js

1794 ms

lottery.css

lottery.css

1905 ms

fun.js

fun.js

2022 ms

jquery.mChange.js

jquery.mChange.js

2023 ms

jquery.mScroll.js

jquery.mScroll.js

2023 ms

10050003.js

10050003.js

1555 ms

clicki.min.js

clicki.min.js

3815 ms

1-1602230T035292.png

1-1602230T035292.png

17644 ms

pic18.png

pic18.png

270 ms

icon4.png

icon4.png

268 ms

arrow6.png

arrow6.png

342 ms

1-1602230T1122P.jpg

1-1602230T1122P.jpg

6584 ms

1-1602230T14TW.jpg

1-1602230T14TW.jpg

12620 ms

1-160225133200401.png

1-160225133200401.png

3129 ms

1-1601110Z3132I.png

1-1601110Z3132I.png

2964 ms

1-151209155123306.jpg

1-151209155123306.jpg

2288 ms

1-151026095603537.png

1-151026095603537.png

3543 ms

1-151026095614U6.png

1-151026095614U6.png

4777 ms

1-151026095635292.png

1-151026095635292.png

4598 ms

1-151026095A2L3.png

1-151026095A2L3.png

4580 ms

1-151026095JVE.png

1-151026095JVE.png

7686 ms

1-151026095P0S9.png

1-151026095P0S9.png

7379 ms

1-151026095Q1Y6.png

1-151026095Q1Y6.png

10822 ms

1-151026095R2193.png

1-151026095R2193.png

11013 ms

1-160201143553394.png

1-160201143553394.png

19791 ms

1-160201140015220.png

1-160201140015220.png

15378 ms

1-160201140042429.png

1-160201140042429.png

14504 ms

1-160201131234634.png

1-160201131234634.png

16760 ms

1-151024204400H7.png

1-151024204400H7.png

15075 ms

1-151024204412364.png

1-151024204412364.png

18808 ms

1-151024204425J1.png

1-151024204425J1.png

17308 ms

1-151024204441101.png

1-151024204441101.png

17471 ms

1-151024204459142.png

1-151024204459142.png

19166 ms

1-151024204512363.png

1-151024204512363.png

19723 ms

1-15102420452DW.png

1-15102420452DW.png

19790 ms

1-15102420453G37.png

1-15102420453G37.png

19789 ms

1-15102420460Y38.png

1-15102420460Y38.png

19789 ms

1-15102420461a13.png

1-15102420461a13.png

19790 ms

1-151024204635602.png

1-151024204635602.png

19790 ms

1-15102420464Oc.png

1-15102420464Oc.png

19792 ms

1-151024204F62I.png

1-151024204F62I.png

19791 ms

1-151024204G9106.png

1-151024204G9106.png

19791 ms

1-151024204I0948.png

1-151024204I0948.png

19792 ms

1-151024204J2195.png

1-151024204J2195.png

19792 ms

1-151024205221120.png

1-151024205221120.png

19792 ms

1-15102420503L22.png

1-15102420503L22.png

19792 ms

z_stat.php

z_stat.php

1281 ms

stat.htm

stat.htm

268 ms

core.php

core.php

1009 ms

1-151024205059520.png

1-151024205059520.png

19507 ms

9.gif

9.gif

953 ms

hm.js

hm.js

874 ms

hm.js

hm.js

949 ms

hm.js

hm.js

739 ms

talk99.css

talk99.css

550 ms

talk99.js

talk99.js

999 ms

1-151024205515A3.png

1-151024205515A3.png

19321 ms

hm.gif

hm.gif

376 ms

1-151024210514P7.png

1-151024210514P7.png

19153 ms

hm.gif

hm.gif

291 ms

app.gif

app.gif

1818 ms

hm.gif

hm.gif

288 ms

210f44c7d0fd4087aa507aa5738d0d3b.jpg

210f44c7d0fd4087aa507aa5738d0d3b.jpg

12015 ms

black85.png

black85.png

238 ms

s.gif

s.gif

281 ms

close.gif

close.gif

329 ms

icon6.png

icon6.png

238 ms

header_bg.png

header_bg.png

313 ms

logo.png

logo.png

1472 ms

select.png

select.png

237 ms

but.png

but.png

312 ms

icon1.png

icon1.png

502 ms

nav_bg_r.png

nav_bg_r.png

491 ms

nav_bg_l.png

nav_bg_l.png

492 ms

nav_bg1_r.png

nav_bg1_r.png

612 ms

nav_bg1_l.png

nav_bg1_l.png

901 ms

icon7.png

icon7.png

703 ms

ico9.png

ico9.png

703 ms

bg_gray.png

bg_gray.png

2399 ms

flw8.jpg

flw8.jpg

869 ms

arrow7.png

arrow7.png

941 ms

gray1.png

gray1.png

940 ms

dot4.png

dot4.png

1802 ms

black1.png

black1.png

2425 ms

icon3.png

icon3.png

1172 ms

black3.png

black3.png

1172 ms

arrow1.png

arrow1.png

1410 ms

black4.png

black4.png

2155 ms

icon2.png

icon2.png

2908 ms

s

s

7215 ms

ajax_login.php

ajax_login.php

16901 ms

track_proxy

track_proxy

790 ms

heatmap.js

heatmap.js

3861 ms

1-151024210642264.png

1-151024210642264.png

17972 ms

1-151024210I33W.png

1-151024210I33W.png

19023 ms

1-150FG93151I7.jpg

1-150FG93151I7.jpg

17468 ms

1-150G6133923W1.jpg

1-150G6133923W1.jpg

16739 ms

1-150G613393T94.jpg

1-150G613393T94.jpg

16372 ms

1-150G6133402A5.jpg

1-150G6133402A5.jpg

16258 ms

track_proxy

track_proxy

390 ms

1-150FG9331BO.jpg

1-150FG9331BO.jpg

12178 ms

1-15062415164H25.jpg

1-15062415164H25.jpg

12488 ms

1-151016155926101.png

1-151016155926101.png

11569 ms

1-15101616005K25.png

1-15101616005K25.png

9720 ms

1-150FQ35430232.png

1-150FQ35430232.png

10497 ms

1-1510161601264L.png

1-1510161601264L.png

17216 ms

1-160105100622236-lp.jpg

1-160105100622236-lp.jpg

12153 ms

1-1506301125333G.png

1-1506301125333G.png

7114 ms

888888888-150522134601M7.png

888888888-150522134601M7.png

7664 ms

1-150FG93342S1.jpg

1-150FG93342S1.jpg

7837 ms

arrow2.png

arrow2.png

5863 ms

track_proxy

track_proxy

350 ms

s

s

2742 ms

s

s

575 ms

SEO Factors

qumei.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 Qumei.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 Qumei.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

qumei.com

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