Tools & Wizards About Us
vitals.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vitals.com

Find a Doctor, Doctor Reviews & Ratings | Vitals.com

Page Load Speed

75.5 sec in total

First Response

240 ms

Resources Loaded

52.8 sec

Page Rendered

22.5 sec

vitals.com screenshot

About Website

Visit vitals.com now to see the best up-to-date Vitals content for United States and also check out these interesting facts you probably never knew about vitals.com

Find great doctors at Vitals. Read ratings and reviews from other patients, get insurance information, hours and locations, and book an appointment online.

Visit vitals.com

Key Findings

We analyzed Vitals.com page load time and found that the first response time was 240 ms and then it took 75.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

vitals.com performance score

0

Network Requests Diagram

vitals.com

240 ms

www.vitals.com

334 ms

analytics.js

2712 ms

gtm.js

737 ms

app_1.min.css

801 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 17% of them (14 requests) were addressed to the original Vitals.com, 24% (20 requests) were made to Mdxvitals-res.cloudinary.com and 8% (7 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (10.7 sec) relates to the external source Bam.nr-data.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.6 MB (60%)

Content Size

5.9 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vitals.com main page is 5.9 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. 85% 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 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 68.7 kB

  • Original 90.6 kB
  • After minification 76.3 kB
  • After compression 21.8 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. This page needs HTML code to be minified as it can gain 14.3 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 68.7 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 54.6 kB

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

JavaScript Optimization

-69%

Potential reduce by 1.9 MB

  • Original 2.7 MB
  • After minification 2.7 MB
  • After compression 855.4 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 1.9 MB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 1.6 MB

  • Original 1.9 MB
  • After minification 1.8 MB
  • After compression 272.1 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. Vitals.com needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 85% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vitals. 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vitals.com

vitals.com

240 ms

www.vitals.com

www.vitals.com

334 ms

analytics.js

analytics.js

2712 ms

gtm.js

gtm.js

737 ms

app_1.min.css

app_1.min.css

801 ms

base.css

base.css

709 ms

header.css

header.css

1385 ms

search.css

search.css

709 ms

footer.css

footer.css

706 ms

style.css

style.css

706 ms

materialize.min.css

materialize.min.css

3588 ms

home.min.5de6f867.css

home.min.5de6f867.css

2627 ms

vtlsdstl.js

vtlsdstl.js

2347 ms

forms2.min.js

forms2.min.js

2582 ms

jquery@2.2.0,algoliasearch,autocomplete.js,algoliasearch.helper

jquery@2.2.0,algoliasearch,autocomplete.js,algoliasearch.helper

2580 ms

features.js

features.js

2396 ms

global.min.3603d89c.js

global.min.3603d89c.js

2579 ms

materialize.min.js

materialize.min.js

4998 ms

homepageFunctions.min.7f77e234.js

homepageFunctions.min.7f77e234.js

2578 ms

analytics.js

analytics.js

1274 ms

linkid.js

linkid.js

227 ms

js

js

1727 ms

gpt.js

gpt.js

1229 ms

vitals-purple-logo_2x.png

vitals-purple-logo_2x.png

763 ms

homepageHero.gif

homepageHero.gif

538 ms

mobile-hero.png

mobile-hero.png

614 ms

officeVitals.jpg

officeVitals.jpg

823 ms

vitalsChoice.jpg

vitalsChoice.jpg

614 ms

personalized-search.png

personalized-search.png

614 ms

bipolar_disorder.jpg

bipolar_disorder.jpg

570 ms

type2diabetes.jpg

type2diabetes.jpg

569 ms

Migraine.jpg

Migraine.jpg

774 ms

ratings-reviews.png

ratings-reviews.png

570 ms

logo-forbes.png

logo-forbes.png

569 ms

logo-washingtonpost.png

logo-washingtonpost.png

570 ms

logo-theeconomist.png

logo-theeconomist.png

772 ms

logo-newyorktimes.png

logo-newyorktimes.png

586 ms

NPR-Logo-Final.png

NPR-Logo-Final.png

759 ms

logo-fortune.png

logo-fortune.png

759 ms

logo-ap.png

logo-ap.png

757 ms

logo-bloomberg.png

logo-bloomberg.png

757 ms

Nightly-News-online-copy.png

Nightly-News-online-copy.png

758 ms

Usa-Today_Web.png

Usa-Today_Web.png

568 ms

d4EyseQelEw

d4EyseQelEw

3448 ms

iframe_api

iframe_api

1571 ms

www-player-vflMqr8uC.css

www-player-vflMqr8uC.css

543 ms

www-embed-player.js

www-embed-player.js

2699 ms

base.js

base.js

2751 ms

pubads_impl_147.js

pubads_impl_147.js

2776 ms

www-widgetapi.js

www-widgetapi.js

2218 ms

getForm

getForm

1335 ms

collect

collect

57 ms

collect

collect

3621 ms

Roboto-Regular.woff

Roboto-Regular.woff

259 ms

Roboto-Regular.woff

Roboto-Regular.woff

257 ms

Roboto-Medium.woff

Roboto-Medium.woff

2765 ms

Roboto-Medium.woff

Roboto-Medium.woff

257 ms

Roboto-Light.woff

Roboto-Light.woff

2733 ms

Roboto-Light.woff

Roboto-Light.woff

2732 ms

Roboto-Thin.woff

Roboto-Thin.woff

2734 ms

Roboto-Bold.woff

Roboto-Bold.woff

3674 ms

Roboto-Bold.woff

Roboto-Bold.woff

2700 ms

MDX-Icons.ttf

MDX-Icons.ttf

2675 ms

forms2.css

forms2.css

1509 ms

forms2-theme-simple.css

forms2-theme-simple.css

1643 ms

id

id

2282 ms

2tj_Yt5eAEN1YazL-za5nq2m-sVEuK50_GPDTIKqlPM.js

2tj_Yt5eAEN1YazL-za5nq2m-sVEuK50_GPDTIKqlPM.js

9333 ms

ad_status.js

ad_status.js

9111 ms

container.html

container.html

1931 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

1074 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

5819 ms

logo_ringo-vflOpz8ZI.png

logo_ringo-vflOpz8ZI.png

5527 ms

collect

collect

2723 ms

collect

collect

253 ms

nr-1044.min.js

nr-1044.min.js

2802 ms

d4EyseQelEw

d4EyseQelEw

1606 ms

XDFrame

XDFrame

5232 ms

collect

collect

291 ms

fbevents.js

fbevents.js

6538 ms

435186637e

435186637e

10703 ms

id

id

2394 ms

T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js

T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js

1917 ms

forms2.min.js

forms2.min.js

1478 ms

SEO Factors

vitals.com SEO score

0

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

vitals.com

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