Tools & Wizards About Us
vemma.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

vemma.com

Bodē Pro - Ultra-premium Wellness Solutions

Page Load Speed

4.1 sec in total

First Response

961 ms

Resources Loaded

2.5 sec

Page Rendered

598 ms

vemma.com screenshot

About Website

Visit vemma.com now to see the best up-to-date Vemma content for United States and also check out these interesting facts you probably never knew about vemma.com

Bode Pro is focused on advancing cellular nutrition using cutting-edge science and technology. We're dedicated to helping you #AgeSmarter.

Visit vemma.com

Key Findings

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

Performance Metrics

vemma.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

vemma.com

961 ms

strong-og

601 ms

jquery-3.6.4.min.js

147 ms

js

79 ms

bootstrap-reboot.min.css

210 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Vemma.com, 61% (38 requests) were made to Bodepro.com and 11% (7 requests) were made to Fast.wistia.com. The less responsive or slowest element that took the longest time to load (961 ms) belongs to the original domain Vemma.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 93.2 kB (8%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vemma.com main page is 1.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. 55% of websites need less resources to load. Images take 562.4 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 29.7 kB

  • Original 41.5 kB
  • After minification 33.8 kB
  • After compression 11.8 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 7.7 kB, which is 18% 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 29.7 kB or 72% of the original size.

Image Optimization

-7%

Potential reduce by 36.9 kB

  • Original 562.4 kB
  • After minification 525.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. Vemma images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 10.3 kB

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

CSS Optimization

-17%

Potential reduce by 16.3 kB

  • Original 98.2 kB
  • After minification 97.0 kB
  • After compression 81.9 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. Vemma.com needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (63%)

Requests Now

51

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vemma.com

vemma.com

961 ms

strong-og

strong-og

601 ms

jquery-3.6.4.min.js

jquery-3.6.4.min.js

147 ms

js

js

79 ms

bootstrap-reboot.min.css

bootstrap-reboot.min.css

210 ms

bootstrap.min.css

bootstrap.min.css

281 ms

jquery-ui.min.js

jquery-ui.min.js

363 ms

jquery-ui.min.css

jquery-ui.min.css

211 ms

util.js

util.js

210 ms

tab.js

tab.js

214 ms

main.js

main.js

271 ms

main.css

main.css

274 ms

font-awesome.min.css

font-awesome.min.css

277 ms

css

css

58 ms

css

css

75 ms

snippet.js

snippet.js

66 ms

front.js

front.js

286 ms

front.css

front.css

337 ms

aak7mpp.css

aak7mpp.css

63 ms

essentials.css

essentials.css

339 ms

layout_header_footer.css

layout_header_footer.css

346 ms

design.css

design.css

342 ms

layout.css

layout.css

380 ms

header-1.css

header-1.css

413 ms

bode.css

bode.css

412 ms

jzz8x0318q.jsonp

jzz8x0318q.jsonp

43 ms

E-v1.js

E-v1.js

58 ms

scripts.js

scripts.js

560 ms

css

css

18 ms

p.css

p.css

33 ms

fbevents.js

fbevents.js

150 ms

us.png

us.png

127 ms

logo_blue_800x179.jpg

logo_blue_800x179.jpg

308 ms

liquidCellularNutrition.png

liquidCellularNutrition.png

149 ms

Strong-OG-Bottle21.png

Strong-OG-Bottle21.png

308 ms

isClinicallyStudied_new.png

isClinicallyStudied_new.png

126 ms

iconPDF.png

iconPDF.png

308 ms

logo_white_800x179.png

logo_white_800x179.png

307 ms

icon-mapPin.png

icon-mapPin.png

306 ms

icon-phone.png

icon-phone.png

306 ms

icon-mail.png

icon-mail.png

368 ms

icon-fax.png

icon-fax.png

369 ms

icon-fb.png

icon-fb.png

368 ms

icon-instagram.png

icon-instagram.png

367 ms

icon-twitter.png

icon-twitter.png

369 ms

d

d

130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

203 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

273 ms

d

d

289 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

290 ms

d

d

201 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

289 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

291 ms

battleRopes.jpg

battleRopes.jpg

483 ms

burnVidBG.jpg

burnVidBG.jpg

482 ms

scienceStripBG.jpg

scienceStripBG.jpg

462 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

462 ms

popover.js

popover.js

144 ms

flashPlayer.js

flashPlayer.js

5 ms

postRoll-v2.js

postRoll-v2.js

26 ms

captions.js

captions.js

36 ms

share-v2.js

share-v2.js

11 ms

Accessibility Review

vemma.com accessibility score

83

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

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

vemma.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

vemma.com SEO score

75

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vemma.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Vemma.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

vemma.com

Open Graph data is detected on the main page of Vemma. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: