6.1 sec in total
370 ms
5.2 sec
535 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 370 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
herbalife.ru performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value23.4 s
0/100
25%
Value12.5 s
3/100
10%
Value1,000 ms
27/100
30%
Value0.366
29/100
15%
Value17.0 s
4/100
10%
370 ms
1119 ms
57 ms
157 ms
244 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 87% of them (109 requests) were addressed to the original Herbalife.ru, 5% (6 requests) were made to Cdn.cookielaw.org and 3% (4 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Herbalife.ru.
Page size can be reduced by 597.9 kB (13%)
4.5 MB
3.9 MB
In fact, the total size of Herbalife.ru main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 261.0 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 51.4 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 261.0 kB or 83% of the original size.
Potential reduce by 120.5 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 216.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 216.4 kB or 48% of the original size.
Number of requests can be reduced by 44 (37%)
118
74
The browser has sent 118 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 21 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
herbalife.ru
370 ms
herbalife.ru
1119 ms
launch-ENa1fb3d1a2f964119b26e49d54e214a6e.min.js
57 ms
ui.design-tokens.min.css
157 ms
ui.font.opensans.min.css
244 ms
main.popup.bundle.min.css
363 ms
page_6afbb53f21238b867a3a7fece007e922_v1.css
365 ms
template_48c898b232655e98db8b5e285575ae36_v1.css
730 ms
css
43 ms
js
96 ms
core.min.js
617 ms
kernel_main_v1.js
609 ms
dexie3.bundle.min.js
497 ms
core_ls.min.js
476 ms
core_frame_cache.min.js
476 ms
main.popup.bundle.min.js
717 ms
optimize.js
77 ms
template_1594bc51a73f492884993d0b8ca14a64_v1.js
1201 ms
page_6f0153d9e0baef63ace1b5163496d430_v1.js
622 ms
sourcebuster.min.js
926 ms
lk5119mvfjcaa.js
982 ms
EX2175ae2789324e2798a4c325d1a9f4be-libraryCode_source.min.js
13 ms
logo.svg
125 ms
logo-gold_standart.png
121 ms
telephone.svg
128 ms
search-green.svg
128 ms
image_16.svg
122 ms
sprite.svg
241 ms
twemoji_flag-for-flag-russia.png
245 ms
twemoji_flag-for-flag-armenia.png
244 ms
twemoji_flag-for-flag-azerbaijan.png
249 ms
twemoji_flag-for-flag-belarus.png
251 ms
twemoji_flag-for-flag-estonia.png
411 ms
twemoji_flag-for-flag-estonia.png
410 ms
twemoji_flag-for-flag-georgia.png
411 ms
twemoji_flag-for-flag-kazakhstan.png
409 ms
twemoji_flag-for-flag-kazakhstan.png
410 ms
twemoji_flag-for-flag-kyrgyzstan.png
691 ms
twemoji_flag-for-flag-latvia.png
689 ms
twemoji_flag-for-flag-lithuania.png
689 ms
twemoji_flag-for-flag-mongolia.png
690 ms
twemoji_flag-for-flag-uzbekistan.png
688 ms
twemoji_flag-for-flag-uzbekistan.png
689 ms
bx_bx-globe%20(1).png
807 ms
sprite.svg
805 ms
Gde_priobretat_produktsiyu_1920kh450_2_.jpg
1056 ms
Herbalife_banner_1920x450_Ronaldu_Preview.jpg
1184 ms
%D0%97%D0%B0%D0%B1%D0%BE%D1%82%D0%B0-%D0%BE-%D0%B1%D0%BB%D0%B8%D0%B7%D0%BA%D0%B8%D1%85-1920.jpg
1163 ms
%D0%92%D0%B8%D0%B4%D0%B8%D0%BC%D1%8B%D0%B9-%D1%80%D0%B5%D0%B7%D1%83%D0%BB%D1%8C%D1%82%D0%B0%D1%82-1920.jpg
872 ms
%D0%A4%D0%BE%D0%BE%D1%80%D0%BC%D1%83%D0%BB%D0%B0-1920.jpg
1285 ms
Mark_KHyuz_1.jpg
1769 ms
2-_-do-minus-2-razmerov-1920kh450.jpg
1228 ms
image_11.svg
1179 ms
image_12.svg
1282 ms
image_13.svg
1305 ms
otSDKStub.js
100 ms
image_14.svg
1241 ms
NotoSans-Regular.woff
1401 ms
8a81f1a9-45d1-487b-a8a3-d69057463bd1.json
26 ms
NotoSans-Medium.woff
1288 ms
NotoSans-Light.woff
1307 ms
NotoSans-Thin.woff
1435 ms
NotoSans-Bold.woff
1454 ms
image_15.svg
1402 ms
location
59 ms
otBannerSdk.js
20 ms
ru-ru.json
32 ms
F1_508%D1%85685.jpg
1289 ms
image_22.svg
1378 ms
image_23.svg
1404 ms
image_21.svg
1402 ms
2-508x685.png
1433 ms
otFlat.json
67 ms
otPcCenter.json
89 ms
emvxvwmmrl
346 ms
Tea_L178KRS-HTC-classic-51-g_preview_01_02.png
1283 ms
package_Liftoff.png
1305 ms
HLF_F1_sport_508x685px_preview.png
1360 ms
508kh685(2).png
1358 ms
0267.png
1399 ms
Collagen.png
1403 ms
Tovar_Goda_Zvezda_2020_v_kruge.png
1146 ms
508x685.png
1199 ms
GreenMax.png
1199 ms
zdorpit_logo_circle-2021.png
1203 ms
aloe%20mango%20508%D1%85685.png
1244 ms
%D0%92%D1%8B%D0%B1%D0%BE%D1%80_%D0%B3%D0%BE%D0%B4%D0%B02020.png
1248 ms
%D0%9F%D1%80%D0%BE%D1%82%D0%B5%D0%B8%D0%BD%D0%BE%D0%B2%D1%8B%D0%B9%20%D0%BA%D0%BE%D1%84%D0%B5.png
1148 ms
arrow__right.svg
1199 ms
icon-calc-men-60-transperent.png
1134 ms
icon-calc-women-60-transperent.png
956 ms
%D0%97%D0%B0%D0%B2%D1%82%D1%80%D0%B0%D0%BA.png
893 ms
%D0%A1%D0%B1%D0%B0%D0%BB%D0%B0%D0%BD%D1%81%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%BD%D0%BE%D0%B5%20%D0%BF%D0%B8%D1%82%D0%B0%D0%BD%D0%B8%D0%B5.png
882 ms
%D0%AD%D0%BD%D0%B5%D1%80%D0%B3%D0%B8%D1%8F.png
890 ms
Programm%20Image.jpg
898 ms
%D0%9F%D0%BE%D0%B4%D0%B4%D0%B5%D1%80%D0%B6%D0%BA%D0%B0%20%D0%BF%D0%B8%D1%89%D0%B5%D0%B2%D0%B0%D1%80%D0%B5%D0%BD%D0%B8%D1%8F.png
843 ms
%D0%96%D0%B5%D0%BD%D1%81%D0%BA%D0%B0%D1%8F%20%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B0.png
1088 ms
%D0%97%D0%B4%D0%BE%D1%80%D0%BE%D0%B2%D1%8B%D0%B5%20%D0%BF%D0%B5%D1%80%D0%B5%D0%BA%D1%83%D1%81%D1%8B.png
874 ms
320%D1%85320.jpg
880 ms
%D0%9F%D0%BE%D0%B4%D0%B4%D0%B5%D1%80%D0%B6%D0%BA%D0%B0%20%D0%B8%D0%BC%D0%BC%D1%83%D0%BD%D0%B8%D1%82%D0%B5%D1%82%D0%B0.png
770 ms
%D0%A1%D0%BD%D0%B8%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20%D0%B2%D0%B5%D1%81%D0%B0.png
782 ms
%D0%9F%D0%BE%D0%B4%D0%B4%D0%B5%D1%80%D0%B6%D0%BA%D0%B0%20%D1%81%D0%B5%D1%80%D0%B4%D1%86%D0%B0%20%D0%B8%20%D1%81%D0%BE%D1%81%D1%83%D0%B4%D0%BE%D0%B2%20%28%D0%BF%D1%80%D0%BE%D0%B4%D1%83%D0%BA%D1%82%20%D0%B7%D0%B0%D0%BC%D0%B5%D0%BD%D0%B5%D0%BD%29.jpg
761 ms
card-blog-img-1.jpg
781 ms
card-blog-img-2.jpg
788 ms
protein-anons-min.jpg
741 ms
card-blog-img-5.jpg
753 ms
bud_v_forme_2.jpg
753 ms
Proekty_Gerbalayf_instagram_desktop-mob.jpg
785 ms
social_youtube-mob.jpg
794 ms
bud_v_forme_2-mob.jpg
755 ms
Proekty_Gerbalayf_myHl_desktop-mob.jpg
803 ms
Proekty_Gerbalayf_PRK_desktop-mob.jpg
777 ms
gkshow1-mob.png
731 ms
image_27.svg
791 ms
image_33.svg
787 ms
image_30.svg
760 ms
image_31.svg
797 ms
image_32.svg
779 ms
RDSA_Logo_25_let_footer.jpg
732 ms
image_28.svg
790 ms
google_play.svg
791 ms
app_store.svg
761 ms
popup_page_out.png
792 ms
RC0ef2c4bbe6244254ae7738401836ad15-source.min.js
9 ms
RC79b7f90a7a0541c595f6a9514c83a8fc-source.min.js
10 ms
c.gif
7 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
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
RU
UTF-8
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 it matches the claimed language. Our system also found out that Herbalife.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.
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: