51.9 sec in total
5.2 sec
46.4 sec
297 ms
Visit gfjl.org now to see the best up-to-date GFJL content for China and also check out these interesting facts you probably never knew about gfjl.org
计量论坛是您的计量百科全书,提供计量标准下载及讨论,计量单位换算表工具,注册计量师,计量法,CMA计量认证,CNAS实验室,计量管理,计量论文,检定规程,校准规范
Visit gfjl.orgWe analyzed Gfjl.org page load time and found that the first response time was 5.2 sec and then it took 46.7 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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
gfjl.org performance score
5197 ms
5254 ms
4320 ms
9652 ms
4964 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 60% of them (62 requests) were addressed to the original Gfjl.org, 7% (7 requests) were made to Cpro.baidustatic.com and 6% (6 requests) were made to T11.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source T12.baidu.com.
Page size can be reduced by 418.7 kB (44%)
961.8 kB
543.1 kB
In fact, the total size of Gfjl.org main page is 961.8 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. 30% of websites need less resources to load. Javascripts take 441.9 kB which makes up the majority of the site volume.
Potential reduce by 52.0 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.0 kB or 79% of the original size.
Potential reduce by 12.8 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. GFJL images are well optimized though.
Potential reduce by 291.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 291.6 kB or 66% of the original size.
Potential reduce by 62.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. Gfjl.org needs all CSS files to be minified and compressed as it can save up to 62.4 kB or 78% of the original size.
Number of requests can be reduced by 52 (53%)
99
47
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GFJL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
forum.php
5197 ms
style_1_common.css
5254 ms
style_1_forum_index.css
4320 ms
common.js
9652 ms
forum.js
4964 ms
logging.js
3987 ms
md5.js
2919 ms
c.js
942 ms
discuz_tips.js
629 ms
background.png
515 ms
switch_width.png
491 ms
logo.png
1558 ms
qq_login.gif
882 ms
811.gif
2093 ms
panran_h.gif
5051 ms
zts.gif
10535 ms
jofra.gif
6588 ms
biaozhunwuzhi.png
5474 ms
collapsed_no.gif
1940 ms
list_7ree.gif
2334 ms
common_16_icon.gif
3913 ms
common_27_icon.gif
2717 ms
common_8_icon.gif
3099 ms
common_25_icon.gif
3483 ms
common_38_icon.gif
3872 ms
common_193_icon.gif
4266 ms
common_30_icon.gif
4439 ms
common_18_icon.gif
4649 ms
common_194_icon.gif
4965 ms
common_192_icon.gif
5036 ms
common_29_icon.gif
5482 ms
common_153_icon.gif
5418 ms
common_56_icon.gif
7789 ms
common_50_icon.gif
5800 ms
common_151_icon.gif
5910 ms
common_187_icon.gif
6000 ms
common_3_icon.gif
6189 ms
common_4_icon.gif
6350 ms
common_5_icon.gif
6515 ms
common_9_icon.gif
6577 ms
common_10_icon.gif
6788 ms
common_11_icon.gif
7032 ms
common_12_icon.gif
6969 ms
common_13_icon.gif
7092 ms
common_14_icon.gif
7218 ms
scfm
874 ms
share.js
20166 ms
h.js
706 ms
connect.php
19784 ms
common_15_icon.gif
7038 ms
21.gif
2075 ms
hm.gif
362 ms
common_43_icon.gif
7563 ms
scfm
1862 ms
common_41_icon.gif
6118 ms
forum.gif
6130 ms
site_qq.jpg
7261 ms
beian.png
13516 ms
adx.php
1541 ms
px.png
5872 ms
u=3039011832,3719616543&fm=76
1180 ms
u=3118428872,3071454351&fm=76
1470 ms
u=1982346307,1902415825&fm=76
976 ms
bg.png
488 ms
reduce_bd-logo1_oper.png
530 ms
u=1496671384,950133907&fm=76
1153 ms
u=561684103,2469852632&fm=76
1686 ms
u=1609015237,2305241722&fm=76
3033 ms
u=2859318808,3618911549&fm=76
1503 ms
u=3076872898,3391698317&fm=76
2357 ms
u=400346673,393997376&fm=76
1708 ms
u=1094626092,3338369978&fm=76
1262 ms
u=2754278886,3178204329&fm=76
3140 ms
u=2193304649,3154934947&fm=76
1383 ms
u=2307322844,3332689743&fm=76
2545 ms
u=293050688,174151590&fm=76
20429 ms
newarow.gif
5863 ms
pn.png
5631 ms
nv.png
6948 ms
qmenu.png
5731 ms
nv_a.png
5525 ms
search.png
5722 ms
pt_item.png
6747 ms
chart.png
5726 ms
titlebg.png
5991 ms
scrolltop.png
6183 ms
closefeedback.min.js
503 ms
o.htm
913 ms
like.php
523 ms
reduce_promotion_oper.png
471 ms
bd_logo.png
504 ms
hm.gif
976 ms
bg_rb.png
511 ms
like
455 ms
wh.js
2165 ms
ac.js
1912 ms
like_this.css
1095 ms
qzfl_for_qzone.js
2435 ms
interface.js
1031 ms
tc.js
4534 ms
fp.htm
459 ms
fp.htm
274 ms
get
641 ms
gfjl.org SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gfjl.org 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 Gfjl.org 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.
gfjl.org
Open Graph description is not detected on the main page of GFJL. 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: