Tools & Wizards About Us
truhealthy.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

truhealthy.com

Truhealthy – Tru Nutrition for Healthy Living

Page Load Speed

8.4 sec in total

First Response

739 ms

Resources Loaded

7.5 sec

Page Rendered

126 ms

truhealthy.com screenshot

About Website

Visit truhealthy.com now to see the best up-to-date Truhealthy content and also check out these interesting facts you probably never knew about truhealthy.com

Visit truhealthy.com

Key Findings

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

Performance Metrics

truhealthy.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

truhealthy.com

739 ms

truhealthy.com

1014 ms

truhealthy.org

1276 ms

mediaelementplayer-legacy.min.css

237 ms

wp-mediaelement.min.css

471 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Truhealthy.com, 80% (61 requests) were made to Truhealthy.org and 9% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Truhealthy.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 93.7 kB (13%)

Content Size

696.1 kB

After Optimization

602.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Truhealthy.com main page is 696.1 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. Images take 272.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 46.7 kB

  • Original 61.0 kB
  • After minification 60.5 kB
  • After compression 14.3 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 46.7 kB or 77% of the original size.

Image Optimization

-16%

Potential reduce by 44.6 kB

  • Original 272.3 kB
  • After minification 227.7 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. Obviously, Truhealthy needs image optimization as it can save up to 44.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 427 B

  • Original 233.4 kB
  • After minification 233.4 kB
  • After compression 233.0 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

-1%

Potential reduce by 1.9 kB

  • Original 129.3 kB
  • After minification 129.3 kB
  • After compression 127.4 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. Truhealthy.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 60 (91%)

Requests Now

66

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

truhealthy.com

truhealthy.com

739 ms

truhealthy.com

truhealthy.com

1014 ms

truhealthy.org

truhealthy.org

1276 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

237 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

471 ms

woocommerce-layout.css

woocommerce-layout.css

705 ms

woocommerce.css

woocommerce.css

707 ms

header-footer-elementor.css

header-footer-elementor.css

704 ms

frontend-lite.min.css

frontend-lite.min.css

717 ms

swiper.min.css

swiper.min.css

715 ms

post-7.css

post-7.css

720 ms

post-159.css

post-159.css

937 ms

fluent-forms-elementor-widget.css

fluent-forms-elementor-widget.css

938 ms

frontend.css

frontend.css

940 ms

post-65.css

post-65.css

953 ms

post-77.css

post-77.css

955 ms

style.min.css

style.min.css

957 ms

theme.min.css

theme.min.css

1170 ms

header-footer.min.css

header-footer.min.css

1171 ms

ekiticons.css

ekiticons.css

1175 ms

widget-styles.css

widget-styles.css

1202 ms

responsive.css

responsive.css

1192 ms

general.min.css

general.min.css

1195 ms

css

css

63 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1403 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1406 ms

wp-polyfill.min.js

wp-polyfill.min.js

1413 ms

hooks.min.js

hooks.min.js

1434 ms

w.js

w.js

48 ms

jquery.min.js

jquery.min.js

1439 ms

jquery-migrate.min.js

jquery-migrate.min.js

1453 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1642 ms

add-to-cart.min.js

add-to-cart.min.js

1643 ms

js.cookie.min.js

js.cookie.min.js

1646 ms

woocommerce.min.js

woocommerce.min.js

1663 ms

s-202410.js

s-202410.js

49 ms

fluent-forms-public.css

fluent-forms-public.css

1683 ms

fluentform-public-default.css

fluentform-public-default.css

1680 ms

photoswipe.min.css

photoswipe.min.css

1875 ms

default-skin.min.css

default-skin.min.css

1876 ms

sourcebuster.min.js

sourcebuster.min.js

1891 ms

e-202410.js

e-202410.js

47 ms

order-attribution.min.js

order-attribution.min.js

1899 ms

dom-ready.min.js

dom-ready.min.js

1691 ms

main.js

main.js

1459 ms

hello-frontend.min.js

hello-frontend.min.js

1411 ms

frontend-script.js

frontend-script.js

1412 ms

widget-scripts.js

widget-scripts.js

1416 ms

general.min.js

general.min.js

1426 ms

webpack.runtime.min.js

webpack.runtime.min.js

1445 ms

frontend-modules.min.js

frontend-modules.min.js

1450 ms

waypoints.min.js

waypoints.min.js

1413 ms

core.min.js

core.min.js

1423 ms

frontend.min.js

frontend.min.js

1419 ms

animate-circle.min.js

animate-circle.min.js

1430 ms

elementor.js

elementor.js

1447 ms

jquery.zoom.min.js

jquery.zoom.min.js

1454 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

1412 ms

photoswipe.min.js

photoswipe.min.js

1423 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

1415 ms

underscore.min.js

underscore.min.js

1428 ms

wp-util.min.js

wp-util.min.js

1451 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

1431 ms

single-product.min.js

single-product.min.js

1412 ms

g.gif

g.gif

44 ms

pexels-photo-1103970.jpeg

pexels-photo-1103970.jpeg

1597 ms

Truhealthy-Final-Logo-NEW-FOR-VIDEO-PNG-1024x843.png

Truhealthy-Final-Logo-NEW-FOR-VIDEO-PNG-1024x843.png

2063 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

20 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

23 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

29 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

36 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

33 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

36 ms

raxkHiKDttkTe1aOGcJMR1A_4lrf0T4.ttf

raxkHiKDttkTe1aOGcJMR1A_4lrf0T4.ttf

59 ms

g.gif

g.gif

3 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

235 ms

Accessibility Review

truhealthy.com accessibility score

100

Accessibility Issues

Best Practices

truhealthy.com best practices score

92

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

SEO Factors

truhealthy.com SEO score

93

Search Engine Optimization Advices

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

truhealthy.com

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