34.4 sec in total
675 ms
33 sec
798 ms
Visit run.gmw.cn now to see the best up-to-date Run Gmw content for China and also check out these interesting facts you probably never knew about run.gmw.cn
光明乐跑,健康每一步,快乐每一天
Visit run.gmw.cnWe analyzed Run.gmw.cn page load time and found that the first response time was 675 ms and then it took 33.8 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.
run.gmw.cn performance score
675 ms
910 ms
614 ms
924 ms
694 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 80% of them (106 requests) were addressed to the original Run.gmw.cn, 4% (5 requests) were made to Wx.mlogcn.com and 4% (5 requests) were made to Webapi.amap.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Run.gmw.cn.
Page size can be reduced by 448.1 kB (9%)
5.1 MB
4.6 MB
In fact, the total size of Run.gmw.cn main page is 5.1 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. 45% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 52.8 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 52.8 kB or 78% of the original size.
Potential reduce by 137.5 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. Run Gmw images are well optimized though.
Potential reduce by 197.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 197.3 kB or 65% of the original size.
Potential reduce by 60.4 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. Run.gmw.cn needs all CSS files to be minified and compressed as it can save up to 60.4 kB or 78% of the original size.
Number of requests can be reduced by 46 (36%)
128
82
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Run Gmw. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
forum.php
675 ms
style_3_common.css
910 ms
style_3_forum_index.css
614 ms
common.js
924 ms
forum.js
694 ms
logging.js
694 ms
md5.js
647 ms
jquery-easing-1.3.pack.js
952 ms
jquery-easing-compatibility.1.2.pack.js
964 ms
coda-slider.1.1.1.pack.js
1019 ms
slider_style_7ree.css
1025 ms
ping.js
481 ms
discuz_tips.js
449 ms
bg_body.png
309 ms
qq_login.gif
310 ms
wechat_login.png
325 ms
logo.png
414 ms
b4.gif
5842 ms
b2.gif
6071 ms
b3.gif
3638 ms
b1.gif
8527 ms
b5.gif
5892 ms
1.gif
740 ms
2.gif
1075 ms
3.gif
1606 ms
4.gif
1956 ms
5.gif
2284 ms
3807ac968aded0f281a5002d8a782649.jpg
6430 ms
2e074b11cf33d8d996cf39b49ce65e79.jpg
7275 ms
b664aac6ed5342c10cfb88cfebfd410b.jpg
9603 ms
125c12948f3cea0193eda219748a90b2.jpg
7114 ms
094436qv7k3liiqiik3kwn.jpg
10441 ms
114453r1a47xyyd40x4rwx.jpg
19729 ms
162007ruppzzcl66r71yrz.jpg
11190 ms
9fecdd1d40e722ad8181dd1fcc140ab3.jpg
7913 ms
110334gye3e3x3jywqwt7z.jpg
12656 ms
collapsed_no.gif
8830 ms
common_150_icon.jpg
9146 ms
common_152_icon.jpg
9466 ms
common_151_icon.jpg
9769 ms
common_53_icon.gif
9932 ms
common_154_icon.png
10695 ms
common_148_icon.png
10616 ms
common_63_icon.gif
10739 ms
common_74_icon.gif
10997 ms
common_64_icon.jpg
11558 ms
index.html
2675 ms
jquery-1.7.1.min.js
12307 ms
common_78_icon.gif
11333 ms
common_73_icon.gif
11191 ms
common_57_icon.gif
11444 ms
common_59_icon.gif
11476 ms
common_75_icon.gif
11583 ms
common_79_icon.gif
11688 ms
common_67_icon.gif
11368 ms
common_136_icon.png
11733 ms
common_61_icon.gif
10849 ms
common_68_icon.gif
10457 ms
common_133_icon.png
10704 ms
main.css
377 ms
modernizr.js
792 ms
maps
1392 ms
vendor.js
2731 ms
main.js
834 ms
common_135_icon.png
9082 ms
style1.3.14.11.css
943 ms
main
12194 ms
common_65_icon.gif
6926 ms
common_77_icon.jpg
7076 ms
common_137_icon.png
7258 ms
common_138_icon.png
7332 ms
common_139_icon.png
6610 ms
common_140_icon.png
6313 ms
common_141_icon.png
5692 ms
common_142_icon.png
5115 ms
common_143_icon.png
5350 ms
31439e90091bd43251bf1d813eb2b7d5.jpg
5379 ms
cec66a89e241c2152d2206735c9a84e5.jpg
4768 ms
231207xqnaaoa11ajbkn0e.jpg
6690 ms
212656ksh3czm7l3n33ppc.jpg
7642 ms
dff663b2c25e09dfaf08b05d7694b14f.jpg
4864 ms
165427ykq0h8ddt1b0zdm1.jpg
5017 ms
2f950386edd27d4371ef9566880735ee.jpg
4505 ms
101538yk4d9j2dkd2uhdbk.jpg
11133 ms
105236cr55ac80a1ww8zrq.jpg
19984 ms
232203n41i4itsijseijzn.jpg
5242 ms
collapsed_yes.gif
5318 ms
163150cdx1zll2jcpi16gj.jpg
5148 ms
161306sbk5sicnekzdkeli.jpg
5285 ms
121043fvo7dzp8qc62pqv6.jpeg
5239 ms
142304tj1lg0404yggli88.jpg
5279 ms
132526njtt9t2pp21xc51p.jpg
5814 ms
131323yxw8rir8mxzjg5z8.jpg
5382 ms
095903mnqognspen9ceqpu.jpg
5449 ms
173450e7xxx1zex6te016z.png
5635 ms
150354kl4l46k9aykubqk4.jpg
5420 ms
common_extra.js
5800 ms
100503aad4d7fsantfabfa.jpg
5911 ms
toss_11.gif
226 ms
MjQ5MjUyNTQ=.js
616 ms
analytics.js
40 ms
atrk.js
99 ms
webdig.js
520 ms
collect
27 ms
collect
97 ms
atrk.gif
49 ms
164721ijachf2u5czu5naz.jpg
5509 ms
test.png
202 ms
103553uzlupuhfbyzwvku9.jpg
5720 ms
ad_close.gif
5706 ms
plugin.php
5946 ms
security.png
5730 ms
px.png
5726 ms
r-549582d83e09093714601378128180.7589899175800383
631 ms
1.gif
614 ms
pn.png
5646 ms
nv.png
5421 ms
nv_a.png
5433 ms
search.png
5685 ms
pt_item.png
6295 ms
chart.png
6098 ms
title.png
5388 ms
sortnum.png
5625 ms
dot.gif
5627 ms
ajax-loader.gif
5490 ms
transpbg_7ree.png
5079 ms
uparrow_icon_7ree.png
4792 ms
init
1433 ms
modules
1121 ms
ip
1188 ms
39.9.json
1315 ms
count
1008 ms
run.gmw.cn SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Run.gmw.cn 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 Run.gmw.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.
run.gmw.cn
Open Graph description is not detected on the main page of Run Gmw. 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: