nextcare.com website review

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

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

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

Your mobile performance score is 57 (desktop: 83). Pages that score under 90 lose visitors before the first paint.

About 169 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

5 third-party services load with your homepage (Cookiebot, webtrends-optimize.com and Salesforce.com and others), adding 612 KiB and 533 ms of main-thread time.

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

The page has 2,356 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

Desktop scores 83 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

7 KiB could be saved by minifying CSS.

7 KiB could be saved by minifying JavaScript.

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.

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.

For real visitors the layout shifts by 0.53 (75th percentile). Good is under 0.1.

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

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

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

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

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

Scripts block taps and scrolling for 206 ms in total while the page loads. Good is under 200 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-17, real Chrome visitors' tap response (inp) went from 104 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.6 MB in 135 requests on a phone: images 1.4 MB (20), scripts 875 KiB (75) and stylesheets 188 KiB (26). Under 2 MB keeps phones on slow connections fast.

1 image (311 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

Some list items are not inside a list.

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Structured data found (ImageObject, MedicalBusiness, MedicalWebPage and Organization) but with 1 problem, for example “ImageObject: url is not an absolute URL ("https://nextcare.com/wp-content/uploads/2025/11/heart-tag.svg")”.

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

The homepage links to 120 pages on nextcare.com and 9 external pages.

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

1 image failed to load on a phone, for example https://nextcare.com/.

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

1 image is served at too low a resolution for sharp phone screens.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your longest form asks for 159 fields (5 required). Every extra field lowers completion.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Opening the homepage sets 7 cookies (measured from a US location before any click).

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