Website review, no card needed
companionmedical.com website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 88 checks
This review found 39 issues worth fixing on companionmedical.com, 11 of them high impact, across 88 checks. The most urgent: 1 image over 500 KB. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 120 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 123 ms |
| Aug 15, 2026 | 127 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 126 ms |
| Sep 5, 2026 | 125 ms |
| Sep 12, 2026 | 125 ms |
| Sep 19, 2026 | 125 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
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.3 s
2.7 s
3.1 s
Speed
Reduce unused JavaScript
2.3 s · 484 KiBAbout 484 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 843 KiB112 files are served with short cache lifetimes, so returning visitors download them again (843 KiB).
Improve image delivery
350 ms · 725 KiB5 images could be 725 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Minify JavaScript
600 ms · 71 KiB71 KiB could be saved by minifying JavaScript.
Render-blocking requests
550 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused CSS
300 ms · 74 KiBAbout 74 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,879 HTML elements
The page has 2,879 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
coveo.com adds 21 ms
21 mscoveo.com costs a phone 21 ms of main-thread work and 361 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.
6 third-party services on the page
6 third-party services load with your homepage (Optanon, mPulse and Google CDN and others), adding 691 KiB and 284 ms of main-thread time.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 125 ms. During a long task the page ignores taps.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 714 ms of it running JavaScript. That is comfortably low.
Server response: 12 ms
12 msYour server sent the HTML in 12 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: 10.2 s
10.2 sYour largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MiniMed Go system”.
Time to Interactive: 10.3 s
10.3 sThe page becomes fully interactive after 10.3 s. Good is under 3.8 s.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 120 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 143 ms
143 msReal visitors wait 143 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 170 ms
170 msScripts block the page for only 170 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.032
0.032The layout barely moves while loading (CLS 0.032, good is under 0.1).
Images and page weight
1 image over 500 KB
MiniMed-Champion-Alex-Zverev-Dontguess-Go-clip.gif weighs 34.9 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
10.3 MB1 image is downloaded at several times the size a phone draws it, for example MiniMed-Champion-Alex-Zverev-Dontguess-Go-clip.gif at 1,280 px wide, shown at 358 px. Resized copies would save about 10.3 MB.
2 images in older formats
2 images (35.1 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.
Page weight: 2.2 MB in 173 requests
2.2 MBYour homepage downloads 2.2 MB in 173 requests on a phone: images 1.0 MB (90), scripts 785 KiB (50) and fonts 207 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 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.
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.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails 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.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “MiniMed Go™ System | MiniMed”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
107 internal links, 24 external
The homepage links to 107 pages on companionmedical.com and 24 external pages.
6 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “The system remembers your insulin doses, reminds you when more is needed, and recommends smart actions, so you can focu…”.
One H1 headline
Your main headline reads: “MiniMed Go system”.
Canonical URL set
The canonical URL is https://www.minimed.com/en-us/products/minimed-go-system.
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://www.minimed.com/en-us/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.
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 (2,620 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.minimed.com/llms.txt (8 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.minimed.com/en-us is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 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.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Pasting is blocked
A form field blocks pasting, which frustrates password managers and people on phones.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
12 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 11-field form
Your longest form asks for 11 fields (8 required). Every extra field lowers completion.
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,412 words of copy
The homepage carries about 2,412 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Diabetes.shop” and “Get started”.
15 calls to action
The homepage has 15 calls to action, for example “Diabetes.shop”, “Get Started” and “Order supplies”.
Direct contact links
Visitors can reach you directly: 2 phone links and 3 email links.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 companionmedical.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Medtronic, Incorporated
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on companionmedical.com, including 17 speed issues, 2 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.