Tools & Wizards About Us
morsh.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

morsh.cn

宁波墨西科技有限公司_石墨烯_锂电池

Page Load Speed

41.9 sec in total

First Response

7.3 sec

Resources Loaded

34.4 sec

Page Rendered

218 ms

morsh.cn screenshot

About Website

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

石墨烯，墨西科技，宁波墨西，锂电池，石墨烯锂电池

Visit morsh.cn

Key Findings

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

Performance Metrics

morsh.cn performance score

0

Network Requests Diagram

7273 ms

base.min.css

6938 ms

4001.min.css

2622 ms

bannerAnimation.min.css

4312 ms

navStyle0.min.css

6695 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 10% of them (4 requests) were addressed to the original Morsh.cn, 57% (24 requests) were made to 0.ss.faisys.com and 33% (14 requests) were made to 6954580.s21i-6.faiusr.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source 6954580.s21i-6.faiusr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (40%)

Content Size

2.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Morsh.cn main page is 2.8 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. 30% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 51.3 kB

  • Original 63.4 kB
  • After minification 62.1 kB
  • After compression 12.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.3 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 151.8 kB

  • Original 1.5 MB
  • After minification 1.4 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. Morsh images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 664.6 kB

  • Original 914.3 kB
  • After minification 914.3 kB
  • After compression 249.7 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 664.6 kB or 73% of the original size.

CSS Optimization

-92%

Potential reduce by 235.8 kB

  • Original 255.9 kB
  • After minification 255.9 kB
  • After compression 20.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. Morsh.cn needs all CSS files to be minified and compressed as it can save up to 235.8 kB or 92% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Morsh. 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

7273 ms

base.min.css

base.min.css

6938 ms

4001.min.css

4001.min.css

2622 ms

bannerAnimation.min.css

bannerAnimation.min.css

4312 ms

navStyle0.min.css

navStyle0.min.css

6695 ms

floatBtn1.min.css

floatBtn1.min.css

2636 ms

ABUIABAEGAAg_7fsrgUosOCfiQcwoQE4SA.png

ABUIABAEGAAg_7fsrgUosOCfiQcwoQE4SA.png

1448 ms

jquery-core.min.js

jquery-core.min.js

5336 ms

jquery-mousewheel.min.js

jquery-mousewheel.min.js

3869 ms

fai.min.js

fai.min.js

5496 ms

jquery-ui-core.min.js

jquery-ui-core.min.js

8122 ms

site.min.js

site.min.js

11019 ms

1033.min.js

1033.min.js

5754 ms

ZeroClipboard.min.js

ZeroClipboard.min.js

5937 ms

ABUIABAEGAAgkL-xrgUotrit-QYwuAE4kQM.png

ABUIABAEGAAgkL-xrgUotrit-QYwuAE4kQM.png

18498 ms

ABUIABAEGAAgmL-xrgUomrvs-QUwuAE4kQM.png

ABUIABAEGAAgmL-xrgUomrvs-QUwuAE4kQM.png

20468 ms

ABUIABAEGAAgpL-xrgUovuTNsAUwuAE4kAM.png

ABUIABAEGAAgpL-xrgUovuTNsAUwuAE4kAM.png

13152 ms

ABUIABAEGAAgp7-xrgUoiebCpQcwuAE4kQM.png

ABUIABAEGAAgp7-xrgUoiebCpQcwuAE4kQM.png

20467 ms

ABUIABAEGAAgrr-xrgUomPDq-AcwuAE4kQM.png

ABUIABAEGAAgrr-xrgUomPDq-AcwuAE4kQM.png

1541 ms

ABUIABAEGAAgn7rrrgUo6N7MowIwggo44gI.png

ABUIABAEGAAgn7rrrgUo6N7MowIwggo44gI.png

111 ms

locater_Arrow2.png

locater_Arrow2.png

431 ms

topline.gif

topline.gif

417 ms

navleft.gif

navleft.gif

418 ms

line.png

line.png

417 ms

navright.gif

navright.gif

874 ms

statistics_h.jsp

statistics_h.jsp

1293 ms

ABUIABAEGAAg7J7xrgUomKHuuQUwtwE4kQM.png

ABUIABAEGAAg7J7xrgUomKHuuQUwtwE4kQM.png

127 ms

ABUIABAEGAAg8J7xrgUo-ObljwIwtwE4kQM.png

ABUIABAEGAAg8J7xrgUo-ObljwIwtwE4kQM.png

6888 ms

ABUIABAEGAAg8Z7xrgUo6ISatQEwtwE4kQM.png

ABUIABAEGAAg8Z7xrgUo6ISatQEwtwE4kQM.png

233 ms

ABUIABAEGAAg9Z7xrgUooIuZiwQwtwE4kQM.png

ABUIABAEGAAg9Z7xrgUooIuZiwQwtwE4kQM.png

341 ms

ABUIABAEGAAg957xrgUooNDnuAIwtwE4kQM.png

ABUIABAEGAAg957xrgUooNDnuAIwtwE4kQM.png

7029 ms

ABUIABAEGAAgprrrrgUok6aWlwUwggo44gI.png

ABUIABAEGAAgprrrrgUok6aWlwUwggo44gI.png

2205 ms

ABUIABAEGAAgtrrrrgUo_Jn0zAMwgwo44gI.png

ABUIABAEGAAgtrrrrgUo_Jn0zAMwgwo44gI.png

16974 ms

photoSwitchBg.png

photoSwitchBg.png

434 ms

left.png

left.png

435 ms

right.png

right.png

425 ms

sound_0_on.gif

sound_0_on.gif

424 ms

photoSlide.min.js

photoSlide.min.js

425 ms

imageEffect.min.js

imageEffect.min.js

425 ms

order_h.jsp

order_h.jsp

606 ms

backtotop.png

backtotop.png

795 ms

statistics_h.jsp

statistics_h.jsp

1616 ms

SEO Factors

morsh.cn 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 Morsh.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 Morsh.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

morsh.cn

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