Tools & Wizards About Us
whyuhc.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

whyuhc.com

Health insurance plans | UnitedHealthcare

Page Load Speed

1.7 sec in total

First Response

27 ms

Resources Loaded

1.6 sec

Page Rendered

55 ms

whyuhc.com screenshot

About Website

Welcome to whyuhc.com homepage info - get ready to check Whyuhc best content for United States right away, or after learning these important things about whyuhc.com

Explore health insurance options including Medicare, Medicaid, individual and family, short term and dental, as well as employer plans.

Visit whyuhc.com

Key Findings

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

Performance Metrics

whyuhc.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value9,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value42.6 s

0/100

10%

Network Requests Diagram

whyuhc.com

27 ms

www.whyuhc.com

51 ms

www.uhc.com

68 ms

clientlib-initial.min.cfe62ec3dc6ec950773a8406345ee49c.js

11 ms

clientlib-polyfills.min.d951ba151044a8195b3c1c387293b2dc.js

48 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Whyuhc.com, 67% (30 requests) were made to Uhc.com and 9% (4 requests) were made to Abyss-cloud.uhc.com. The less responsive or slowest element that took the longest time to load (214 ms) relates to the external source Instant.page.

Page Optimization Overview & Recommendations

Page size can be reduced by 511.3 kB (26%)

Content Size

2.0 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whyuhc.com main page is 2.0 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. 80% 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. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 75.0 kB

  • Original 92.1 kB
  • After minification 87.6 kB
  • After compression 17.0 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 75.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 800.2 kB
  • After minification 798.6 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. Whyuhc images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 433.3 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 613.6 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 433.3 kB or 41% of the original size.

CSS Optimization

-7%

Potential reduce by 1.4 kB

  • Original 20.6 kB
  • After minification 20.6 kB
  • After compression 19.2 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. Whyuhc.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (67%)

Requests Now

30

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whyuhc.com

whyuhc.com

27 ms

www.whyuhc.com

www.whyuhc.com

51 ms

www.uhc.com

www.uhc.com

68 ms

clientlib-initial.min.cfe62ec3dc6ec950773a8406345ee49c.js

clientlib-initial.min.cfe62ec3dc6ec950773a8406345ee49c.js

11 ms

clientlib-polyfills.min.d951ba151044a8195b3c1c387293b2dc.js

clientlib-polyfills.min.d951ba151044a8195b3c1c387293b2dc.js

48 ms

clientlib-initial.min.e30fbd79b4c95b39f491fc9fc9f9a516.css

clientlib-initial.min.e30fbd79b4c95b39f491fc9fc9f9a516.css

61 ms

clientlib-site.min.f41db6d9254f71ecf444883c5acafa07.css

clientlib-site.min.f41db6d9254f71ecf444883c5acafa07.css

69 ms

clientlib-livechat.min.143a6046d1e2182e6a51006e0afd6baf.css

clientlib-livechat.min.143a6046d1e2182e6a51006e0afd6baf.css

97 ms

clientlib-react-components.min.50b491ce0b129e0622b13de4213dc8da.css

clientlib-react-components.min.50b491ce0b129e0622b13de4213dc8da.css

98 ms

launch-5e90c3319557.min.js

launch-5e90c3319557.min.js

208 ms

header.css

header.css

66 ms

uhc-header-component.parcel.js

uhc-header-component.parcel.js

127 ms

footer.css

footer.css

125 ms

uhc-footer-component.parcel.js

uhc-footer-component.parcel.js

206 ms

clientlib-video.min.28b3ece926d7dfb102f99bc7045f031c.js

clientlib-video.min.28b3ece926d7dfb102f99bc7045f031c.js

145 ms

clientlib-site.min.31f7409253a44794ba9decbe7233c69f.js

clientlib-site.min.31f7409253a44794ba9decbe7233c69f.js

144 ms

5.1.0

5.1.0

214 ms

clientlib-react-components.min.ec2a5559bc64bc8c7eabe8bf023d713a.js

clientlib-react-components.min.ec2a5559bc64bc8c7eabe8bf023d713a.js

214 ms

clientlib-livechat.min.97c708380f6c61c536c9dfcf828a40f0.js

clientlib-livechat.min.97c708380f6c61c536c9dfcf828a40f0.js

203 ms

original

original

106 ms

apple-app-store-badge.svg

apple-app-store-badge.svg

70 ms

google-play-app-badge-135x40.png

google-play-app-badge-135x40.png

70 ms

cq5dam.web.1280.1280.jpeg

cq5dam.web.1280.1280.jpeg

103 ms

CTA_internal_digitalblue.svg

CTA_internal_digitalblue.svg

131 ms

caret_down_darkgrey.svg

caret_down_darkgrey.svg

129 ms

brightcove_neutral.svg

brightcove_neutral.svg

133 ms

caret_down_digitalblue.svg

caret_down_digitalblue.svg

131 ms

original

original

134 ms

UHCSans-Medium.woff

UHCSans-Medium.woff

194 ms

UHCSans-SemiBold.woff

UHCSans-SemiBold.woff

199 ms

UHCSans-Bold.woff

UHCSans-Bold.woff

212 ms

UHCSerif-SemiBold.woff

UHCSerif-SemiBold.woff

210 ms

UHCSerifHeadlineWeb-Bold.woff

UHCSerifHeadlineWeb-Bold.woff

92 ms

UHCSerifHeadlineWeb-Regular.woff

UHCSerifHeadlineWeb-Regular.woff

90 ms

UHCSerifHeadlineWeb-Light.woff

UHCSerifHeadlineWeb-Light.woff

90 ms

UHCSansDigital-Bold.woff

UHCSansDigital-Bold.woff

92 ms

UHCSansDigital-SemiBold.woff

UHCSansDigital-SemiBold.woff

90 ms

UHCSansDigital-Medium.woff

UHCSansDigital-Medium.woff

91 ms

id

id

147 ms

AppMeasurement.min.js

AppMeasurement.min.js

51 ms

dest5.html

dest5.html

41 ms

pixel

pixel

30 ms

pixel

pixel

17 ms

ibs:dpid=771&dpuuid=CAESECecS5-TuOrkWqZoEEMNjaA&google_cver=1

ibs:dpid=771&dpuuid=CAESECecS5-TuOrkWqZoEEMNjaA&google_cver=1

9 ms

ibs:dpid=411&dpuuid=Ze5oewAAAGhLjANw

ibs:dpid=411&dpuuid=Ze5oewAAAGhLjANw

10 ms

Accessibility Review

whyuhc.com accessibility score

93

Accessibility Issues

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

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

Image elements do not have [alt] attributes

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

whyuhc.com

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