northcare.com website review

70 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).

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

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

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

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

6 images could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

55 KiB could be saved by minifying CSS.

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

35 KiB could be saved by minifying JavaScript.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 272 KiB and 122 ms of main-thread time.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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.

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

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

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

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

The layout shifts by 0.462 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 103 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.0 MB in 104 requests on a phone: scripts 1.5 MB (41), stylesheets 1.2 MB (24) and images 933 KiB (26). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Central-Oklahoma-and-Canadian-County-logo_localization_UWfir at 1,965 px wide, shown at 171 px. Resized copies would save about 74 KiB.

1 image (79 KiB) is 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.

1 image further down the page (79 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

13 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings should not be empty: 7 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 9 characters: “NorthCare”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 21 characters: “| Live Without Limits”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 111 pages on northcare.com and 17 external pages.

There is no https://www.northcare.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://www.northcare.com/index.php/our-locations, https://www.northcare.com/index.php/our-story, https://www.northcare.com/index.php/contact-form, https://www.northcare.com/index.php/northcare-medical-records, https://www.northcare.com/index.php/leadership and https://www.northcare.com/index.php/adult-services and 5 others use the same meta description. A description written for each page earns more clicks.

https://www.northcare.com/index.php/why-work-at-northcare has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.northcare.com/index.php/our-locations, https://www.northcare.com/index.php/our-story, https://www.northcare.com/index.php/contact-form, https://www.northcare.com/index.php/northcare-medical-records, https://www.northcare.com/index.php/leadership and https://www.northcare.com/index.php/adult-services and 5 others took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Unexpected token '<'”.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics 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 2 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.