36.4 sec in total
2 sec
33.8 sec
548 ms
Visit fckb.cc now to see the best up-to-date Fckb content for China and also check out these interesting facts you probably never knew about fckb.cc
本站专业提供最新恐怖片、稀有恐怖片、经典恐怖片、欧美恐怖片、泰国恐怖片、日韩恐怖片、以及其他最新电影与最新电视剧.本站每日更新,字幕组定期翻译优秀电影作品,压制组每日发布电影.
Visit fckb.ccWe analyzed Fckb.cc page load time and found that the first response time was 2 sec and then it took 34.4 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.
fckb.cc performance score
2005 ms
3512 ms
693 ms
227 ms
703 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 68% of them (92 requests) were addressed to the original Fckb.cc, 6% (8 requests) were made to Appicon.manyou.com and 4% (5 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Pcookie.cnzz.com.
Page size can be reduced by 454.9 kB (30%)
1.5 MB
1.1 MB
In fact, the total size of Fckb.cc main page is 1.5 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 91.1 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 91.1 kB or 82% of the original size.
Potential reduce by 94.2 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. Fckb images are well optimized though.
Potential reduce by 216.4 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 216.4 kB or 71% of the original size.
Potential reduce by 53.2 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. Fckb.cc needs all CSS files to be minified and compressed as it can save up to 53.2 kB or 75% of the original size.
Number of requests can be reduced by 43 (34%)
128
85
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fckb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fckb.cc
2005 ms
www.fckb.cc
3512 ms
style_2_common.css
693 ms
style_2_forum_index.css
227 ms
common.js
703 ms
forum.js
305 ms
t9.css
157 ms
i.php
1873 ms
i.php
3476 ms
p.jusha.com
1434 ms
ss.xq199.com
1563 ms
v.php
1176 ms
logging.js
152 ms
GB_BIG.js
262 ms
ping.js
557 ms
4184833.js
4712 ms
stat.php
1378 ms
1068309
15483 ms
1053099
15500 ms
1065853
15505 ms
1036797
15747 ms
1060375
15504 ms
1065730
15761 ms
1065808
15705 ms
1036304
15736 ms
bg_all.png
83 ms
logo.gif
85 ms
8e00fd4fd59658f4ba7d13ad23bba07b.jpg
537 ms
b5fbbdce072b4b4e0cf46716a96b9469.jpg
320 ms
9940c142161608de23c33625b1915a4a.jpg
507 ms
cd484f2e408ac12d02ad1e0bd6704c0e.jpg
532 ms
ed0954de6d624beb6eb81492d5782240.jpg
328 ms
cd4e7d5bb2326d4e82cab74e954f0464.jpg
618 ms
e652da9ae84d217201d0b0404cc98e61.jpg
621 ms
45a23b159de63e0390f4dcd0afa48d27.jpg
977 ms
243317f36dd98b478406c890fe3dad86.jpg
1011 ms
5b7444c1362e8bc79d569879620c8cbf.jpg
878 ms
22c6bcbac7d8772962fd26ae78c96404.jpg
879 ms
1f7e6d724cdcb9027f0f72c266c7b53c.jpg
1114 ms
1168.jpg
803 ms
1167.jpg
878 ms
1165.jpg
974 ms
1163.jpg
974 ms
1162.jpg
1076 ms
135517pukksgwu7k2xlsk8.gif
19800 ms
1160.jpg
1048 ms
1159.jpg
1046 ms
group_120_icon.jpg
1095 ms
group_64_icon.jpg
1138 ms
group_181_icon.jpg
1137 ms
group_188_icon.jpg
1146 ms
group_187_icon.jpg
1163 ms
group_195_icon.png
1216 ms
nophoto.gif
1236 ms
collapsed_no.gif
941 ms
forum.gif
1095 ms
forum_new.gif
1071 ms
collapsed_no.gif
974 ms
online_admin.gif
966 ms
online_supermod.gif
1005 ms
online_moderator.gif
1006 ms
online_jianxi.gif
1002 ms
online_team.gif
1069 ms
online_guest.gif
1018 ms
lr_s.js
1815 ms
ha0000.php
1416 ms
save_log.php
916 ms
online_vip.gif
1001 ms
noavatar_small.gif
1049 ms
noavatar_small.gif
972 ms
00_avatar_small.jpg
1037 ms
88_avatar_small.jpg
1687 ms
98_avatar_small.jpg
977 ms
29_avatar_small.jpg
904 ms
68_avatar_small.jpg
949 ms
77_avatar_small.jpg
953 ms
98_avatar_small.jpg
909 ms
01_avatar_small.jpg
905 ms
97_avatar_small.jpg
1525 ms
05_avatar_small.jpg
897 ms
92_avatar_small.jpg
893 ms
00_avatar_small.jpg
846 ms
39_avatar_small.jpg
1155 ms
59_avatar_small.jpg
855 ms
01_avatar_small.jpg
842 ms
noavatar_small.gif
922 ms
noavatar_small.gif
817 ms
noavatar_small.gif
953 ms
noavatar_small.gif
874 ms
noavatar_small.gif
946 ms
noavatar_small.gif
938 ms
noavatar_small.gif
874 ms
online_member.gif
946 ms
logo.gif
874 ms
security.png
867 ms
m.js
2138 ms
iiadclosepf.png
5293 ms
iiadlogo.png
5304 ms
dot.gif
5746 ms
bg.png
1399 ms
top_bg.jpg
1168 ms
t9_top.png
76 ms
px.png
94 ms
18064039kg9m5weze9ardr.gif
38 ms
0953351hcnq10n6w4zqnwh.png
31 ms
t9_nv_bg.png
113 ms
t9_nv_bg_a.png
121 ms
mu_bg.png
163 ms
search.png
163 ms
arrwd.gif
204 ms
followbutton.php
818 ms
pt_item.png
168 ms
title.png
225 ms
common_extra.js
570 ms
sortnum.png
206 ms
chart.png
141 ms
t9_title_bg_02.png
606 ms
shell_v2.js
9631 ms
MzA3MzkwMg==.js
298 ms
icon_5.gif
7122 ms
stat.htm
198 ms
core.php
1094 ms
followButton.css
156 ms
sso.js
163 ms
followButton.js
157 ms
suda.js
153 ms
bg_flbtn.png
28 ms
b.gif
930 ms
9.gif
777 ms
pic1.gif
1241 ms
scrolltop.png
79 ms
app.gif
20445 ms
logger.js
307 ms
bds_s_v2.js
1256 ms
bdsstyle.css
309 ms
l3.gif
1229 ms
fckb.cc 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 Fckb.cc 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 Fckb.cc 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.
fckb.cc
Open Graph description is not detected on the main page of Fckb. 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: