Tools & Wizards About Us
vitalizerx.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

vitalizerx.com

Down for Maintenance – please come back again soon! – VitalizeRx.com

Page Load Speed

2.1 sec in total

First Response

150 ms

Resources Loaded

1.8 sec

Page Rendered

92 ms

vitalizerx.com screenshot

About Website

Click here to check amazing Vitalize Rx content. Otherwise, check out these important facts you probably never knew about vitalizerx.com

Visit vitalizerx.com

Key Findings

We analyzed Vitalizerx.com page load time and found that the first response time was 150 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

vitalizerx.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

54/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.183

66/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

vitalizerx.com

150 ms

css

55 ms

style.min.css

36 ms

VitalizeRx-Logo1.png

54 ms

Patty_2022-87873_74x74.jpg

87 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 33% of them (19 requests) were addressed to the original Vitalizerx.com, 29% (17 requests) were made to C0.wp.com and 19% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (614 ms) belongs to the original domain Vitalizerx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 209.3 kB (40%)

Content Size

522.4 kB

After Optimization

313.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vitalizerx.com main page is 522.4 kB. 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. HTML takes 248.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 204.5 kB

  • Original 248.3 kB
  • After minification 247.2 kB
  • After compression 43.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. 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 204.5 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 2.1 kB

  • Original 43.4 kB
  • After minification 41.2 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. Vitalize Rx images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 946 B

  • Original 174.1 kB
  • After minification 174.1 kB
  • After compression 173.2 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

-3%

Potential reduce by 1.7 kB

  • Original 56.6 kB
  • After minification 56.4 kB
  • After compression 54.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. Vitalizerx.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (81%)

Requests Now

42

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vitalizerx.com

vitalizerx.com

150 ms

css

css

55 ms

style.min.css

style.min.css

36 ms

VitalizeRx-Logo1.png

VitalizeRx-Logo1.png

54 ms

Patty_2022-87873_74x74.jpg

Patty_2022-87873_74x74.jpg

87 ms

VitalizeRx-Logo1.png

VitalizeRx-Logo1.png

98 ms

Footer-Icons-Green.png

Footer-Icons-Green.png

127 ms

loader.js

loader.js

95 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

13 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

31 ms

wp-polyfill.min.js

wp-polyfill.min.js

35 ms

hooks.min.js

hooks.min.js

51 ms

w.js

w.js

59 ms

vitalizerx.com

vitalizerx.com

614 ms

jquery.min.js

jquery.min.js

50 ms

jquery-migrate.min.js

jquery-migrate.min.js

34 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

46 ms

add-to-cart.min.js

add-to-cart.min.js

53 ms

js.cookie.min.js

js.cookie.min.js

58 ms

woocommerce.min.js

woocommerce.min.js

58 ms

s-202401.js

s-202401.js

74 ms

image-cdn.js

image-cdn.js

92 ms

scripts.min.js

scripts.min.js

161 ms

jquery.fitvids.js

jquery.fitvids.js

129 ms

cpt-modules-wrapper.js

cpt-modules-wrapper.js

127 ms

xoo-wsc-main.js

xoo-wsc-main.js

129 ms

common.js

common.js

128 ms

e-202401.js

e-202401.js

72 ms

css

css

51 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

85 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

92 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

98 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

17 ms

g.gif

g.gif

41 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

17 ms

woocommerce-layout.css

woocommerce-layout.css

5 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

11 ms

woocommerce.css

woocommerce.css

9 ms

jetpack.css

jetpack.css

8 ms

g.gif

g.gif

67 ms

modules.woff

modules.woff

42 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf

9 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf

11 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf

10 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf

9 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf

10 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf

11 ms

echeck-custom.css

echeck-custom.css

28 ms

xoo-wsc-fonts.css

xoo-wsc-fonts.css

27 ms

xoo-wsc-style.css

xoo-wsc-style.css

29 ms

Woo-Side-Cart.woff

Woo-Side-Cart.woff

43 ms

wc-custom-add-to-cart.min.css

wc-custom-add-to-cart.min.css

29 ms

checkout-blocks.css

checkout-blocks.css

28 ms

woocommerce.css

woocommerce.css

28 ms

style.css

style.css

29 ms

v5ttwu8txcgjuinha1vre696bw7hqhq7.js

v5ttwu8txcgjuinha1vre696bw7hqhq7.js

140 ms

Accessibility Review

vitalizerx.com accessibility score

89

Accessibility Issues

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

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

vitalizerx.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

vitalizerx.com SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

vitalizerx.com

Open Graph description is not detected on the main page of Vitalize Rx. 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: