Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 68

    SEO

    Google-friendlier than
    27% of websites

herbalife.ru

Главная HERBALIFE

Page Load Speed

6.1 sec in total

First Response

370 ms

Resources Loaded

5.2 sec

Page Rendered

535 ms

herbalife.ru screenshot

About Website

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.ru

Key Findings

We 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.

Performance Metrics

herbalife.ru performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value23.4 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.366

29/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 597.9 kB (13%)

Content Size

4.5 MB

After Optimization

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.

HTML Optimization

-83%

Potential reduce by 261.0 kB

  • Original 313.0 kB
  • After minification 261.6 kB
  • After compression 51.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. 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.

Image Optimization

-3%

Potential reduce by 120.5 kB

  • Original 3.7 MB
  • After minification 3.6 MB

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.

JavaScript Optimization

-48%

Potential reduce by 216.4 kB

  • Original 449.0 kB
  • After minification 449.0 kB
  • After compression 232.7 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.

Requests Breakdown

Number of requests can be reduced by 44 (37%)

Requests Now

118

After Optimization

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.

Accessibility Review

herbalife.ru accessibility score

65

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

herbalife.ru best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

herbalife.ru SEO score

68

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    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.

Social Sharing Optimization

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: