Access yogobe.com. Yoga, meditation, breathwork and fitness exercise online

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value19.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,320 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value33.7 s

0/100

10%

yogobe.com

296 ms

yogobe.com

741 ms

1239 ms

uc.js

26 ms

slick.css

510 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 54% of them (31 requests) were addressed to the original Yogobe.com, 32% (18 requests) were made to Yogobe-assets-shrine-production.s3.eu-north-1.amazonaws.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Yogobe-assets-shrine-production.s3.eu-north-1.amazonaws.com.

Content Size

6.6 MB

After Optimization

6.2 MB

In fact, the total size of Yogobe.com main page is 6.6 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. 60% of websites need less resources to load. Images take 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 126.3 kB

Original 151.8 kB
After minification 151.6 kB
After compression 25.5 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 126.3 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 275.6 kB

Original 6.3 MB
After minification 6.0 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. Yogobe images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 9.2 kB

Original 144.6 kB
After minification 144.6 kB
After compression 135.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. This website has mostly compressed JavaScripts.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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/).

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 Yogobe.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 Yogobe.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 data is detected on the main page of Yogobe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: