pvmc.org website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.

The page goes through 1 redirect before it starts loading, costing about 8.7 s. Link and advertise the final URL directly.

About 112 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (airbud.io, Google Tag Manager and roundprincethere.com and others), adding 1.5 MB and 1.2 s of main-thread time.

airbud.io costs a phone 409 ms of main-thread work and 806 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.

28 files are served with short cache lifetimes, so returning visitors download them again (350 KiB).

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

Google Tag Manager costs a phone 274 ms of main-thread work and 168 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.

6 images could be 254 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 KiB could be saved by minifying JavaScript.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Real visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

1 image have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 5.9 MB in 148 requests on a phone: scripts 3.4 MB (57), images 1.3 MB (33) and fonts 442 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Your title is only 27 characters: “Home - Intermountain Health”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

Your hreflang tags are invalid, so Google may show the wrong language version.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 59 pages on pvmc.org and 29 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.intermountainhealth.org/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.intermountainhealth.org/undefined declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.intermountainhealth.org/undefined all use the title “Home - Intermountain Health”. Search engines can't tell which page to show for a search, so each competes with the others.

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

Requests the geolocation permission on page load.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 673 words of visible text.

Before a visitor clicks anything, the page loads Amplitude and Google Tag Manager (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 8 cookies (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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.