2.5 sec in total
333 ms
1.9 sec
202 ms
Welcome to herbalife.ru homepage info - get ready to check HERBALIFE best content for Russia right away, or after learning these important things about herbalife.ru
Visit herbalife.ruWe analyzed Herbalife.ru page load time and found that the first response time was 333 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
herbalife.ru performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value21.7 s
0/100
25%
Value18.3 s
0/100
10%
Value15,870 ms
0/100
30%
Value0.196
63/100
15%
Value25.9 s
0/100
10%
333 ms
97 ms
192 ms
7 ms
289 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 51% of them (36 requests) were addressed to the original Herbalife.ru, 16% (11 requests) were made to Vk.com and 6% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (841 ms) belongs to the original domain Herbalife.ru.
Page size can be reduced by 803.2 kB (36%)
2.2 MB
1.4 MB
In fact, the total size of Herbalife.ru main page is 2.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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 33.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 6.8 kB, which is 16% 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 33.2 kB or 79% of the original size.
Potential reduce by 6.2 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. HERBALIFE images are well optimized though.
Potential reduce by 485.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 485.1 kB or 70% of the original size.
Potential reduce by 278.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. Herbalife.ru needs all CSS files to be minified and compressed as it can save up to 278.8 kB or 83% of the original size.
Number of requests can be reduced by 38 (60%)
63
25
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HERBALIFE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
herbalife.ru
333 ms
base.css
97 ms
hbx.js
192 ms
jquery-1.10.2.min.js
7 ms
s_code.js
289 ms
AC_RunActiveContent.js
188 ms
swfobject.js
218 ms
openapi.js
380 ms
jquery.jcarousel.min.js
224 ms
jquery.min.js
35 ms
user1.js
215 ms
amazon_scroller.js
281 ms
skin.css
282 ms
easypaginate.js
280 ms
watch.js
169 ms
watch.js
440 ms
s51448817115742
12 ms
body_bkg.jpg
127 ms
2011_bg_head.jpg
96 ms
icon_arrow.gif
824 ms
2011_bg_head_right.jpg
97 ms
2011_logo.jpg
101 ms
2011_btn_search_.jpg
100 ms
HRB_cream_coct_banner.jpg
471 ms
Banner_Bud_v_forme.jpg
281 ms
baner_woman_skin.jpg
552 ms
banner_23-07-2015.jpg
565 ms
06-04-2015.jpg
407 ms
550x254.jpg
568 ms
NADN_F1_banner_HLru.jpg
653 ms
banner-ronaldo.jpg
665 ms
banner_pitanie_laureat.jpg
568 ms
f1-1.jpg
783 ms
winter15-16.jpg
785 ms
circle.gif
665 ms
icon-youtube.gif
667 ms
institut_pitania4.jpg
841 ms
RDSA_Logo_Pantone2.jpg
785 ms
arrow-down.png
779 ms
bs_fon.jpg
780 ms
upload.gif
126 ms
widget_community.php
281 ms
3zxtElIJF68
103 ms
connect.js
624 ms
www-embed-player-vflZsBgOl.css
60 ms
www-embed-player.js
90 ms
base.js
165 ms
loader_nav19127_3.js
139 ms
lite.css
140 ms
lite.js
452 ms
lang3_0.js
257 ms
widget_community.css
260 ms
xdm.js
272 ms
al_community.js
273 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
20 ms
ad_status.js
62 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
70 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
80 ms
spartak_banner_bg.jpg
134 ms
2011_bg_footer.gif
152 ms
advert.gif
103 ms
analytics.js
60 ms
f5qVVkMUyWE.jpg
396 ms
arrow.png
99 ms
bg_buttons.png
99 ms
w_logo.png
126 ms
collect
12 ms
collect
55 ms
ga-audiences
19 ms
1
85 ms
herbalife.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
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
herbalife.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
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
herbalife.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use legible font sizes
Tap targets are not sized appropriately
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Herbalife.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 Herbalife.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.
herbalife.ru
Open Graph description is not detected on the main page of HERBALIFE. 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: