Tools & Wizards About Us
homr.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

homr.cn

淄博明锐网络工程有限公司-网站建设|网站制作|企业网站|做网站|网站优化|网站设计公司

Page Load Speed

73.5 sec in total

First Response

6 sec

Resources Loaded

66.6 sec

Page Rendered

829 ms

homr.cn screenshot

About Website

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

明锐网络成立于2011年，致力于为企业设计网站，开发软件，小程序等业务。

Visit homr.cn

Key Findings

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

Performance Metrics

homr.cn performance score

0

Network Requests Diagram

index.html

5999 ms

style80_common.css

6558 ms

style80_portal_index.css

10739 ms

jquery.min.js

15775 ms

jquery.SuperSlide.js

20188 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that all of those requests were addressed to Homr.cn and no external sources were called. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Homr.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.7 kB (60%)

Content Size

306.6 kB

After Optimization

123.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Homr.cn main page is 306.6 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 116.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 61.0 kB

  • Original 70.1 kB
  • After minification 60.0 kB
  • After compression 9.1 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 10.1 kB, which is 14% 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 61.0 kB or 87% of the original size.

Image Optimization

-18%

Potential reduce by 19.4 kB

  • Original 108.5 kB
  • After minification 89.2 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, Homr needs image optimization as it can save up to 19.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 7.9 kB

  • Original 11.4 kB
  • After minification 10.9 kB
  • After compression 3.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 7.9 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 94.5 kB

  • Original 116.5 kB
  • After minification 94.5 kB
  • After compression 22.1 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. Homr.cn needs all CSS files to be minified and compressed as it can save up to 94.5 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

19

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homr. According to our analytics all requests are already optimized.

Network Requests Diagram

index.html

index.html

5999 ms

style80_common.css

style80_common.css

6558 ms

style80_portal_index.css

style80_portal_index.css

10739 ms

jquery.min.js

jquery.min.js

15775 ms

jquery.SuperSlide.js

jquery.SuperSlide.js

20188 ms

nav.js

nav.js

2395 ms

rightUtilStyle.css

rightUtilStyle.css

2880 ms

rightUtilJs.js

rightUtilJs.js

3389 ms

logo.jpg

logo.jpg

14063 ms

1-160225152319615.jpg

1-160225152319615.jpg

20390 ms

1_0224093S143c.jpg

1_0224093S143c.jpg

982 ms

1-160224110620L2.jpg

1-160224110620L2.jpg

4646 ms

1-1602241112254b.png

1-1602241112254b.png

20389 ms

1-160224104213S2.png

1-160224104213S2.png

20390 ms

1_022410024345a.jpg

1_022410024345a.jpg

6352 ms

1-160226113G9606.png

1-160226113G9606.png

20390 ms

1-16022611364c05.png

1-16022611364c05.png

20391 ms

adlx1.jpg

adlx1.jpg

20393 ms

1-16022413421TF.png

1-16022413421TF.png

20393 ms

1-16022411520b09.png

1-16022411520b09.png

20395 ms

1-16022413292B51.png

1-16022413292B51.png

20396 ms

1-16022616214V05.jpg

1-16022616214V05.jpg

20397 ms

1-1602261J235631.jpg

1-1602261J235631.jpg

20397 ms

1-160225100G4O0.jpg

1-160225100G4O0.jpg

20398 ms

1-160225094P9A8.jpg

1-160225094P9A8.jpg

20399 ms

1-160225162153437.png

1-160225162153437.png

20399 ms

1-160225151220109.jpg

1-160225151220109.jpg

20399 ms

1-160225145034K2-lp.png

1-160225145034K2-lp.png

20399 ms

1-160226092943638.png

1-160226092943638.png

20398 ms

1-16022414241Q92.jpg

1-16022414241Q92.jpg

20399 ms

1-160226140P1413.png

1-160226140P1413.png

20400 ms

1-1602261331555H-lp.jpg

1-1602261331555H-lp.jpg

20400 ms

1-160226132531103-lp.gif

1-160226132531103-lp.gif

20401 ms

adlx2.jpg

adlx2.jpg

20400 ms

1-160226095K92X.png

1-160226095K92X.png

20400 ms

1-160224143444E8.png

1-160224143444E8.png

20401 ms

1-16022610331H57.png

1-16022610331H57.png

20400 ms

1-160226101R44T-lp.png

1-160226101R44T-lp.png

20401 ms

1-160226113401942.png

1-160226113401942.png

20401 ms

1-160224150343V2.png

1-160224150343V2.png

20401 ms

1-160226115Q33a.png

1-160226115Q33a.png

20400 ms

1-160226115201193.png

1-160226115201193.png

20400 ms

addh1.jpg

addh1.jpg

20392 ms

addx1.jpg

addx1.jpg

20408 ms

ftlogo.png

ftlogo.png

19940 ms

erweima.jpg

erweima.jpg

19744 ms

0_search.png

0_search.png

15471 ms

ticker.png

ticker.png

11023 ms

bg.jpg

bg.jpg

20004 ms

column.png

column.png

20003 ms

wonderful.png

wonderful.png

2436 ms

icon-hot.jpg

icon-hot.jpg

5772 ms

quote.png

quote.png

14542 ms

elevator-weixin.png

elevator-weixin.png

5868 ms

elevator-qq.jpg

elevator-qq.jpg

19995 ms

qq2.jpg

qq2.jpg

9854 ms

elevator-phone.jpg

elevator-phone.jpg

18914 ms

tel.jpg

tel.jpg

19992 ms

gotop.png

gotop.png

15083 ms

SEO Factors

homr.cn 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 Homr.cn 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 Homr.cn 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

homr.cn

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