8.1 sec in total
628 ms
6 sec
1.5 sec
Welcome to brobr.ru homepage info - get ready to check Brobr best content right away, or after learning these important things about brobr.ru
Узнать подробнее о домене в магазине доменов RU-CENTER.
Visit brobr.ruWe analyzed Brobr.ru page load time and found that the first response time was 628 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.
brobr.ru performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value13.2 s
0/100
25%
Value7.0 s
33/100
10%
Value2,980 ms
3/100
30%
Value0.073
96/100
15%
Value14.6 s
8/100
10%
628 ms
759 ms
38 ms
515 ms
33 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Brobr.ru, 81% (42 requests) were made to Nado.info and 4% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Nado.info.
Page size can be reduced by 507.1 kB (47%)
1.1 MB
562.7 kB
In fact, the total size of Brobr.ru main page is 1.1 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. 60% of websites need less resources to load. HTML takes 614.4 kB which makes up the majority of the site volume.
Potential reduce by 491.9 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 491.9 kB or 80% of the original size.
Potential reduce by 9.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. Brobr images are well optimized though.
Potential reduce by 5.3 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 19 (39%)
49
30
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brobr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
brobr.ru
628 ms
ru
759 ms
css2
38 ms
hiddenBotOpenLink.js
515 ms
a9c37ce.js
33 ms
524a12c.js
32 ms
8648e85.js
28 ms
e8ec5f5.js
37 ms
2e545d4.js
54 ms
c9b852b.js
38 ms
3dc5e51.js
50 ms
b6f5dd5.js
48 ms
b77a6f9.js
60 ms
gtm.js
2435 ms
tag.js
2904 ms
openapi.js
2772 ms
fbevents.js
2435 ms
logo.dbd7f3c.svg
2332 ms
kz.be4e502.svg
2330 ms
2673a15197a86170956a1f4144e5e1cd572be6533ab832b6ffc09035be1ca3e7.jpg
2331 ms
d28800783a0b302c139b91954dc9df2f691acf305fa16401648c07f1148c8075.jpg
2330 ms
8677beae737da01814c7dd2607f432fc4564d4ee796567e00507084c8e340c31.jpg
2331 ms
29c466c3658ed6b901c73d186fcf0504b79d4504c723fca251d99d109373f4b3.jpg
2331 ms
edfb1263fa8db1fc96acdfc2700eeb69ee0fce8178b9f08a665274f70da928aa.jpg
2334 ms
9c78bc5eda71b30b511a0df0e9fbe5bf8de81dd0458d0d4f7e20af3180d4e258.jpg
2334 ms
26ed64b2eb9968899c38adc869fd7cb98c9d516d3d6154913de6ab8dbc2e1105.jpg
2333 ms
6d337e36e72140424bc4b3168b9b0f6e4fcc5cb253f1678819cb0fbf38f5d08d.jpg
2946 ms
20b5644f3a3a1dcd9fb67ed63ab04897d6c8d50e16dd3637f08b55f4dc52c964.jpg
2832 ms
304fa72c89e0d7296e218ab722297191f65b879578e0b02da664e16902be2508.jpg
2867 ms
c350ef189fabb7d87c0280abcb6f4e23e56e8a25cf008ea2c4197920a69e6e33.jpg
2831 ms
0489df01708deec909adb0adb5e3a6c5f4bb5e6ea1321714dc24ae58107fc4eb.jpg
2880 ms
693cc6b373450b18c91196d520b87c925a9bb8f21189420cf319ddd09f58fd36.jpg
2837 ms
b9a48067a4e31aac930c1e45de7d1afd72aaf5e1060ee7df6236cd362864e9d0.jpg
3392 ms
20f29c10fba99bf0922e95e2c268f256cc0e080cb838675028e5e0d806d5f3fe.jpg
3253 ms
473422930c9b3ecb812430dd8f74eb99d31c6654ffff8a79d593c2b6865d9f25.jpg
3284 ms
da2535af6e8379cf6469bb35496f3c0b31fe47e084217e3aba60fc254fcb2ad9.jpg
2982 ms
3192def20a69149268cfca0734f8f3d5278c9c6f0c28060f5f1a6eefb641110b.jpg
3518 ms
e14d64ded684d42df4cdd7726b8f1371cf60f9ed80ed7715c6c693b0d72f8f4c.jpg
3583 ms
521eb9f8c1e044a50669f197316d88f4c223ead86e5fe9740c2a7cc0aa63cf6a.jpg
3445 ms
a10de5de1b18a359a5ab16cc3c8dd1694dbda60cf0a8b0df1210e01d94e638ea.jpg
3867 ms
8afb6018b2f68f7bfd9b6ac840eb895df9460b1c86faee12c1dababc544947e0.jpg
3837 ms
50f9d83a173975672e89f81f5b2c9a2f0a2b7082668fed1f7a27451e7bfb20df.jpg
3943 ms
e334dac9d8712589e25fc91d296faa2f030621ad1c7592cece36c44343ef3bd5.jpg
4018 ms
iphone.2a8fc8d.png
3517 ms
6474fb6.js
1264 ms
8554ec7.js
1273 ms
conversion_async.js
55 ms
23 ms
57 ms
43 ms
2c452d8.js
19 ms
db0019f.js
464 ms
brobr.ru accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
brobr.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
brobr.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brobr.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Brobr.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.
brobr.ru
Open Graph description is not detected on the main page of Brobr. 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: