vhdenver.com website review

7 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.

About 807 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

7 third-party services load with your homepage (YouTube, cleantalk.org and Other Google APIs/SDKs and others), adding 7.9 MB and 575 ms of main-thread time.

About 211 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

vibrahealthcare.com costs a phone 9 ms of main-thread work and 6.9 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

YouTube costs a phone 542 ms of main-thread work and 976 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.3 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 long tasks block the main thread while loading, the longest for 195 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The first text or image appears after 9.7 s on a phone. Good is under 1.8 s.

Your largest element takes 26.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Vibra Hospital of Denver”.

The page becomes fully interactive after 26.8 s. Good is under 3.8 s.

Visually, the page fills in at 13.3 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 229 ms in total while the page loads. Good is under 200 ms.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 11.8 MB in 72 requests on a phone: media 6.8 MB (4), images 3.2 MB (14) and scripts 1.3 MB (23). Under 2 MB keeps phones on slow connections fast.

3 images (200 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

2 images further down the page (77 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.34 g of CO₂e: 401.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 links inside paragraphs rely on colour alone to stand out.

All page content should be contained by landmarks: 45 elements on the page fail this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h5, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 24 characters: “Vibra Hospital of Denver”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“Getting you back to better,”, “Welcome to Vibra Hospital of Denver” and “Elevating Patient Care”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://vhdenver.com/sitemap_index.xml, so Google discovers your pages only by following links.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

2 links have no real href, so search engines can't follow them.

The homepage links to 86 pages on vhdenver.com and 14 external pages.

There is no https://vhdenver.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://vhdenver.com/about-us, https://vhdenver.com/about-us/certifications-accreditations, https://vhdenver.com/about-us/corporate-compliance, https://vhdenver.com/about-us/mission-values, https://vhdenver.com/about-us/news-announcements and https://vhdenver.com/about-us/nondiscrimination-policy and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 672 words of visible text.

Before a visitor clicks anything, the page loads Google Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.