Tools & Wizards About Us
medwhat.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

medwhat.com

MedWhat | Your virtual medical assistant

Page Load Speed

1.5 sec in total

First Response

170 ms

Resources Loaded

1.1 sec

Page Rendered

200 ms

medwhat.com screenshot

About Website

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

MedWhat is an intelligent personal medical and health assistant that can automatically provide a contextual answer to questions posed in natural language.

Visit medwhat.com

Key Findings

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

Performance Metrics

medwhat.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

medwhat.com

170 ms

medwhat.css

66 ms

jquery.min.js

27 ms

jquery.js

190 ms

jquery-migrate.min.js

126 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 78% of them (63 requests) were addressed to the original Medwhat.com, 7% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (579 ms) belongs to the original domain Medwhat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 286.3 kB (18%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Medwhat.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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 37.8 kB

  • Original 47.6 kB
  • After minification 44.3 kB
  • After compression 9.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 37.8 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 121.8 kB

  • Original 1.2 MB
  • After minification 1.1 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. Med What images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 87.8 kB

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

CSS Optimization

-50%

Potential reduce by 38.9 kB

  • Original 78.5 kB
  • After minification 78.5 kB
  • After compression 39.6 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. Medwhat.com needs all CSS files to be minified and compressed as it can save up to 38.9 kB or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (72%)

Requests Now

71

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

medwhat.com

medwhat.com

170 ms

medwhat.css

medwhat.css

66 ms

jquery.min.js

jquery.min.js

27 ms

jquery.js

jquery.js

190 ms

jquery-migrate.min.js

jquery-migrate.min.js

126 ms

md5.js

md5.js

128 ms

mw_question_engine.js

mw_question_engine.js

126 ms

mw_profile_engine.js

mw_profile_engine.js

124 ms

mw_graph_engine.js

mw_graph_engine.js

128 ms

mw_dialogue_engine.js

mw_dialogue_engine.js

201 ms

mw_accounts_engine.js

mw_accounts_engine.js

202 ms

mw_storage.js

mw_storage.js

187 ms

mw_scroller.js

mw_scroller.js

188 ms

style.css

style.css

267 ms

media-queries.css

media-queries.css

251 ms

animate.min.css

animate.min.css

275 ms

hover.min.css

hover.min.css

260 ms

css

css

44 ms

css

css

72 ms

css

css

72 ms

font-awesome.css

font-awesome.css

256 ms

lightbox.css

lightbox.css

255 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

326 ms

wp-mediaelement.css

wp-mediaelement.css

325 ms

comment-reply.min.js

comment-reply.min.js

325 ms

navigation.js

navigation.js

328 ms

waypoints.min.js

waypoints.min.js

352 ms

jquery.scrollto.js

jquery.scrollto.js

353 ms

preload.custom.js

preload.custom.js

406 ms

slick.min.js

slick.min.js

408 ms

slick.min.custom.js

slick.min.custom.js

404 ms

yui.js

yui.js

410 ms

yui-custom.js

yui-custom.js

425 ms

text-scroll.js

text-scroll.js

417 ms

backstretch.js

backstretch.js

447 ms

backstretch-header.js

backstretch-header.js

447 ms

backstretch-footer.js

backstretch-footer.js

453 ms

mediaCheck.js

mediaCheck.js

449 ms

fitvids.js

fitvids.js

529 ms

flexslider-min.js

flexslider-min.js

530 ms

owl-gallery.js

owl-gallery.js

531 ms

owl-gallery-custom.js

owl-gallery-custom.js

465 ms

wow.js

wow.js

416 ms

wow-custom.js

wow-custom.js

415 ms

lightbox.js

lightbox.js

429 ms

lightbox-custom.js

lightbox-custom.js

432 ms

main.js

main.js

453 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

458 ms

wp-mediaelement.js

wp-mediaelement.js

394 ms

ssl_seal_1.png

ssl_seal_1.png

75 ms

logo.png

logo.png

306 ms

header_app1.png

header_app1.png

579 ms

iphone_01.png

iphone_01.png

510 ms

iphone_02.png

iphone_02.png

533 ms

iphone_03.png

iphone_03.png

485 ms

iphone_04.png

iphone_04.png

538 ms

logo_wjs-300x161.png

logo_wjs-300x161.png

429 ms

logo_techcrunch-300x130.png

logo_techcrunch-300x130.png

491 ms

analytics.js

analytics.js

49 ms

logo_siliconvalley.png

logo_siliconvalley.png

547 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQUwaEQXjM.woff

57 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQUwaEQXjM.woff

85 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff

88 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrcVIT9d4cw.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrcVIT9d4cw.woff

86 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d4cw.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d4cw.woff

87 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

569 ms

sdk.js

sdk.js

40 ms

logo_medcity.png

logo_medcity.png

523 ms

logo_cbs.png

logo_cbs.png

547 ms

collect

collect

60 ms

logo_pandodaily-300x80.png

logo_pandodaily-300x80.png

529 ms

ssl_seal_1.png

ssl_seal_1.png

32 ms

logo_standford.png

logo_standford.png

537 ms

logo_vb.png

logo_vb.png

559 ms

sdk.js

sdk.js

17 ms

footappicon.png

footappicon.png

514 ms

header_bg.png

header_bg.png

538 ms

js

js

65 ms

combo

combo

31 ms

none

none

266 ms

Accessibility Review

medwhat.com accessibility score

73

Accessibility Issues

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.

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

Links do not have a discernible name

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

medwhat.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

medwhat.com SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a valid hreflang

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

medwhat.com

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