Website review, no card needed
mihealths.com website review
Visit site (opens in a new tab)Reviewed 18 October 202627 issues · 71 checks
This review found 27 issues worth fixing on mihealths.com, 9 of them high impact, across 71 checks. The most urgent: improve image delivery. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.6 s |
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 71 ms |
| May 2, 2026 | 70 ms |
| May 9, 2026 | 70 ms |
| May 16, 2026 | 71 ms |
| May 23, 2026 | 71 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 72 ms |
| Jun 20, 2026 | 72 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 74 ms |
| Jul 11, 2026 | 72 ms |
| Jul 18, 2026 | 71 ms |
| Jul 25, 2026 | 73 ms |
| Aug 1, 2026 | 76 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 82 ms |
| Aug 22, 2026 | 79 ms |
| Aug 29, 2026 | 77 ms |
| Sep 5, 2026 | 74 ms |
| Sep 12, 2026 | 73 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 91 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 116 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
Improve image delivery
32.7 s · 8.1 MB3 images could be 8.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 32.7 s faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 58). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 92 KiBAbout 92 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 508 ms. During a long task the page ignores taps.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
Reduce unused CSS
20 KiBAbout 20 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
9 KiB2 files are served with short cache lifetimes, so returning visitors download them again (9 KiB).
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.
1 third-party service on the page
1 third-party service load with your homepage (supabase.co), adding 1 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 141 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 50.3 s
50.3 sYour largest element takes 50.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Michigan Health Specialists care team”.
Time to Interactive: 51.6 s
51.6 sThe page becomes fully interactive after 51.6 s. Good is under 3.8 s.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 56% slower for real visitors
+56%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 71 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 113 ms
113 msReal visitors wait 113 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.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
4 images over 500 KB
4 images weigh 11.9 MB together. On a phone connection a single image that size takes seconds.
Page weight: 12.3 MB in 22 requests
12.3 MBYour homepage downloads 12.3 MB in 22 requests on a phone: images 12.0 MB (7), scripts 220 KiB (8) and fonts 71 KiB (3). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
11.6 MB5 images are downloaded at several times the size a phone draws them, for example hero.jpg at 6,766 px wide, shown at 390 px. Resized copies would save about 11.6 MB.
5 images in older formats
5 images (12.0 MB) 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.
3 images below the first screen load straight away
3 images further down the page (5.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.49 g of CO₂e: 418.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to michigan-health-glow.lovable.app, not mihealths.com, so Google may credit that host instead.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (181 characters)
Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.
29 internal links, 14 external
The homepage links to 29 pages on mihealths.com and 14 external pages.
5 checks passed
One H1 headline
Your main headline reads: “No patient left behind.”.
Title: 63 characters
Your title is a healthy 63 characters: “Michigan Health Specialists — Family, Internal & Pediatric Care”.
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://michigan-health-glow.lovable.app/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://mihealths.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (759 words), so crawlers that don't run JavaScript still read it.
Other pages
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 14 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 14 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 14 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
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
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 712 words of copy
The homepage carries about 712 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a Visit” and “Schedule an Appointment”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Book a Visit” and “Schedule an Appointment”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 mihealths.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on mihealths.com, including 15 speed issues, 3 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.