4.3 sec in total
785 ms
3 sec
511 ms
Visit fandc.ro now to see the best up-to-date Fandc content and also check out these interesting facts you probably never knew about fandc.ro
Visit fandc.roWe analyzed Fandc.ro page load time and found that the first response time was 785 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster. This domain responded with an error, which can significantly jeopardize Fandc.ro rating and web reputation
fandc.ro performance score
785 ms
161 ms
382 ms
260 ms
268 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 35% of them (31 requests) were addressed to the original Fandc.ro, 32% (28 requests) were made to Static.xx.fbcdn.net and 15% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Fandc.ro.
Page size can be reduced by 346.7 kB (23%)
1.5 MB
1.2 MB
In fact, the total size of Fandc.ro 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 27.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 4.7 kB, which is 13% 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 27.2 kB or 78% of the original size.
Potential reduce by 35.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. Fandc images are well optimized though.
Potential reduce by 156.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 156.4 kB or 70% of the original size.
Potential reduce by 128.0 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. Fandc.ro needs all CSS files to be minified and compressed as it can save up to 128.0 kB or 82% of the original size.
Number of requests can be reduced by 47 (59%)
80
33
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fandc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
fandc.ro
785 ms
all.js
161 ms
iabootstrap.css
382 ms
iabootstrap-responsive.css
260 ms
user-style.css
268 ms
jquery.fancybox.css
270 ms
style.css
275 ms
css
25 ms
jquery.js
461 ms
intelli.js
457 ms
intelli.config.js
458 ms
intelli.minmax.js
459 ms
footer.js
459 ms
intelli.lang.en.js
514 ms
bootstrap.min.js
642 ms
jquery.fancybox.pack.js
542 ms
handler.js
545 ms
app.js
550 ms
logoofl2rating.png
404 ms
100000_logo_logo.png
268 ms
79 ms
site_logo.png
366 ms
f84b2ab4e0.png
564 ms
6e014437b2.png
753 ms
6de14aa24d.png
756 ms
e610e36d0e.png
635 ms
2c9f11529e.jpg
512 ms
fb51e9a5a3.jpg
705 ms
115729145f.jpg
650 ms
b6995d6b7d.jpg
688 ms
811 ms
sdk.js
88 ms
bg.jpg
1416 ms
7YGmE4Ls5b94ct65u07hVQLUuEpTyoUstqEm5AMlJo4.woff
10 ms
0XxGQsSc1g4rdRdjJKZrNL3hpw3pgy2gAi-Ip7WPMi0.woff
10 ms
fontawesome-webfont.svg
664 ms
fontawesome-webfont.woff
692 ms
PIPMHY90P7jtyjpXuZ2cLLO3LdcAZYWl9Si6vvxL-qU.woff
22 ms
cool-icons.woff
601 ms
165 ms
fb.gif
396 ms
xd_arbiter.php
128 ms
xd_arbiter.php
256 ms
page.php
290 ms
xd_arbiter.php
84 ms
4n08FrZmW0I.css
173 ms
6anp_x4LZhS.css
213 ms
ziZi0nPwp2z.css
257 ms
xwoSSm6eTF5.css
295 ms
q68gy-v_YMF.js
369 ms
YvxwM8R7ol8.js
389 ms
ihptErjAmMX.js
330 ms
3So47A9WcrL.js
297 ms
cUsKAwzqrQw.js
404 ms
_mImxO4mCU1.js
417 ms
QjJ5QeyKyW9.js
339 ms
6PDLJFN-l6_.js
424 ms
553701_492900150726211_51637730_n.jpg
275 ms
safe_image.php
339 ms
11133852_1050802524935968_2078063801906431264_n.png
287 ms
1148946_1384103611815886_833392124_n.jpg
323 ms
1888679_10207332604167673_8345863796932755728_n.jpg
327 ms
12122743_837841269648370_4706919608101271463_n.jpg
359 ms
12799258_1080176278671346_227462973735906344_n.jpg
359 ms
10462745_679021742133535_646325848367355676_n.jpg
368 ms
12743818_1145481162195248_8539267626534198691_n.jpg
361 ms
12742496_1143755295701168_7753791139688874513_n.jpg
395 ms
12743864_1143755325701165_1177706356498217970_n.jpg
525 ms
12729131_1143755322367832_8669150177838417140_n.jpg
555 ms
12717173_1143755395701158_8891246841179507996_n.jpg
430 ms
12744203_1141990909210940_1216626464219208726_n.jpg
448 ms
wL6VQj7Ab77.png
99 ms
s7jcwEQH7Sx.png
100 ms
GtIpNnEyqq_.png
99 ms
vErY8zngADX.js
82 ms
FzGTmhgBEqv.js
42 ms
lRyN50VcaFW.js
41 ms
css;base64,
4 ms
2dVi2K8Rj4g.css
52 ms
X6vRG7qpshl.css
45 ms
b8XhdWI9eAN.js
53 ms
JNPO3NqYHEj.png
44 ms
QijIVO3ZIrO.png
45 ms
R9a_DtVRZgv.js
42 ms
cUDgRFxaoIk.js
43 ms
0JBr1QHp8Gi.js
44 ms
kDOzhTr2W91.js
44 ms
1BQnIVjTFoC.js
81 ms
fandc.ro SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fandc.ro can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fandc.ro 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.
fandc.ro
Open Graph description is not detected on the main page of Fandc. 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: