Tools & Wizards About Us
m.cc screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

m.cc

Page Load Speed

40.6 sec in total

First Response

5.3 sec

Resources Loaded

35 sec

Page Rendered

340 ms

m.cc screenshot

About Website

Visit m.cc now to see the best up-to-date M content and also check out these interesting facts you probably never knew about m.cc

米融网是一家域名抵押借贷平台,专为米农解决资金问题,开启米农致富之路,提供一个权威、安全、可靠的域名融资和投资理财平台

Visit m.cc

Key Findings

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

Performance Metrics

m.cc performance score

0

Network Requests Diagram

www.mirong.com

5253 ms

main.css

2133 ms

css.css

1427 ms

banzhu.css

959 ms

base.js

1270 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original M.cc, 8% (4 requests) were made to Wochou.com and 2% (1 request) were made to S5.cnzz.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Mirong.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.5 kB (26%)

Content Size

1.4 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M.cc main page is 1.4 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. 20% of websites need less resources to load. Images take 972.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 46.6 kB

  • Original 54.7 kB
  • After minification 37.3 kB
  • After compression 8.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 17.4 kB, which is 32% 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 46.6 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 42.5 kB

  • Original 972.6 kB
  • After minification 930.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. M images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 211.5 kB

  • Original 278.7 kB
  • After minification 213.5 kB
  • After compression 67.1 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 211.5 kB or 76% of the original size.

CSS Optimization

-81%

Potential reduce by 61.8 kB

  • Original 76.5 kB
  • After minification 69.9 kB
  • After compression 14.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. M.cc needs all CSS files to be minified and compressed as it can save up to 61.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (43%)

Requests Now

44

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.mirong.com

www.mirong.com

5253 ms

main.css

main.css

2133 ms

css.css

css.css

1427 ms

banzhu.css

banzhu.css

959 ms

base.js

base.js

1270 ms

jquery.min.js

jquery.min.js

2828 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1882 ms

WdatePicker.js

WdatePicker.js

2948 ms

kefu.css

kefu.css

1867 ms

jquery.js

jquery.js

10252 ms

scroll.js

scroll.js

2278 ms

slide.js

slide.js

2293 ms

z_stat.php

z_stat.php

764 ms

WdatePicker.css

WdatePicker.css

1677 ms

wpa_preview_a01.png

wpa_preview_a01.png

2727 ms

logo.png

logo.png

1446 ms

group.png

group.png

456 ms

foot_beian.gif

foot_beian.gif

1176 ms

shopnc.png

shopnc.png

8473 ms

bg_welcome.gif

bg_welcome.gif

522 ms

17_scrollpic_14126644359.jpg

17_scrollpic_14126644359.jpg

16104 ms

17_scrollpic_14158691387.jpg

17_scrollpic_14158691387.jpg

20337 ms

1_scrollpic_14140659935.jpg

1_scrollpic_14140659935.jpg

20338 ms

1_scrollpic_14001186429.jpg

1_scrollpic_14001186429.jpg

17170 ms

jindu.gif

jindu.gif

6140 ms

gonggao.png

gonggao.png

7205 ms

tender.jpg

tender.jpg

7811 ms

loan_repayment.jpg

loan_repayment.jpg

8879 ms

home-fix.gif

home-fix.gif

11072 ms

guanbixianxing.png

guanbixianxing.png

9341 ms

code.jpg

code.jpg

17283 ms

rz.jpg

rz.jpg

15093 ms

tou.jpg

tou.jpg

16834 ms

lishui.jpg

lishui.jpg

17935 ms

foot_logo.bmp

foot_logo.bmp

20334 ms

sm_realname.png

sm_realname.png

19899 ms

szfw_logo.jpg

szfw_logo.jpg

20334 ms

foot_wljc.gif

foot_wljc.gif

6485 ms

foot_110.gif

foot_110.gif

3475 ms

foot_jubao.gif

foot_jubao.gif

6932 ms

404.html

404.html

17891 ms

dot.png

dot.png

13238 ms

page_title.jpg

page_title.jpg

15902 ms

1.png

1.png

14641 ms

2.png

2.png

15099 ms

3.png

3.png

16761 ms

4.png

4.png

16078 ms

mvl.js

mvl.js

19600 ms

stat.htm

stat.htm

167 ms

core.php

core.php

1792 ms

404.html

404.html

15730 ms

9.gif

9.gif

762 ms

app.gif

app.gif

807 ms

SEO Factors

m.cc SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.cc 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 M.cc main page’s claimed encoding is gb2312. 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

m.cc

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