73.1 sec in total
2.5 sec
66 sec
4.6 sec
Welcome to jmcity.com homepage info - get ready to check Jmcity best content right away, or after learning these important things about jmcity.com
首页
Visit jmcity.comWe analyzed Jmcity.com page load time and found that the first response time was 2.5 sec and then it took 70.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 58 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
jmcity.com performance score
2518 ms
14974 ms
11398 ms
10159 ms
8378 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 75% of them (87 requests) were addressed to the original Jmcity.com, 7% (8 requests) were made to Bbs.jmcity.com and 3% (4 requests) were made to Static.js.weather.com.cn. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Jmcity.com.
Page size can be reduced by 356.1 kB (50%)
718.1 kB
362.0 kB
In fact, the total size of Jmcity.com main page is 718.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. 20% of websites need less resources to load. Images take 296.6 kB which makes up the majority of the site volume.
Potential reduce by 84.7 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 84.7 kB or 82% of the original size.
Potential reduce by 40.7 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, Jmcity needs image optimization as it can save up to 40.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 135.3 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 135.3 kB or 68% of the original size.
Potential reduce by 95.5 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. Jmcity.com needs all CSS files to be minified and compressed as it can save up to 95.5 kB or 80% of the original size.
Number of requests can be reduced by 21 (38%)
55
34
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jmcity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
jmcity.com
2518 ms
www.jmcity.com
14974 ms
jquery-1.7.2.min.js
11398 ms
style_12_common.css
10159 ms
common.js
8378 ms
portal.js
11007 ms
logging.js
11002 ms
bbs_style.css
19076 ms
99433.js
3977 ms
jquery.masonry.min.js
20254 ms
discuz_tips.js
1777 ms
site_nav.png
4517 ms
sprite_bg.png
8338 ms
weixin.png
7526 ms
logo.png
20236 ms
sprite.png
5141 ms
ico.png
7921 ms
line.png
4859 ms
ad1.jpg
15644 ms
a28c0c32959f91cb9d6d4b8dd3cfbc72.jpg
1409 ms
8794da06d47d553b801241f81c04d7eb.jpg
1425 ms
ad01.gif
19210 ms
104309u2the3kj3kkh2erj.jpg
20232 ms
20130730_1000_35.jpg
12681 ms
2015shujia1.png
12225 ms
ad5.png
12781 ms
2015shujia2.png
13629 ms
4c7840b5b1ab7886112207177dc6e94f.jpg
20230 ms
826dae2baa594026af4c737c5b486baa.jpg
20190 ms
79a7c7dac040bd8b80d657e57a284b89.jpg
20191 ms
18707299730d6bcdeb8c97697f0aa3a8.jpg
20191 ms
32751e2119035fcbb857601b9600c975.jpg
20196 ms
c655170949974fa8a1dfadd59cf78ea0.jpg
20197 ms
183722302830d350f7603b97666b2fd9.jpg
20196 ms
f1d921a64d6554da0d1da2704fe12b41.jpg
20080 ms
ad09.gif
20086 ms
100_24.jpg
20075 ms
a498f379fc1dff6ce77e2a4d63dba7bb.jpg
20013 ms
ad02.gif
20005 ms
a9736aea3f426e986647506a1bab11d0.jpg
20006 ms
e6a8775e926a1a2e9a5f87a0c119339f.jpg
20008 ms
ad03.gif
20009 ms
343_24.jpg
20010 ms
c72b7be6fc8c9d7e4618b39ebb5660a6.jpg
20009 ms
ad04.gif
20010 ms
10c0831292037b0123960b0dc1a995de.jpg
20014 ms
ad06.gif
20017 ms
ad05.gif
20012 ms
20130802121443839.jpg
20013 ms
1118ee03e64ebab857951d9bca794f17.jpg
20014 ms
20130805_343_24.jpg
19839 ms
77618f7a7504ab7aa19cab1209936aba.jpg
19813 ms
ad07.gif
19832 ms
086a639cdd0d3378334fbe526c3323fe.jpg
19815 ms
common_extra.js
20314 ms
99433.html
8168 ms
thumb_45_45_140.jpg
12351 ms
thumb_45_45_20121002080649897.jpg
9644 ms
37335d7ce1f51ac666bd98fc4252b592.jpg
11821 ms
ce1342111a5da5b4cb6822016185ed4b.jpg
13064 ms
stat.php
1072 ms
connect.php
14653 ms
stat.htm
258 ms
core.php
1702 ms
52450b864c24eda9e4e4fb1fd14c956c.jpg
14758 ms
11.css
6075 ms
jquery.js
7452 ms
b.js
4137 ms
6.js
4202 ms
11.js
4576 ms
9.gif
2188 ms
pic1.gif
1557 ms
scrolltop.png
2954 ms
f60d82dff49cea5ec411cfb9ceb09548.jpg
13551 ms
app.gif
20018 ms
b41d4523773c7fa8aa691dc31f197bbe.jpg
6577 ms
c77b5dc961a64554cfa437a01f7ce2fc.jpg
10361 ms
20130118_340_24.jpg
8921 ms
si_137586686320828.jpg
19993 ms
136921232389666200.jpg
17491 ms
si_137575688550950.jpg
19991 ms
20130813043822749.jpg
19992 ms
6e0cde57d83f5d880c478db6f25a24d0.jpg
19991 ms
c73f5d90a1fa44d258ad353dca98c74a.jpg
19981 ms
10584de4641b537e838b25194c8a31a8.jpg
19981 ms
9137d0dab635d2d24db59d1917090361.jpg
19976 ms
09d556ab27d017e6854c3bcb9d7fe899.jpg
19975 ms
ad10.gif
19975 ms
1e0f3e112f236521b51c96393c204976.jpg
19966 ms
4ae5f020bef30648971d7376e1613bbc.jpg
19965 ms
7e5cc3f310f975f8fa1338baf71e9baa.jpg
19977 ms
c91f358e0301fbf2a0ce958a8899287c.jpg
19977 ms
fce21942edc80c4fd9686a480f17c5ca.jpg
19977 ms
9b2bf92adabd762a17b9be5006dd9537.jpg
19979 ms
21ff0765ef3e9697427382dd46ff9b1e.jpg
19976 ms
aa421ecf6ce7d140667597a805851879.jpg
19972 ms
7f3022878b4c73594ec279ba4aef1f73.jpg
19972 ms
177a93b5f76a9a986050ac72e2788337.jpg
19970 ms
e5fe474182349f6671fea071d170c830.jpg
19981 ms
dfa118c8fca804f8dc0b3d3ff7ad59bb.jpg
19980 ms
981db9f9eba056555b86ec4bd1d51403.jpg
19945 ms
ad08.gif
19999 ms
security.png
19995 ms
libg.png
18931 ms
b.css
5367 ms
huamao.png
16731 ms
jiaojing.png
19628 ms
tuangou.png
18077 ms
club_logo3.png
20423 ms
h.js
1283 ms
link_ico.png
13624 ms
101281101.json
2040 ms
hm.gif
363 ms
pluginlog.aspx
5436 ms
mini.png
2684 ms
hm.gif
870 ms
jmcity.com SEO score
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jmcity.com 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 Jmcity.com 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.
jmcity.com
Open Graph description is not detected on the main page of Jmcity. 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: