Website review, no card needed
nhi.edu website review
Visit site (opens in a new tab)Reviewed 29 October 202628 issues · 72 checks
This review found 28 issues worth fixing on nhi.edu, 9 of them high impact, across 72 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 217 ms |
| May 16, 2026 | 214 ms |
| May 23, 2026 | 211 ms |
| May 30, 2026 | 213 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 216 ms |
| Jun 20, 2026 | 216 ms |
| Jun 27, 2026 | 217 ms |
| Jul 4, 2026 | 219 ms |
| Jul 11, 2026 | 223 ms |
| Jul 18, 2026 | 227 ms |
| Jul 25, 2026 | 228 ms |
| Aug 1, 2026 | 230 ms |
| Aug 8, 2026 | 240 ms |
| Aug 15, 2026 | 262 ms |
| Aug 22, 2026 | 272 ms |
| Aug 29, 2026 | 279 ms |
| Sep 5, 2026 | 277 ms |
| Sep 12, 2026 | 271 ms |
| Sep 19, 2026 | 281 ms |
| Sep 26, 2026 | 289 ms |
| Oct 3, 2026 | 297 ms |
| Oct 10, 2026 | 306 ms |
| Oct 17, 2026 | 312 ms |
| Oct 24, 2026 | 318 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
Speed
Render-blocking requests
1.9 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.8 s
A phone's processor spends 6.8 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 3.1 MB and 2.5 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
989 KiB24 files are served with short cache lifetimes, so returning visitors download them again (989 KiB).
YouTube adds 774 ms
774 msYouTube costs a phone 774 ms of main-thread work and 980 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.
Reduce unused CSS
450 ms · 181 KiBAbout 181 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.
Google Tag Manager adds 444 ms
444 msGoogle Tag Manager costs a phone 444 ms of main-thread work and 353 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.
Facebook adds 419 ms
419 msFacebook costs a phone 419 ms of main-thread work and 447 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.
Google CDN adds 335 ms
335 msGoogle CDN costs a phone 335 ms of main-thread work and 805 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 on the main thread
20 long tasks block the main thread while loading, the longest for 270 ms. During a long task the page ignores taps.
1,743 HTML elements
The page has 1,743 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
46 KiB2 images could be 46 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 34.4 s
34.4 sThe page becomes fully interactive after 34.4 s. Good is under 3.8 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 217 ms to 318 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 729 ms
729 msReal visitors wait 729 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.031
0.031The layout barely moves while loading (CLS 0.031, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 145 requests
6.7 MBYour homepage downloads 6.7 MB in 145 requests on a phone: scripts 5.1 MB (64), other files 711 KiB (25) and fonts 299 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 1.9 g of CO₂ per visit
1.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 226.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Links do not have a discernible name
Links do not have a discernible name (6 elements).
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
SEO
Title is long (84 characters)
Your title is 84 characters, so Google will cut it off around 60: “California Massage School – National Holistic Institute | College of Massage Therapy”.
Meta description is long (226 characters)
Your meta description is 226 characters; Google truncates after about 160, so the end of your pitch is cut.
202 internal links, 11 external
The homepage links to 202 pages on nhi.edu and 11 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Turn Massage School into a Career You Love”.
Canonical URL set
The canonical URL is https://nhi.edu/.
Structured data in place
Structured data found: BreadcrumbList, 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://nhi.edu/sitemap.xml.
AI search readiness
3 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://nhi.edu/llms.txt (195 KiB, 591 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share a meta description
https://nhi.edu/how-to-become-a-massage-therapist and https://nhi.edu/how-to-become-a-massage-therapist/start-here use the same meta description. A description written for each page earns more clicks.
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
7 third-party cookies
7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 1,300 words of copy
The homepage carries about 1,300 words of visible text.
3 checks passed
20 calls to action
The homepage has 20 calls to action, for example “Start Here”, “How to Apply for Financial Aid” and “Course Schedule”.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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 nhi.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Employees
- 457
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on nhi.edu, including 20 speed issues, 2 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.