Tools & Wizards About Us
shop.gettinghealthier.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

shop.gettinghealthier.com

Getting Healthier Cancer and Immune Support Nutrition Supplements and Books

Page Load Speed

2.3 sec in total

First Response

84 ms

Resources Loaded

1.2 sec

Page Rendered

1.1 sec

shop.gettinghealthier.com screenshot

About Website

Visit shop.gettinghealthier.com now to see the best up-to-date Shop Getting Healthier content for United States and also check out these interesting facts you probably never knew about shop.gettinghealthier.com

Online vitamins and minerals nutrition supplements along with best selling books. Based in California.

Visit shop.gettinghealthier.com

Key Findings

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

Performance Metrics

shop.gettinghealthier.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value17.9 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value4,340 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.5 s

0/100

10%

Network Requests Diagram

shop.gettinghealthier.com

84 ms

shop.gettinghealthier.com

505 ms

theme-bundle.polyfills.js

351 ms

theme-bundle.head_async.js

72 ms

css

72 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Shop.gettinghealthier.com, 38% (16 requests) were made to Cdn11.bigcommerce.com and 12% (5 requests) were made to Sdk.beeketing.com. The less responsive or slowest element that took the longest time to load (505 ms) belongs to the original domain Shop.gettinghealthier.com.

Page Optimization Overview & Recommendations

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

Content Size

1.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Shop.gettinghealthier.com main page is 1.9 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 125.8 kB

  • Original 150.1 kB
  • After minification 122.1 kB
  • After compression 24.4 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 28.1 kB, which is 19% 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 125.8 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 10 B

  • Original 1.5 MB
  • After minification 1.5 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. Shop Getting Healthier images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

  • Original 259.6 kB
  • After minification 259.6 kB
  • After compression 258.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.

Requests Breakdown

Number of requests can be reduced by 23 (64%)

Requests Now

36

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

shop.gettinghealthier.com

shop.gettinghealthier.com

84 ms

shop.gettinghealthier.com

shop.gettinghealthier.com

505 ms

theme-bundle.polyfills.js

theme-bundle.polyfills.js

351 ms

theme-bundle.head_async.js

theme-bundle.head_async.js

72 ms

css

css

72 ms

theme-bundle.font.js

theme-bundle.font.js

177 ms

theme-c843d2b0-5b36-013d-6819-1e55b31ddb0b.css

theme-c843d2b0-5b36-013d-6819-1e55b31ddb0b.css

90 ms

google_analytics4-9a468da7c21d2e9e41cd445d567f3f3a5a9b6759.js

google_analytics4-9a468da7c21d2e9e41cd445d567f3f3a5a9b6759.js

85 ms

loader.js

loader.js

80 ms

ga.js

ga.js

87 ms

js

js

209 ms

index.js

index.js

86 ms

platform.js

platform.js

67 ms

theme-bundle.main.js

theme-bundle.main.js

82 ms

axios.min.js

axios.min.js

84 ms

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

183 ms

platform.js

platform.js

119 ms

fbevents.js

fbevents.js

106 ms

jmwdi5rpia

jmwdi5rpia

219 ms

j.php

j.php

132 ms

ga.js

ga.js

104 ms

kf6azry405

kf6azry405

259 ms

m9izzf4nbv

m9izzf4nbv

258 ms

getting-healthier-best-of-nature_1493693418__45596.original.png

getting-healthier-best-of-nature_1493693418__45596.original.png

86 ms

ip-hero-july-2024.jpg

ip-hero-july-2024.jpg

87 ms

ipg-gr-july-2024.png

ipg-gr-july-2024.png

86 ms

SInus-1000-PNG__74526.1689089644.png

SInus-1000-PNG__74526.1689089644.png

86 ms

Immunopower-Gold-Turmeric-June-2024__61580.1721955157.png

Immunopower-Gold-Turmeric-June-2024__61580.1721955157.png

84 ms

BCN-PNG__96755.1689533646.png

BCN-PNG__96755.1689533646.png

165 ms

phone-consultation-Sept-2024__89036.1726795662.jpg

phone-consultation-Sept-2024__89036.1726795662.jpg

164 ms

collage.jpg

collage.jpg

166 ms

beeketing.js

beeketing.js

201 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

17 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

41 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

42 ms

clarity.js

clarity.js

86 ms

beeketing.0.41fa4b0af8d6bfceac2f.js

beeketing.0.41fa4b0af8d6bfceac2f.js

41 ms

beeketing.1.19d05760fa520b2970db.js

beeketing.1.19d05760fa520b2970db.js

58 ms

beeketing.3.f475d5839949f0aad803.js

beeketing.3.f475d5839949f0aad803.js

51 ms

beeketing.131.849372d45e7048adcda7.js

beeketing.131.849372d45e7048adcda7.js

59 ms

nobot

nobot

92 ms

c.gif

c.gif

8 ms

Accessibility Review

shop.gettinghealthier.com accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Tables and lists

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

Impact

Issue

High

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

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

shop.gettinghealthier.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

High

Missing source maps for large first-party JavaScript

SEO Factors

shop.gettinghealthier.com SEO score

93

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

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 Shop.gettinghealthier.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 Shop.gettinghealthier.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

shop.gettinghealthier.com

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