8.3 sec in total
760 ms
6 sec
1.5 sec
Visit fb.ru now to see the best up-to-date FB content for Russia and also check out these interesting facts you probably never knew about fb.ru
Visit fb.ruWe analyzed Fb.ru page load time and found that the first response time was 760 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fb.ru performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value3.9 s
51/100
25%
Value4.8 s
67/100
10%
Value580 ms
51/100
30%
Value0.01
100/100
15%
Value7.7 s
46/100
10%
760 ms
36 ms
463 ms
277 ms
285 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 12% of them (11 requests) were addressed to the original Fb.ru, 77% (73 requests) were made to Img.fb.ru and 4% (4 requests) were made to Site.yandex.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Img.fb.ru.
Page size can be reduced by 241.2 kB (20%)
1.2 MB
967.7 kB
In fact, the total size of Fb.ru main page is 1.2 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 869.8 kB which makes up the majority of the site volume.
Potential reduce by 133.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 52.8 kB, which is 33% 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 133.2 kB or 84% of the original size.
Potential reduce by 31.9 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. FB images are well optimized though.
Potential reduce by 76.1 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 76.1 kB or 42% of the original size.
Number of requests can be reduced by 12 (13%)
92
80
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FB. 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.
fb.ru
760 ms
analytics.js
36 ms
watch.js
463 ms
index.css
277 ms
main.css
285 ms
ads.js
796 ms
jquery.js
739 ms
index.js
629 ms
news.js
662 ms
tracker.js
692 ms
collect
12 ms
advert.gif
85 ms
1
85 ms
32729_729x486.jpg
893 ms
search_form
229 ms
32725_300x200.jpg
664 ms
32513_300x200.jpg
665 ms
32716_300x200.jpg
702 ms
32522_300x200.jpg
915 ms
32697_300x200.jpg
925 ms
32537_300x200.jpg
942 ms
32470_300x200.jpg
939 ms
27827_300x200.jpg
994 ms
32361_300x200.jpg
1078 ms
19400_300x200.jpg
1351 ms
32421_300x200.jpg
1365 ms
32394_300x200.jpg
1217 ms
32435_300x200.jpg
1214 ms
32038_300x200.jpg
1286 ms
32081_300x200.jpg
1354 ms
31381_300x200.jpg
1489 ms
31725_300x200.jpg
1493 ms
32270_300x200.jpg
1569 ms
32142_300x200.jpg
1774 ms
27899_300x200.jpg
1628 ms
32001_300x200.jpg
1797 ms
32138_300x200.jpg
1764 ms
32555_300x200.jpg
1767 ms
32283_300x200.jpg
1858 ms
31596_300x200.jpg
1904 ms
32167_300x200.jpg
2039 ms
29906_300x200.jpg
2042 ms
31802_300x200.jpg
2197 ms
31501_300x200.jpg
2227 ms
31654_300x200.jpg
2140 ms
25198_300x200.jpg
2179 ms
30635_300x200.jpg
2314 ms
27765_300x200.jpg
2317 ms
25034_300x200.jpg
2418 ms
23204_300x200.jpg
2454 ms
PFDinCondensedMedium.woff
276 ms
fontic.woff
464 ms
all.js
14 ms
jquery.min.js
47 ms
suggest.js
58 ms
opensearch.js
58 ms
punycode.js
4 ms
track_tb
485 ms
22445_300x200.jpg
1971 ms
22535_300x200.jpg
2014 ms
23373_300x200.jpg
1892 ms
15691_300x200.jpg
1788 ms
18031_300x200.jpg
1783 ms
12615_300x200.jpg
1810 ms
16218_300x200.jpg
1930 ms
32707_300x200.jpg
1929 ms
32665_300x200.jpg
2069 ms
32469_300x200.jpg
2052 ms
32227_300x200.jpg
1764 ms
31590_300x200.jpg
1792 ms
31890_300x200.jpg
1858 ms
32150_300x200.jpg
1795 ms
32189_300x200.jpg
1904 ms
31702_300x200.jpg
1921 ms
31814_300x200.jpg
2005 ms
24331_300x200.jpg
2088 ms
25333_300x200.jpg
1850 ms
25008_300x200.jpg
1792 ms
28174_300x200.jpg
1774 ms
25972_300x200.jpg
1793 ms
22733_300x200.jpg
1921 ms
23309_300x200.jpg
1898 ms
26252_300x200.jpg
2083 ms
26656_300x200.jpg
1906 ms
31742_300x200.jpg
1796 ms
31820_300x200.jpg
1992 ms
32339_300x200.jpg
1829 ms
32457_300x200.jpg
1790 ms
32366_300x200.jpg
1886 ms
32338_300x200.jpg
1884 ms
31751_300x200.jpg
2082 ms
31807_300x200.jpg
1927 ms
31768_300x200.jpg
1828 ms
31771_300x200.jpg
2046 ms
31789_300x200.jpg
1775 ms
fb.ru 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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fb.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fb.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fb.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Fb.ru 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.
fb.ru
Open Graph description is not detected on the main page of FB. 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: