usenourish.com website review

Google Tag Manager costs a phone 1.0 s of main-thread work and 682 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and website-files.com and others), adding 20.0 MB and 2.1 s of main-thread time.

website-files.com costs a phone 165 ms of main-thread work and 18.6 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.

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 600 ms.

JSDelivr CDN costs a phone 447 ms of main-thread work and 244 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.

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

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

16 KiB could be saved by minifying JavaScript.

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

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

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.

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.

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

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

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

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

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

1 image 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 140 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 20.3 MB in 140 requests on a phone: media 17.6 MB (2), scripts 1.5 MB (57) and images 695 KiB (34). Under 2 MB keeps phones on slow connections fast.

2 images (99 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.

By the Sustainable Web Design model, a visit to your homepage emits about 5.74 g of CO₂e: 689.1 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: 2 elements on the page fail this check, rated critical by axe-core.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

Your meta description is 242 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 117 pages on usenourish.com and 26 external pages.

https://www.nourish.com/employers and https://www.nourish.com/health-systems have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nourish.com/refer and https://www.nourish.com/for-health-plans use the same meta description. A description written for each page earns more clicks.

https://www.nourish.com/does-my-insurance-cover-nutrition has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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 53 fields (0 required). Every extra field lowers completion.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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