7.4 sec in total
1.5 sec
5.2 sec
699 ms
Click here to check amazing Whats Better content for Russia. Otherwise, check out these important facts you probably never knew about whatsbetter.ru
Хочешь узнать, что лучше? Ищи ответ на WhatsBetter.ru. Сравнительные обзоры, рейтинги марок, аналитические статьи, мнения. Максимум полезной информации в одном месте.
Visit whatsbetter.ruWe analyzed Whatsbetter.ru page load time and found that the first response time was 1.5 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
whatsbetter.ru performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value6.5 s
9/100
25%
Value5.1 s
61/100
10%
Value780 ms
38/100
30%
Value0.15
76/100
15%
Value7.0 s
53/100
10%
1481 ms
262 ms
266 ms
269 ms
273 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 89% of them (84 requests) were addressed to the original Whatsbetter.ru, 3% (3 requests) were made to S7.addthis.com and 2% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Whatsbetter.ru.
Page size can be reduced by 821.3 kB (47%)
1.7 MB
920.2 kB
In fact, the total size of Whatsbetter.ru main page is 1.7 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. 40% of websites need less resources to load. Javascripts take 738.8 kB which makes up the majority of the site volume.
Potential reduce by 175.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 175.1 kB or 81% of the original size.
Potential reduce by 10.3 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. Whats Better images are well optimized though.
Potential reduce by 540.6 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 540.6 kB or 73% of the original size.
Potential reduce by 95.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. Whatsbetter.ru needs all CSS files to be minified and compressed as it can save up to 95.2 kB or 86% of the original size.
Number of requests can be reduced by 42 (46%)
91
49
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whats Better. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
whatsbetter.ru
1481 ms
all.css
262 ms
page_e4d8fd7c89f2eb08383bf8934ca28db1_587a1fca658bcac984ad5c94b8c45fea.css
266 ms
kernel_main.css
269 ms
kernel_socialservices.css
273 ms
template_709034c05da7c6ba0d1cf8ff9ebab213_673a611f07f1895b4afd0fd7ed1a1ed7.css
282 ms
kernel_main.js
926 ms
ajax.js
659 ms
kernel_socialservices.js
390 ms
template_2af0431e49ddae6e009ef133acb9e041_dffb58b56e8788ffca36374028f6099b.js
395 ms
api.js
403 ms
addthis_widget.js
55 ms
watch.js
26 ms
bg_fill.gif
137 ms
header_bg.png
136 ms
wb.jpg
799 ms
whatsbetter.gif
147 ms
icon_home.gif
136 ms
icon_search.gif
127 ms
icon_send.gif
310 ms
icons.png
408 ms
1.gif
311 ms
menu_bg_top.png
312 ms
menu_bg_bottom.png
313 ms
plus.gif
399 ms
banner_expo.jpg
927 ms
pr_phone.png
486 ms
pr_tablet.png
486 ms
pr_photo.png
580 ms
pr_note.png
590 ms
pr_tv.png
626 ms
1_phone.png
645 ms
2_tv.png
801 ms
3_photo.png
824 ms
4_video2.png
840 ms
5_laptop.png
852 ms
6_tablet.png
955 ms
13_mp3.png
955 ms
8_ebook.png
973 ms
9_printer.png
983 ms
10_monitor.png
996 ms
7_console.png
1075 ms
11_headphones.png
1277 ms
10_mouse.png
1144 ms
14_gps.png
1304 ms
13_av.png
1322 ms
14_browser.png
1324 ms
main62.jpg
1620 ms
main63.jpg
1602 ms
hirequest.js
1497 ms
main60.jpg
1436 ms
main59.jpg
2134 ms
main58.jpg
1491 ms
hit
264 ms
300lo.json
54 ms
main55.jpg
1663 ms
sh.953eb77977227bfd253ee158.html
38 ms
layers.486057f6e3ab422798c9.js
19 ms
main54.jpg
1747 ms
main53.jpg
1615 ms
main6.jpg
1632 ms
main49.jpg
1651 ms
noavatar.png
1570 ms
comment_add.png
1664 ms
hit
131 ms
konkurs7.png
1823 ms
bg-mostcomm.png
1644 ms
search_bg.png
1547 ms
plashka0_bgr.png
1646 ms
plashka0_1a.png
1695 ms
empty.gif
1687 ms
about_bgr_top.png
1561 ms
about_bgr_bottom.png
1565 ms
plashka1_bgr.png
1750 ms
plashka1_1a.png
1603 ms
plashka4m_bgr.png
1619 ms
plashka4m_1a.png
1546 ms
plashka3_bgr.png
1534 ms
icon_about3.png
1539 ms
plashka3_1a.png
1633 ms
nrav_act.png
1619 ms
nenrav_act.png
1607 ms
plashkaq_bg.png
1547 ms
plashkaq_1a.png
1491 ms
comments_bgr_topq.png
1562 ms
comments_bgr_bottom.png
1429 ms
plashkak_bgr.png
1572 ms
plashkak_2a.png
1432 ms
share.php
290 ms
fql
171 ms
shares.json
62 ms
konkurs_bgr_top.png
1217 ms
konkurs_bgr_bottom.png
1207 ms
right_shadow.gif
1241 ms
whatsbetter.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.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
whatsbetter.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
whatsbetter.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
RU
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatsbetter.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 Whatsbetter.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
whatsbetter.ru
Open Graph description is not detected on the main page of Whats Better. 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: