63.7 sec in total
3 sec
60.4 sec
332 ms
Visit fjzg.org now to see the best up-to-date Fjzg content and also check out these interesting facts you probably never knew about fjzg.org
福建致公网-02-22年记录-外链超多
Visit fjzg.orgWe analyzed Fjzg.org page load time and found that the first response time was 3 sec and then it took 60.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 37 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fjzg.org performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
3014 ms
817 ms
114 ms
850 ms
1175 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 95% of them (155 requests) were addressed to the original Fjzg.org, 1% (1 request) were made to Adobe.com and 1% (1 request) were made to Pw.cnzz.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Fjzg.org.
Page size can be reduced by 109.8 kB (19%)
585.1 kB
475.3 kB
In fact, the total size of Fjzg.org main page is 585.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. 30% of websites need less resources to load. Images take 466.7 kB which makes up the majority of the site volume.
Potential reduce by 80.2 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. This page needs HTML code to be minified as it can gain 11.6 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 80.2 kB or 86% of the original size.
Potential reduce by 12.4 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. Fjzg images are well optimized though.
Potential reduce by 17.0 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 17.0 kB or 70% of the original size.
Potential reduce by 255 B
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. Fjzg.org needs all CSS files to be minified and compressed as it can save up to 255 B or 48% of the original size.
Number of requests can be reduced by 16 (13%)
123
107
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fjzg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
fjzg.org
3014 ms
css1.css
817 ms
get_flash_player.gif
114 ms
3.js
850 ms
main_02.gif
1175 ms
main_03.gif
855 ms
main_04.gif
1171 ms
main_05.gif
1175 ms
main_06.gif
1176 ms
main_07.gif
1208 ms
main_08.gif
1536 ms
main_09.gif
1544 ms
main_10.gif
1545 ms
main_11.gif
1545 ms
main_12.gif
1602 ms
main_13.gif
1739 ms
main_14.gif
1925 ms
main_15.gif
1928 ms
main_16.gif
1932 ms
main_17.gif
1932 ms
main_18.gif
2028 ms
main_19.gif
2162 ms
main_20.gif
2346 ms
taiyang.gif
2345 ms
ShowA.asp
2082 ms
ShowA.asp
2026 ms
S_Article.js
2116 ms
ShowA.asp
1921 ms
c.php
1467 ms
ajax.js
1960 ms
main_23.gif
1941 ms
main_22.gif
2142 ms
main_23-24.gif
3702 ms
main_26-31.gif
2264 ms
main_32.gif
2386 ms
main_34.gif
2289 ms
main_45.gif
2415 ms
main_58.gif
4334 ms
main_36-61.gif
2843 ms
main_37-62.gif
2729 ms
userlogin.asp
2940 ms
main_39-87.gif
2817 ms
wx.jpg
13259 ms
main_41-89.gif
3313 ms
1-1.jpg
3577 ms
%E5%AD%A6%E4%B9%A0%E5%8D%81%E4%B8%83%E5%A4%A7%E7%B2%BE%E7%A5%9E.jpg
7307 ms
%E6%94%BF%E6%B2%BB%E4%BA%A4%E6%8E%A5%E5%AD%A6%E4%B9%A0%E6%95%99%E8%82%B2%E6%B4%BB%E5%8A%A8.jpg
4418 ms
%E7%9C%81%E7%AC%AC%E4%B8%83%E6%AC%A1%E4%BB%A3%E8%A1%A8%E5%A4%A7%E4%BC%9A.jpg
12173 ms
%E8%87%B4%E5%85%AC%E5%85%9A%E5%91%98%E9%A3%8E%E9%87%87%E5%BD%95.jpg
7007 ms
main_43-118-1.jpg
6216 ms
jian.gif
4712 ms
main_43-118.gif
5229 ms
201206070017534439.jpg
18909 ms
main_121.gif
8961 ms
main_47-149.gif
8669 ms
main_150.gif
8651 ms
main_152.gif
9146 ms
main_50-154.gif
13119 ms
main_51-155.gif
9245 ms
main_52-156.gif
11397 ms
main_156.gif
10951 ms
main_24.gif
14385 ms
main_37.gif
13233 ms
null
3 ms
main_38.gif
12996 ms
main_92.gif
4691 ms
main_40.gif
20397 ms
stat.htm
1304 ms
core.php
1247 ms
1.gif
12950 ms
2.gif
13297 ms
3.gif
14118 ms
4.gif
15317 ms
5.gif
15439 ms
6.gif
14179 ms
7.gif
15239 ms
8.gif
16976 ms
main_62.gif
15346 ms
main_63-69.gif
15344 ms
losspass.gif
1304 ms
mas.gif
1756 ms
main_71.gif
17837 ms
9.gif
1885 ms
2.gif
793 ms
ajax.asp
17560 ms
main_72.gif
19597 ms
main_42.gif
18594 ms
main_43.gif
19963 ms
main_46.gif
20489 ms
app.gif
4236 ms
main_48.gif
19857 ms
main_73-76.gif
20280 ms
main_77.gif
20354 ms
main_76-80.gif
17777 ms
1-2.jpg
19563 ms
2010071916174434005.jpg
19526 ms
main_78.gif
16529 ms
main_44.gif
18350 ms
main_89.gif
19195 ms
main_97.gif
19370 ms
main_98.gif
18450 ms
main_83-100.gif
18049 ms
2016020311404721209.jpg
20364 ms
2016020311402742006.jpg
19690 ms
2016020311394819806.jpg
19721 ms
201602031139314921.jpg
19543 ms
2016020311391389881.jpg
20409 ms
2016020311385113401.jpg
20387 ms
2016020311382728456.jpg
20065 ms
2016020311375554025.jpg
20285 ms
2016020311373861526.jpg
18257 ms
2016020311372455537.jpg
19605 ms
main_103.gif
17829 ms
main_100.gif
19644 ms
main_101.gif
18052 ms
main_88.gif
17829 ms
main_89-108.gif
20093 ms
main_90.gif
16403 ms
main_122.gif
16544 ms
main_93-112.gif
15675 ms
main_112.gif
15268 ms
main_123.gif
14437 ms
main_115.gif
14340 ms
main_116.gif
13658 ms
main_141.gif
12781 ms
main_142.gif
11820 ms
main_143.gif
11934 ms
main_129-145.gif
11916 ms
2015021608105073436.jpg
19999 ms
2015021608102643350.png
19985 ms
2015021608100213108.jpg
13190 ms
2015021608093590077.jpg
11769 ms
2015021608072577436.jpg
13691 ms
2015021608070789210.jpg
19999 ms
201502160806307318.jpg
19835 ms
2015021608053839653.jpg
20331 ms
2015021608045680855.jpg
20361 ms
2015021608044015696.jpg
20357 ms
main_157.gif
15649 ms
main_145.gif
16175 ms
main_146.gif
15900 ms
main_38-63.gif
16207 ms
2010071916034758732.gif
16013 ms
main_125.gif
17143 ms
2010071915584445417.gif
19999 ms
main_39.gif
17887 ms
main_41.gif
18654 ms
2016040811481145208.jpg
19520 ms
main_69.gif
17044 ms
main_70.gif
19143 ms
main_73.gif
20129 ms
main_74.gif
20000 ms
main_78.jpg
18323 ms
main_109.gif
19812 ms
main_92-111.gif
19221 ms
main_113.gif
19560 ms
main_114.gif
20427 ms
2016040811455454034.jpg
20341 ms
201604061815434940.jpg
20219 ms
2016040514443541264.png
20178 ms
loading.gif
20063 ms
2016040511394321801.jpg
20001 ms
2016040115483461041.jpg
19938 ms
fjzg.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
fjzg.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
fjzg.org SEO score
EN
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fjzg.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Fjzg.org 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.
fjzg.org
Open Graph description is not detected on the main page of Fjzg. 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: