Tools & Wizards About Us
runyes.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

runyes.com

宁波蓝野医疗器械有限公司-口扫宝,灭菌器

Page Load Speed

59.6 sec in total

First Response

9.6 sec

Resources Loaded

50 sec

Page Rendered

111 ms

runyes.com screenshot

About Website

Click here to check amazing Runyes content for France. Otherwise, check out these important facts you probably never knew about runyes.com

宁波蓝野医疗器械有限公司是一家专业研制生产医疗器械的高新技术企业，专注于口腔设备。

Visit runyes.com

Key Findings

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

Performance Metrics

runyes.com performance score

0

Network Requests Diagram

runyes.com

9567 ms

home.css

10299 ms

AC_RunActiveContent.js

9403 ms

jquery.min.js

19655 ms

jquery.hoverIntent.minified.js

986 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that all of those requests were addressed to Runyes.com 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 Runyes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.7 kB (76%)

Content Size

53.9 kB

After Optimization

13.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Runyes.com main page is 53.9 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 24.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 5.7 kB

  • Original 8.2 kB
  • After minification 7.6 kB
  • After compression 2.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. 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 5.7 kB or 70% of the original size.

JavaScript Optimization

-69%

Potential reduce by 14.9 kB

  • Original 21.6 kB
  • After minification 16.5 kB
  • After compression 6.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 14.9 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 20.1 kB

  • Original 24.1 kB
  • After minification 19.4 kB
  • After compression 4.0 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. Runyes.com needs all CSS files to be minified and compressed as it can save up to 20.1 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

9

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

runyes.com

runyes.com

9567 ms

home.css

home.css

10299 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

9403 ms

jquery.min.js

jquery.min.js

19655 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

986 ms

jquery.nav.js

jquery.nav.js

4372 ms

myfocus-1.2.0.full.js

myfocus-1.2.0.full.js

11138 ms

ajax.js

ajax.js

20397 ms

01117-001.jpg

01117-001.jpg

509 ms

logo.jpg

logo.jpg

19982 ms

01117-007.jpg

01117-007.jpg

19983 ms

01117-030.jpg

01117-030.jpg

15062 ms

nav_1.jpg

nav_1.jpg

19983 ms

nav_2.jpg

nav_2.jpg

16031 ms

nav_3.jpg

nav_3.jpg

19983 ms

nav_4.jpg

nav_4.jpg

19984 ms

nav_5.jpg

nav_5.jpg

19983 ms

nav_6.jpg

nav_6.jpg

19983 ms

top-02-004.jpg

top-02-004.jpg

19984 ms

%E7%89%99%E6%A4%852.jpg

%E7%89%99%E6%A4%852.jpg

19983 ms

04.jpg

04.jpg

19984 ms

2015081312563126265.jpg

2015081312563126265.jpg

19983 ms

2014061716213439030.jpg

2014061716213439030.jpg

19984 ms

01117-008.jpg

01117-008.jpg

19983 ms

LXWM.jpg

LXWM.jpg

19984 ms

yayi-22-D-up-0.jpg

yayi-22-D-up-0.jpg

19984 ms

%E5%A3%B0%E6%98%8E.jpg

%E5%A3%B0%E6%98%8E.jpg

19984 ms

mF_classicHB.css

mF_classicHB.css

15794 ms

mF_classicHB.js

mF_classicHB.js

19998 ms

SEO Factors

runyes.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runyes.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 Runyes.com 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

runyes.com

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