5.2 sec in total
491 ms
4.2 sec
534 ms
Welcome to fcb.uz homepage info - get ready to check Fcb best content for Uzbekistan right away, or after learning these important things about fcb.uz
Visit fcb.uzWe analyzed Fcb.uz page load time and found that the first response time was 491 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fcb.uz performance score
491 ms
1210 ms
411 ms
408 ms
209 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 27% of them (21 requests) were addressed to the original Fcb.uz, 26% (20 requests) were made to Static.xx.fbcdn.net and 12% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fcb.uz.
Page size can be reduced by 568.1 kB (22%)
2.6 MB
2.1 MB
In fact, the total size of Fcb.uz main page is 2.6 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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 245.5 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 245.5 kB or 86% of the original size.
Potential reduce by 34.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. Fcb images are well optimized though.
Potential reduce by 176.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 176.4 kB or 65% of the original size.
Potential reduce by 111.8 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. Fcb.uz needs all CSS files to be minified and compressed as it can save up to 111.8 kB or 86% of the original size.
Number of requests can be reduced by 38 (51%)
75
37
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fcb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
491 ms
bootstrap.css
1210 ms
styles.css
411 ms
datepicker.css
408 ms
online_users.css
209 ms
jquery.js
1000 ms
all.js
410 ms
bootstrap.min.js
614 ms
typeahead.js
623 ms
datepicker_uz.js
441 ms
ga.js
11 ms
Villarreal-vs-Barcelona.jpg
42 ms
ZL2oYuOnLv.jpg
1239 ms
_T6Q7136-Optimized.v1458413689.JPG
42 ms
nou-camp-nou-mono.v1457611755.jpg
39 ms
rWuRqHRBVJk.jpg
805 ms
0000247541.jpg
136 ms
031816-SOCCER-Messi-Restaurant-LN-PI.vadapt.664.high.71.jpg
242 ms
logo_uz.png
418 ms
top_uz.png
836 ms
uz.png
207 ms
en.png
208 ms
ru.png
239 ms
fe31dcf5a83fabcb6c7b98d7f1482599.jpg
647 ms
bb982bdfa10ad8aec125a8ee6d69e09c.jpg
417 ms
2016-03-19_ENTRENO_30-Optimized.v1458407044.JPG
36 ms
pflT4snb5-s.jpg
924 ms
TmhfvdGkROo.jpg
1038 ms
sdk.js
33 ms
background.jpg
1873 ms
menu.png
448 ms
context.js
228 ms
__utm.gif
28 ms
glyphicons-halflings-regular.woff
590 ms
69 ms
73 ms
xd_arbiter.php
28 ms
xd_arbiter.php
45 ms
context_static_r1071.js
334 ms
141894
140 ms
watch.js
206 ms
2014.png
217 ms
y80
18 ms
watch.js
519 ms
cnt.png
818 ms
likebox.php
96 ms
410ucuAGgaJ.css
34 ms
tSbl8xBI27R.css
41 ms
VyhHmC9SnBT.css
40 ms
q68gy-v_YMF.js
46 ms
FJmpeSpHpjS.js
66 ms
0wM5s1Khldu.js
34 ms
1bNoFZUdlYZ.js
35 ms
OloiM1PZafe.js
78 ms
LTv6ZK-5zxz.js
87 ms
1FCa-btixu2.js
83 ms
Oagsvfb4VWi.js
83 ms
pObvZSrFc_4.js
85 ms
Kt4tkgSRvHH.js
84 ms
H3EKDTObx05.js
81 ms
eR-qA8bp1RM.js
121 ms
12039230_496944620467565_1962178868659146369_n.jpg
94 ms
1619120_272131382948891_1030216825_n.jpg
32 ms
10354686_10150004552801856_220367501106153455_n.jpg
13 ms
12803146_145248765866325_4218450723921147068_n.jpg
14 ms
12795455_196731644026978_6522934575529941013_n.jpg
14 ms
12522916_121779831533441_393746725341255718_n.jpg
15 ms
12508815_199911990355502_1561155544816536288_n.jpg
12 ms
11701133_703974023065529_7064227544346206144_n.jpg
14 ms
12316525_789946297818019_6944229083963652975_n.jpg
16 ms
wL6VQj7Ab77.png
11 ms
s7jcwEQH7Sx.png
10 ms
gxbPuQdXIZP.png
9 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
5 ms
advert.gif
85 ms
1
86 ms
fcb.uz 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 Fcb.uz 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 Fcb.uz 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.
fcb.uz
Open Graph description is not detected on the main page of Fcb. 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: