Website review, no card needed

inmodemd.com logo

inmodemd.com website review

Visit site (opens in a new tab)Reviewed 3 November 202650 issues · 90 checks

This review found 50 issues worth fixing on inmodemd.com, 20 of them high impact, across 90 checks. The most urgent: improve image delivery. 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.1 sMay 16Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.1 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
99 ms76 msMay 16Oct 3187 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202696 ms
May 23, 202688 ms
May 30, 202687 ms
Jun 6, 202683 ms
Jun 13, 202682 ms
Jun 20, 202683 ms
Jun 27, 202680 ms
Jul 4, 202681 ms
Jul 11, 202683 ms
Jul 18, 202681 ms
Jul 25, 202683 ms
Aug 1, 202683 ms
Aug 8, 202681 ms
Aug 15, 202680 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202681 ms
Oct 10, 202686 ms
Oct 17, 202687 ms
Oct 24, 202687 ms
Oct 31, 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

Full-page screenshot of inmodemd.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. inmodemd.com at 0.8 s0.8 s
  2. inmodemd.com at 1.5 s1.5 s
  3. inmodemd.com at 2.3 s2.3 s
  4. inmodemd.com at 3.1 s3.1 s
  5. inmodemd.com at 3.9 s3.9 s
  6. inmodemd.com at 4.6 s4.6 s
  7. inmodemd.com at 5.4 s5.4 s
  8. inmodemd.com at 6.2 s6.2 s

Speed

11 to fix38
  • Improve image delivery

    33.1 s · 7.8 MB

    15 images could be 7.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 33.1 s faster on a phone.

  • Use efficient cache lifetimes

    15.7 s · 24.3 MB

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

  • Reduce unused JavaScript

    5.2 s · 783 KiB

    About 783 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.

  • Render-blocking requests

    3.5 s

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

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 4.0 s

    A phone's processor spends 4.0 s on main-thread work while loading, 2.3 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 (Google CDN, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.8 MB and 1.5 s of main-thread time.

  • Reduce unused CSS

    590 ms · 144 KiB

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

  • Google CDN adds 547 ms

    547 ms

    Google CDN costs a phone 547 ms of main-thread work and 763 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 497 ms

    497 ms

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

  • 1,532 HTML elements

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

  • 14 long tasks on the main thread

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

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • Legacy JavaScript

    35 KiB

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

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • First Contentful Paint: 7.8 s

    7.8 s

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

  • Largest Contentful Paint: 59.8 s

    59.8 s

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

  • Speed Index: 17.5 s

    17.5 s

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

  • Time to Interactive: 60.7 s

    60.7 s

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

  • Total Blocking Time: 685 ms

    685 ms

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user CLS: 0.19

    0.19

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

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

    +33%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 29 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

2 checks passed
  • Real-user INP: 90 ms

    90 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix28
  • Page weight: 63.2 MB in 158 requests

    63.2 MB

    Your homepage downloads 63.2 MB in 158 requests on a phone: media 49.7 MB (10), images 10.6 MB (41) and scripts 1.9 MB (46). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Morpheus8-Cool-Mobile.gif weighs 6.1 MB. On a phone connection a single image that size takes seconds.

  • 26 images in older formats

    26 images (10.4 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.

  • 12 images below the first screen load straight away

    12 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    139 KiB

    2 images are downloaded at several times the size a phone draws them, for example Define-Homepage.png at 428 px wide, shown at 110 px. Resized copies would save about 139 KiB.

  • About 17.9 g of CO₂ per visit

    17.90 g

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

Accessibility

4 to fixGoogle 9294
  • 2 text elements with low contrast

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

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • 13 links without text

    13 visible links have no text or label, so screen readers cannot say where they go.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

3 to fixGoogle 8586
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 15 links crawlers can't follow

    15 links have no real href, so search engines can't follow them.

  • 14 links with vague text

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

  • 125 internal links, 3 external

    The homepage links to 125 pages on inmodemd.com and 3 external pages.

7 checks passed
  • Meta description: 120 characters

    Your meta description is 120 characters: “InMode advanced aesthetic medical devices. Innovative radiofrequency technology for face, body, and wellness treatments.”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “InMode - Advanced Medical Aesthetic Technology”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.inmodemd.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.inmodemd.com/llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

7 to fix45
  • 2 linked pages are broken

    Your homepage links to https://www.inmodemd.com/contact-us and https://www.inmodemd.com/international, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 linked page hidden from search

    https://www.inmodemd.com/events is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.inmodemd.com/workstations and https://www.inmodemd.com/technologies all use the title “InMode Workstations & Medical Devices”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.inmodemd.com/careers has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.inmodemd.com/workstations and https://www.inmodemd.com/technologies use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.inmodemd.com/physician-finder, whose canonical is https://www.inmodemd.com/find-a-provider. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.inmodemd.com/events has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.inmodemd.com/physician-finder took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

1 checks passed
  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134601411&tm=gtm002&Ver=2&mid=c8689031-04b0-4f62-87ea-749e23f1bf4e&bo=1&sid=6f065210d76611f18fbf9547d2f4c415&vid=6f0672b0d76611f1b2a2b9dd66444078&vids=1&msclkid=N&gtm_.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to find a valid digest in the 'integrity' attribute for resource 'https://cdn.cookielaw.org/consent/211d40b0-d6e…”.

2 checks passed
  • Tap targets are thumb-sized

    29 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix61
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 29-field form

    Your longest form asks for 29 fields (9 required). Every extra field lowers completion.

  • Only about 165 words

    The homepage has only about 165 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

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

4 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact Us”, “Learn More” and “Learn more”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 14 cookies set on arrival

    14

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

  • 17 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 inmodemd.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
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Sucuri

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on inmodemd.com, including 23 speed issues, 3 SEO issues and 5 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