Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

viobin.com

Viobin – VIOBIN | CBD | Wheat Germ | Wheat Germ Oil

Page Load Speed

3.6 sec in total

First Response

245 ms

Resources Loaded

2.5 sec

Page Rendered

856 ms

viobin.com screenshot

About Website

Click here to check amazing Viobin content. Otherwise, check out these important facts you probably never knew about viobin.com

Visit viobin.com

Key Findings

We analyzed Viobin.com page load time and found that the first response time was 245 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

viobin.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value1,890 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

viobin.com

245 ms

viobin.com

361 ms

wc-square-cart-checkout-blocks.min.css

41 ms

theme.min.css

146 ms

style.css

48 ms

Our browser made a total of 195 requests to load all elements on the main page. We found that 88% of them (171 requests) were addressed to the original Viobin.com, 5% (9 requests) were made to Fonts.gstatic.com and 3% (6 requests) were made to Scontent-iad3-2.cdninstagram.com. The less responsive or slowest element that took the longest time to load (605 ms) belongs to the original domain Viobin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 229.1 kB (7%)

Content Size

3.1 MB

After Optimization

2.8 MB

In fact, the total size of Viobin.com main page is 3.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. Only a small number of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 168.7 kB

  • Original 202.3 kB
  • After minification 194.1 kB
  • After compression 33.6 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 168.7 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 60.3 kB

  • Original 2.8 MB
  • After minification 2.8 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. Viobin images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 79 B

  • Original 35.9 kB
  • After minification 35.9 kB
  • After compression 35.8 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.

CSS Optimization

-23%

Potential reduce by 88 B

  • Original 376 B
  • After minification 376 B
  • After compression 288 B

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. Viobin.com needs all CSS files to be minified and compressed as it can save up to 88 B or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 144 (86%)

Requests Now

167

After Optimization

23

The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viobin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 92 to 1 for JavaScripts and from 54 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

viobin.com accessibility score

93

Accessibility Issues

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

viobin.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

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

viobin.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viobin.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Viobin.com 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 Viobin. 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: