95.7 sec in total
4.4 sec
88.3 sec
2.9 sec
Welcome to fcuhome.com homepage info - get ready to check Fcuhome best content right away, or after learning these important things about fcuhome.com
首页
Visit fcuhome.comWe analyzed Fcuhome.com page load time and found that the first response time was 4.4 sec and then it took 91.2 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 50 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fcuhome.com performance score
4432 ms
15880 ms
8547 ms
20383 ms
8404 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 83% of them (95 requests) were addressed to the original Fcuhome.com, 9% (10 requests) were made to V3.jiathis.com and 3% (3 requests) were made to Tcss.qq.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Fcuhome.com.
Page size can be reduced by 415.1 kB (57%)
726.8 kB
311.7 kB
In fact, the total size of Fcuhome.com main page is 726.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. 25% of websites need less resources to load. Images take 247.7 kB which makes up the majority of the site volume.
Potential reduce by 137.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 137.7 kB or 83% of the original size.
Potential reduce by 42.0 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, Fcuhome needs image optimization as it can save up to 42.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 105.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 105.0 kB or 65% of the original size.
Potential reduce by 130.3 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. Fcuhome.com needs all CSS files to be minified and compressed as it can save up to 130.3 kB or 86% of the original size.
Number of requests can be reduced by 20 (33%)
61
41
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fcuhome. 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 as a result speed up the page load time.
fcuhome.com
4432 ms
www.fcuhome.com
15880 ms
style_18_common.css
8547 ms
style_18_portal_index.css
20383 ms
common.js
8404 ms
portal.js
1046 ms
logging.js
2568 ms
md5.js
3025 ms
show_ps3.js
4575 ms
jiathis_r.js
577 ms
blockstyle.css
4875 ms
ping.js
497 ms
discuz_tips.js
497 ms
transparent-noise.png
19206 ms
top_bg.gif
19982 ms
logo.png
19389 ms
qq_login.gif
19982 ms
menu_news.gif
10929 ms
menu_bbs.gif
3961 ms
chanpin.png
4527 ms
xiazai.png
5487 ms
shejishi.png
7907 ms
shangcheng.png
10130 ms
pinpai.png
11452 ms
luntan.png
11443 ms
tiyanting.png
11961 ms
anli.png
13450 ms
a4c3a5fe2df18ebeb999286a81247a01.jpg
16344 ms
dd06a4dddfc26332b7144d7430448e53.jpg
19961 ms
ef851572b184c7b2983a9d641869aa23.jpg
19961 ms
a699f84cf772d646bd6295a501520f2e.jpg
19961 ms
d39540c50a4adb935f2db068e7fd3081.jpg
19961 ms
0272468051e03234d17056f83b56cb39.jpg
19962 ms
37d17384547774761a83aac37e9ff247.jpg
19963 ms
9ba218fa28db97dcbc00a2116963a459.jpg
19963 ms
sqrz.gif
19963 ms
sjrz.gif
19967 ms
b6720eaf1c0611c6da98fea8a5ea5a08.jpg
19968 ms
enocean.png
19969 ms
bochuang.png
19969 ms
comfort.png
19977 ms
knx.png
19978 ms
belkin.png
19978 ms
amx.png
19979 ms
easy.png
19979 ms
ed27fbceada178314d5d2a545be7261b.jpg
19979 ms
c2eea15c2f0896e9d94e442ed137ee65.jpg
19995 ms
9a7a6daedbf969e4ddc1a5238d2c76e6.jpg
19997 ms
c060872c375cbcc4c546f2c669ad67a1.jpg
19885 ms
adshow
3342 ms
jiathis_utility.html
57 ms
jiathis_share.css
61 ms
ckepop.js
60 ms
ckecenterpop.js
59 ms
plugin.client.js
43 ms
r1.gif
43 ms
img_exit.gif
17 ms
img_012.gif
16 ms
jiathis_ico.png
44 ms
toss_11.gif
1051 ms
OTI1NTIzMw==.js
594 ms
h.js
542 ms
21.gif
986 ms
hm.gif
270 ms
common_extra.js
20019 ms
ee72a07e8562c684954e7e5eed5d654e.jpg
20453 ms
ee6759e3d79ce90e929a6e8e08969c0d.jpg
20493 ms
d6f0674716075c89fada656456eb99bb.jpg
20072 ms
c9561aa68872ba4fdb6be6ab8e4425c6.jpg
19838 ms
005134d7az6uuub5up5jdf.jpg
20053 ms
1f54585109720d4146094c28da28b5f8.jpg
19518 ms
eee8cc952ecad5847083189238641067.jpg
16699 ms
0d2e2b5d61d3f299dc5d403afe4b0e81.jpg
17961 ms
3c4ed3e70c3ed075ad26b396f8e52a7d.jpg
16151 ms
7e2aafa40c8575397957877a86e5a6c2.jpg
13687 ms
9a332765b2c22aba4db44fa440cb4627.jpg
11932 ms
930cc1fc90d031813275896155b48ecd.jpg
14325 ms
388624f70496f3067a4e2fc8bcc0ec9b.jpg
14731 ms
52dba42f914844e558b2b227ceb49062.jpg
19999 ms
52ba1cd7a7ebe6fb21ee581e17c37740.jpg
13455 ms
c9d18473aa8d8c81d0e5c20214a0dce8.jpg
19999 ms
1a91f75315fade9a2c382f9b11854a54.jpg
19999 ms
1234f782566590817101d395085bca35.jpg
16009 ms
af93412344b0a15a61b3158ddc2ccba8.jpg
15026 ms
a53d5455b35bc7908b5436450836c8be.jpg
19806 ms
67002705379d4fb6fa41841418c4879f.jpg
16049 ms
e256e70f2e64794f7a59a4caf88c64b6.jpg
19071 ms
9230927b3f51e32c9c334299a264f086.jpg
19991 ms
b53dfa6f167968fa657f67a809c33484.jpg
19992 ms
9f2755968762fe98ae68e5a68cdea757.jpg
19992 ms
bb16048f91059b3ac51864ce1e67c7e3.jpg
19985 ms
85e7aa2e7bb262e4f2201afe527540d3.jpg
19985 ms
1a70edb78d00e631da0307cfaa0aca60.jpg
19985 ms
2693d6a14966aa68faddb41f67b39b48.jpg
19985 ms
a5d9ffb4c281b7c4c7a601a77ca4b8f2.jpg
19984 ms
security.png
19987 ms
px.png
19972 ms
newarow.gif
19971 ms
pn.png
19969 ms
nv_left.gif
19965 ms
nv_right.gif
19010 ms
nv.jpg
15930 ms
qmenu.png
19997 ms
nv_a.gif
20005 ms
nv_aright.gif
19824 ms
nv_line.gif
11314 ms
ping_right.png
13172 ms
ping_left.png
11549 ms
search.png
12041 ms
dot.gif
11636 ms
archy_sdbg.png
12151 ms
archy_buttom_left.gif
12442 ms
archy_buttom_right.gif
10207 ms
scrolltop.png
9848 ms
fcuhome.com SEO score
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcuhome.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 Fcuhome.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.
fcuhome.com
Open Graph description is not detected on the main page of Fcuhome. 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: