Tools & Wizards About Us
wholeyou.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

wholeyou.com

Respire Products - DynaFlex

Page Load Speed

22.4 sec in total

First Response

189 ms

Resources Loaded

21.9 sec

Page Rendered

362 ms

wholeyou.com screenshot

About Website

Click here to check amazing Wholeyou content for United States. Otherwise, check out these important facts you probably never knew about wholeyou.com

Visit wholeyou.com

Key Findings

We analyzed Wholeyou.com page load time and found that the first response time was 189 ms and then it took 22.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

wholeyou.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.157

74/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

wholeyou.com

189 ms

wholeyou.com

253 ms

1433 ms

prettyPhoto.css

126 ms

wp-video-lightbox.css

187 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wholeyou.com, 60% (50 requests) were made to Dynaflex.com and 25% (21 requests) were made to Assets.dynaflex.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Dev.dynaflex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 394.6 kB (25%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 224.7 kB

  • Original 262.9 kB
  • After minification 258.8 kB
  • After compression 38.2 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 224.7 kB or 85% of the original size.

Image Optimization

-17%

Potential reduce by 161.9 kB

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

JavaScript Optimization

-2%

Potential reduce by 4.3 kB

  • Original 244.4 kB
  • After minification 244.4 kB
  • After compression 240.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

-4%

Potential reduce by 3.7 kB

  • Original 97.5 kB
  • After minification 97.5 kB
  • After compression 93.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. Wholeyou.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (61%)

Requests Now

67

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wholeyou.com

wholeyou.com

189 ms

wholeyou.com

wholeyou.com

253 ms

1433 ms

prettyPhoto.css

prettyPhoto.css

126 ms

wp-video-lightbox.css

wp-video-lightbox.css

187 ms

all.min.css

all.min.css

195 ms

bootstrap.min.css

bootstrap.min.css

190 ms

front.css

front.css

199 ms

font-awesome.min.css

font-awesome.min.css

27 ms

css

css

32 ms

ubermenu.min.css

ubermenu.min.css

140 ms

cleanwhite.css

cleanwhite.css

138 ms

font-awesome.min.css

font-awesome.min.css

185 ms

ytprefs.min.css

ytprefs.min.css

192 ms

lity.min.css

lity.min.css

196 ms

style.css

style.css

194 ms

jquery.min.js

jquery.min.js

263 ms

jquery-migrate.min.js

jquery-migrate.min.js

203 ms

nfpluginsettings.js

nfpluginsettings.js

246 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

254 ms

video-lightbox.js

video-lightbox.js

257 ms

popper.min.js

popper.min.js

258 ms

bootstrap.min.js

bootstrap.min.js

281 ms

front.js

front.js

308 ms

divi-child.js

divi-child.js

317 ms

lity.min.js

lity.min.js

320 ms

ytprefs.min.js

ytprefs.min.js

322 ms

et-divi-customizer-global.min.css

et-divi-customizer-global.min.css

338 ms

ninjatables-public.css

ninjatables-public.css

364 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

442 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

443 ms

wp-polyfill.min.js

wp-polyfill.min.js

442 ms

hooks.min.js

hooks.min.js

441 ms

i18n.min.js

i18n.min.js

441 ms

jquery.form.min.js

jquery.form.min.js

441 ms

scripts.min.js

scripts.min.js

580 ms

jquery.fitvids.js

jquery.fitvids.js

524 ms

common.js

common.js

527 ms

ubermenu.min.js

ubermenu.min.js

524 ms

fitvids.min.js

fitvids.min.js

524 ms

footable.min.js

footable.min.js

525 ms

ninja-tables-footable.js

ninja-tables-footable.js

523 ms

gtm.js

gtm.js

176 ms

Norris-Menu4.png

Norris-Menu4.png

139 ms

Respire-Solid-Checkmark-150px.png

Respire-Solid-Checkmark-150px.png

19688 ms

DynaFlex_Header.png

DynaFlex_Header.png

245 ms

footerlogos4.png

footerlogos4.png

246 ms

Respire-WhiteCircle-Checkmark-150px.png

Respire-WhiteCircle-Checkmark-150px.png

19687 ms

Respire-Checkmark-150px.png

Respire-Checkmark-150px.png

19687 ms

DynaFusion-Logo-Small3.png

DynaFusion-Logo-Small3.png

147 ms

SmileShare-Logo-Nav.png

SmileShare-Logo-Nav.png

151 ms

Rhinogram-Primary-Logo-1024x671-1.png

Rhinogram-Primary-Logo-1024x671-1.png

153 ms

DynaFusion_Tutorial_Page_Logo.png

DynaFusion_Tutorial_Page_Logo.png

166 ms

prd-RespirePink-1.png

prd-RespirePink-1.png

193 ms

prd-RespirePinkEF-1.png

prd-RespirePinkEF-1.png

170 ms

prd-RespirePinkATMicro.png

prd-RespirePinkATMicro.png

166 ms

prd-RespirePinkEFATMicro.png

prd-RespirePinkEFATMicro.png

167 ms

prd-RespireBlue-1.png

prd-RespireBlue-1.png

169 ms

prd-RespireBlueEF-1.png

prd-RespireBlueEF-1.png

170 ms

prd-RespireSplint.png

prd-RespireSplint.png

192 ms

Respire-Solid-Checkmark-150px.png

Respire-Solid-Checkmark-150px.png

535 ms

Respire-WhiteCircle-Checkmark-150px.png

Respire-WhiteCircle-Checkmark-150px.png

190 ms

Respire-Checkmark-150px.png

Respire-Checkmark-150px.png

536 ms

prd-RespireBlue150.png

prd-RespireBlue150.png

625 ms

prd-RespirePink150.png

prd-RespirePink150.png

192 ms

prd-RespirePinkMicroAT150.png

prd-RespirePinkMicroAT150.png

193 ms

prd-RespireBlueEF150.png

prd-RespireBlueEF150.png

624 ms

prd-RespirePinkEF150.png

prd-RespirePinkEF150.png

537 ms

prd-RespirePinkATEFMicro150.png

prd-RespirePinkATEFMicro150.png

196 ms

Background1-Light2.png

Background1-Light2.png

332 ms

font

font

47 ms

modules.woff

modules.woff

221 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

430 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

24 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

203 ms

fa-regular-400.ttf

fa-regular-400.ttf

265 ms

fa-brands-400.ttf

fa-brands-400.ttf

430 ms

fa-solid-900.ttf

fa-solid-900.ttf

521 ms

loader.js

loader.js

166 ms

et-divi-dynamic-46794-late.css

et-divi-dynamic-46794-late.css

272 ms

font

font

31 ms

style.min.css

style.min.css

70 ms

getC9WPInfo

getC9WPInfo

343 ms

Accessibility Review

wholeyou.com accessibility score

87

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

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

wholeyou.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

wholeyou.com SEO score

79

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

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

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

wholeyou.com

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