Website review, no card needed

mimithealth.com logo

mimithealth.com website review

Visit site (opens in a new tab)Reviewed 21 October 202641 issues · 89 checks

This review found 41 issues worth fixing on mimithealth.com, 19 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
3.4 s2.4 sMay 2Oct 173.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.0 s
May 9, 20263.1 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.0 s
Aug 1, 20262.8 s
Aug 8, 20262.5 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20263.3 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
101 ms84 msMay 2Oct 1799 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202686 ms
May 9, 202686 ms
May 16, 202689 ms
May 23, 202691 ms
May 30, 202692 ms
Jun 6, 202694 ms
Jun 13, 202692 ms
Jun 20, 202693 ms
Jun 27, 202695 ms
Jul 4, 202693 ms
Jul 11, 202692 ms
Jul 18, 202691 ms
Jul 25, 202695 ms
Aug 1, 202693 ms
Aug 8, 202694 ms
Aug 15, 202694 ms
Aug 22, 202689 ms
Aug 29, 202690 ms
Sep 5, 202695 ms
Sep 12, 202697 ms
Sep 19, 202697 ms
Sep 26, 202699 ms
Oct 3, 202698 ms
Oct 10, 202697 ms
Oct 17, 202699 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

Full-page screenshot of mimithealth.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mimithealth.com at 0.9 s0.9 s
  2. mimithealth.com at 1.8 s1.8 s
  3. mimithealth.com at 2.7 s2.7 s
  4. mimithealth.com at 3.5 s3.5 s
  5. mimithealth.com at 4.4 s4.4 s
  6. mimithealth.com at 5.3 s5.3 s
  7. mimithealth.com at 6.2 s6.2 s
  8. mimithealth.com at 7.1 s7.1 s

Speed

17 to fix27
  • Reduce unused JavaScript

    3.5 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

  • Render-blocking requests

    3.5 s

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

  • Use efficient cache lifetimes

    1.1 s · 595 KiB

    32 files are served with short cache lifetimes, so returning visitors download them again (595 KiB).

  • audioeye.com adds 1.5 s

    1.5 s

    audioeye.com costs a phone 1.5 s of main-thread work and 297 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.

  • Reduce unused CSS

    1.1 s · 238 KiB

    About 238 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Squarespace adds 1.1 s

    1.1 s

    Squarespace costs a phone 1.1 s of main-thread work and 1.2 MB 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.

  • Main-thread work: 10.5 s

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

  • Mobile performance score: 27

    27/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, Squarespace and YouTube and others), adding 4.0 MB and 4.5 s of main-thread time.

  • Minify JavaScript

    760 ms · 56 KiB

    56 KiB could be saved by minifying JavaScript.

  • YouTube adds 668 ms

    668 ms

    YouTube costs a phone 668 ms of main-thread work and 963 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 Tag Manager adds 521 ms

    521 ms

    Google Tag Manager costs a phone 521 ms of main-thread work and 727 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.

  • Legacy JavaScript

    400 ms · 171 KiB

    Polyfills for old browsers add 171 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • Improve image delivery

    150 ms · 388 KiB

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

  • 20 long tasks on the main thread

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

  • 2,028 HTML elements

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

  • sqspcdn.com adds 133 ms

    133 ms

    sqspcdn.com costs a phone 133 ms of main-thread work and 404 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.

  • 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: 71 ms

    71 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 16.6 s

    16.6 s

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

  • Speed Index: 18.3 s

    18.3 s

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

  • Time to Interactive: 37.0 s

    37.0 s

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

  • First Contentful Paint: 7.4 s

    7.4 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 14% slower for real visitors

    +14%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

3 checks passed
  • Real-user INP: 98 ms

    98 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix70
  • Page weight: 6.3 MB in 198 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 198 requests on a phone: scripts 4.4 MB (114), images 965 KiB (22) and stylesheets 357 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

    2 images further down the page (163 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.78 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8491
  • 21 tap targets too small

    21 tap targets are too small or too close together to hit reliably with a finger.

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

3 to fixGoogle 8589
  • 5 H1 headlines

    There are 5 <h1> headlines (“Protect Your Health This SeasonGet Your Flu Vacci…”, “Transform Your Health Today with MIMIT Health's P…” and “Where Every Patient's Journey is a Priority”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5e98b54d0f918a5bacc…”.

  • 4 links with vague text

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

  • 199 internal links, 43 external

    The homepage links to 199 pages on mimithealth.com and 43 external pages.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Minimally invasive treatment for fibroids, hemorrhoids, PAD, varicose veins, enlarged prostate and more. Interventional…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “MIMIT Health | Vascular & Interventional Care, Chicago”.

  • Canonical URL set

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

  • 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://mimithealth.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://mimithealth.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 (1,117 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 3 pages without a meta description

    https://mimithealth.com/conditions/erectile-dysfunction, https://mimithealth.com/conditions/hemorrhoids and https://mimithealth.com/conditions/male-pattern-baldness have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 7385
  • 7 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Evergage is not defined”.

  • 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

1 to fix94
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. 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 map or directions link

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

  • 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 852 words of copy

    The homepage carries about 852 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule an Appointment” and “Book Your Appointment Today”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Call (708) 486-2600”, “Book Your Appointment Today” and “Learn more”.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

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

  • 19 other companies contacted

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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 mimithealth.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Squarespace
Framework
jQuery
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on mimithealth.com, including 27 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

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