Programmable

Website review, no card needed

intermountainnutrition.com logo

intermountainnutrition.com website review

Visit site (opens in a new tab)Reviewed 21 October 202620 issues · 78 checks

This review found 20 issues worth fixing on intermountainnutrition.com, 8 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

88B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.4 s1.5 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.6 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.3 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.1 s
Oct 10, 20262.3 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
125 ms81 msMay 30Oct 1787 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202698 ms
Jun 6, 202696 ms
Jun 13, 202686 ms
Jun 20, 202691 ms
Jun 27, 2026111 ms
Jul 4, 2026120 ms
Jul 11, 2026111 ms
Jul 18, 202691 ms
Jul 25, 202686 ms
Aug 1, 202689 ms
Aug 8, 202689 ms
Aug 15, 202694 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 2026100 ms
Sep 12, 2026102 ms
Sep 19, 2026103 ms
Sep 26, 2026105 ms
Oct 3, 202694 ms
Oct 10, 202694 ms
Oct 17, 202687 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

intermountainnutrition.com (opens in a new tab)
Full-page screenshot of intermountainnutrition.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. intermountainnutrition.com at 0.4 s0.4 s
  2. intermountainnutrition.com at 0.8 s0.8 s
  3. intermountainnutrition.com at 1.1 s1.1 s
  4. intermountainnutrition.com at 1.5 s1.5 s
  5. intermountainnutrition.com at 1.9 s1.9 s
  6. intermountainnutrition.com at 2.3 s2.3 s
  7. intermountainnutrition.com at 2.6 s2.6 s
  8. intermountainnutrition.com at 3.0 s3.0 s

Speed

1 to fix100

  • 1,615 HTML elements

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

  • Reduce unused CSS

    177 KiB

    About 177 KiB of CSS is downloaded but never applied on this page.

  • 2 long tasks on the main thread

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

  • Improve image delivery

    14 KiB

    1 image could be 14 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Chained critical requests

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

  • Forced reflow

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

3 checks passed

  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100 (desktop: 80). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 79 ms of it running JavaScript. That is comfortably low.

  • Server response: 14 ms

    14 ms

    Your server sent the HTML in 14 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix67

  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 22.5 s

    22.5 s

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

  • Real-user CLS: 0.18

    0.18

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

  • Largest content (LCP) got 31% slower for real visitors

    +31%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Tap response (INP) held steady for real visitors

    -7%

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

8 checks passed

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 88 ms

    88 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Largest Contentful Paint: 1.3 s

    1.3 s

    Your largest element renders in 1.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Intermountain Nutrition is a high-capacity, turnkey nutrace…”.

  • Speed Index: 1.2 s

    1.2 s

    Visually, the page fills in at 1.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 40 ms

    40 ms

    Scripts block the page for only 40 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70

  • Page weight: 5.6 MB in 45 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 45 requests on a phone: fonts 4.6 MB (5), other files 714 KiB (32) and stylesheets 199 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.59 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 8288

  • Certain ARIA roles must contain particular children (9 elements)

    Certain ARIA roles must contain particular children: 9 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must be contained by particular parents (2 elements)

    Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

  • 16 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed

  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100

  • 136 internal links, 5 external

    The homepage links to 136 pages on intermountainnutrition.com and 5 external pages.

8 checks passed

  • Meta description: 139 characters

    Your meta description is 139 characters: “Intermountain Nutrition is a high-capacity nutraceutical contract manufacturer for supplement brands. They're cGMP cert…”.

  • One H1 headline

    Your main headline reads: “A Leading Nutraceutical Contract Manufacturer”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Intermountain Nutrition - A Nutraceutical Manufacturer”.

  • Canonical URL set

    The canonical URL is https://intermountainnutrition.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://intermountainnutrition.com/sitemap_index.xml.

AI search readiness

100
4 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,685 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://intermountainnutrition.com/llms.txt (4 KiB, 21 links), a plain-text guide to the site for AI tools.

Other pages

100

  • 15 internal pages checked

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

7 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093

  • 5 small tap targets

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

2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88

  • Local business without LocalBusiness data

    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 8-field form

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

  • No opening hours

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

  • No risk reducer

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

  • About 2,522 words of copy

    The homepage carries about 2,522 words of visible text.

6 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “CONTACT”, “Contact” and “request a quote”.

  • Social proof on the page

    Social proof on the homepage: 26 testimonial or review blocks, 5 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 3 cookies set on arrival

    3

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

  • No consent tool detected

    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.

  • 3 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at intermountainnutrition.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on intermountainnutrition.com, including 6 speed issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25