Tools & Wizards About Us
jme.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

jme.com

大圆银泰

Page Load Speed

54.3 sec in total

First Response

8.4 sec

Resources Loaded

38.5 sec

Page Rendered

7.4 sec

jme.com screenshot

About Website

Click here to check amazing Jme content for China. Otherwise, check out these important facts you probably never knew about jme.com

Visit jme.com

Key Findings

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

Performance Metrics

jme.com performance score

0

Network Requests Diagram

jme.com

8437 ms

index.css

4548 ms

jquery.min.js

12673 ms

index.js

1277 ms

layout.js

426 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 62% of them (38 requests) were addressed to the original Jme.com, 20% (12 requests) were made to Img.jme.com and 5% (3 requests) were made to Sobot.com. The less responsive or slowest element that took the longest time to load (20.8 sec) relates to the external source Img.jme.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.4 kB (42%)

Content Size

131.1 kB

After Optimization

75.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Jme.com main page is 131.1 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. 15% of websites need less resources to load. Images take 79.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.1 kB

  • Original 32.0 kB
  • After minification 29.6 kB
  • After compression 7.9 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 24.1 kB or 75% of the original size.

Image Optimization

-21%

Potential reduce by 17.0 kB

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

JavaScript Optimization

-72%

Potential reduce by 14.3 kB

  • Original 19.9 kB
  • After minification 16.0 kB
  • After compression 5.6 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.3 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (14%)

Requests Now

49

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jme.com

jme.com

8437 ms

index.css

index.css

4548 ms

jquery.min.js

jquery.min.js

12673 ms

index.js

index.js

1277 ms

layout.js

layout.js

426 ms

pc.min.js

pc.min.js

2415 ms

20150909153917889222139.jpg

20150909153917889222139.jpg

19528 ms

201603241058172119310953.jpg

201603241058172119310953.jpg

19507 ms

20160317095236904781737.jpg

20160317095236904781737.jpg

18241 ms

20160204225300495301861.jpg

20160204225300495301861.jpg

20760 ms

20160108153545792839861.jpg

20160108153545792839861.jpg

20760 ms

2016010815575068965153.jpg

2016010815575068965153.jpg

19321 ms

201603241428461886924842.jpg

201603241428461886924842.jpg

20758 ms

201603091140481289871236.jpg

201603091140481289871236.jpg

20759 ms

201603011511541851945726.jpg

201603011511541851945726.jpg

20758 ms

20160226115248101868424.jpg

20160226115248101868424.jpg

20758 ms

201601221603001218234115.jpg

201601221603001218234115.jpg

20758 ms

20160111095758334230998.jpg

20160111095758334230998.jpg

20758 ms

logo.jpg

logo.jpg

1546 ms

search.png

search.png

3508 ms

block_bg.jpg

block_bg.jpg

419 ms

new.jpg

new.jpg

414 ms

new2.jpg

new2.jpg

417 ms

vid_bg.jpg

vid_bg.jpg

808 ms

new2.png

new2.png

810 ms

ios.png

ios.png

5231 ms

hot.jpg

hot.jpg

1198 ms

ios2.jpg

ios2.jpg

2345 ms

dowm.png

dowm.png

3242 ms

rl_pic.jpg

rl_pic.jpg

2016 ms

rl_bg.jpg

rl_bg.jpg

2423 ms

rl_more.jpg

rl_more.jpg

2749 ms

kx_tle.jpg

kx_tle.jpg

2855 ms

rl_pic2.jpg

rl_pic2.jpg

3204 ms

wx_two11.jpg

wx_two11.jpg

8450 ms

copy_icoh.jpg

copy_icoh.jpg

3640 ms

copy_icoh2.jpg

copy_icoh2.jpg

6747 ms

copy_icoh7.jpg

copy_icoh7.jpg

5791 ms

copy_icoh5.jpg

copy_icoh5.jpg

3959 ms

copy_icoh3.jpg

copy_icoh3.jpg

4062 ms

copy_icoh6.jpg

copy_icoh6.jpg

4388 ms

copy_icoh10.jpg

copy_icoh10.jpg

11471 ms

fx168.jpg

fx168.jpg

8304 ms

nicemore.jpg

nicemore.jpg

5619 ms

payb.png

payb.png

13068 ms

jtyh.jpg

jtyh.jpg

13579 ms

wx_two.jpg

wx_two.jpg

13100 ms

erwm.jpg

erwm.jpg

8751 ms

copy_bt.png

copy_bt.png

8862 ms

fixCont.png

fixCont.png

10429 ms

wxkf.jpg

wxkf.jpg

12656 ms

refresh.js

refresh.js

11492 ms

stat.php

stat.php

2079 ms

stat.htm

stat.htm

184 ms

core.php

core.php

861 ms

9.gif

9.gif

3942 ms

hm.js

hm.js

1137 ms

load.action

load.action

599 ms

zhichichatBtnBg.png

zhichichatBtnBg.png

1510 ms

hm.gif

hm.gif

761 ms

app.gif

app.gif

1069 ms

SEO Factors

jme.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 Jme.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 Jme.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

jme.com

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