Tools & Wizards About Us
whathealth.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

whathealth.com

What Health - Healthy Living For Every Body

Page Load Speed

2.5 sec in total

First Response

226 ms

Resources Loaded

1.2 sec

Page Rendered

1 sec

whathealth.com screenshot

About Website

Visit whathealth.com now to see the best up-to-date What Health content for India and also check out these interesting facts you probably never knew about whathealth.com

What Health promotes healthy living. Health tools are featured including body mass index charts calculators.

Visit whathealth.com

Key Findings

We analyzed Whathealth.com page load time and found that the first response time was 226 ms and then it took 2.2 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

whathealth.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value3,280 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.334

34/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

whathealth.com

226 ms

www.whathealth.com

207 ms

cookieconsent.latest.min.js

75 ms

counter.js

99 ms

adsbygoogle.js

4 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 43% of them (6 requests) were addressed to the original Whathealth.com, 14% (2 requests) were made to Google-analytics.com and 7% (1 request) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (354 ms) relates to the external source Apis.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.4 kB (29%)

Content Size

217.7 kB

After Optimization

155.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Whathealth.com main page is 217.7 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. 25% of websites need less resources to load. Javascripts take 131.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.8 kB

  • Original 37.5 kB
  • After minification 36.7 kB
  • After compression 8.7 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 28.8 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 2 B

  • Original 49.1 kB
  • After minification 49.1 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. What Health images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 33.5 kB

  • Original 131.0 kB
  • After minification 131.0 kB
  • After compression 97.5 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 33.5 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (50%)

Requests Now

10

After Optimization

5

  • Images
  • JavaScript

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

Network Requests Diagram

whathealth.com

whathealth.com

226 ms

www.whathealth.com

www.whathealth.com

207 ms

cookieconsent.latest.min.js

cookieconsent.latest.min.js

75 ms

counter.js

counter.js

99 ms

adsbygoogle.js

adsbygoogle.js

4 ms

bkg_body.png

bkg_body.png

124 ms

analytics.js

analytics.js

122 ms

logo3.png

logo3.png

279 ms

healthwoman.jpg

healthwoman.jpg

261 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

258 ms

t.php

t.php

244 ms

plusone.js

plusone.js

354 ms

sdk.js

sdk.js

321 ms

linkid.js

linkid.js

242 ms

Accessibility Review

whathealth.com accessibility score

85

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

Best Practices

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

High

Browser errors were logged to the console

SEO Factors

whathealth.com SEO score

97

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

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

whathealth.com

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