Website review, no card needed
conceptmedical.com website review
Visit site (opens in a new tab)Reviewed 2 November 202637 issues · 81 checks
This review found 37 issues worth fixing on conceptmedical.com, 17 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 6.2 s |
| May 23, 2026 | 6.2 s |
| May 30, 2026 | 6.2 s |
| Jun 6, 2026 | 6.1 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 360 ms |
| May 23, 2026 | 360 ms |
| May 30, 2026 | 360 ms |
| Jun 6, 2026 | 354 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 132 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 143 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 143 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 116 ms |
| Oct 17, 2026 | 115 ms |
| Oct 24, 2026 | 123 ms |
| Oct 31, 2026 | 127 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
1.3 s
2.7 s
4.0 s
5.4 s
6.7 s
8.0 s
9.4 s
10.7 s
Speed
Use efficient cache lifetimes
6.5 s · 1.8 MB79 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Reduce unused JavaScript
4.0 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
4.8 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Font display
1.9 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.9 s).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.4 MB and 1.2 s of main-thread time.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 674 ms
674 msGoogle Tag Manager costs a phone 674 ms of main-thread work and 1.3 MB 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.
Improve image delivery
411 KiB5 images could be 411 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 265 ms
265 msGoogle CDN costs a phone 265 ms of main-thread work and 742 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.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
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 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 541 ms
541 msYour server sent the HTML in 541 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.
Real-user LCP: 4.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 19.6 s
19.6 sYour largest element takes 19.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Innovating Healthcare by Revolutionizing Medical Solutions”.
Speed Index: 19.7 s
19.7 sVisually, the page fills in at 19.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
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.
Tap response (INP) got 65% faster for real visitors
-65%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 360 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 42% faster for real visitors
-42%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 6.2 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 185 ms
185 msScripts block the page for only 185 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 114 requests
4.4 MBYour homepage downloads 4.4 MB in 114 requests on a phone: scripts 2.6 MB (48), images 1.2 MB (20) and other files 365 KiB (14). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (371 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images in older formats
3 images (295 KiB) 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.
About 1.3 g of CO₂ per visit
1.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 150.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
121 internal links, 19 external
The homepage links to 121 pages on conceptmedical.com and 19 external pages.
7 checks passed
Meta description: 115 characters
Your meta description is 115 characters: “Explore Concept Medical's innovative approach in developing groundbreaking medical devices for cardiovascular care.”.
Title: 48 characters
Your title is a healthy 48 characters: “Concept Medical: Pioneering Drug Coated Balloons”.
Canonical URL set
The canonical URL is https://www.conceptmedical.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Medical Device Company, MedicalBusiness and MedicalWebPage.
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.conceptmedical.com/sitemap_index.xml.
AI search readiness
4 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.
Text is in the HTML
Your server sends the page's text in the HTML (612 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.conceptmedical.com/llms.txt (11 KiB, 82 links), a plain-text guide to the site for AI tools.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.conceptmedical.com/drug-coated-balloon-dcb, whose canonical is https://www.conceptmedical.com/dcb. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://www.conceptmedical.com/about, https://www.conceptmedical.com/4es, https://www.conceptmedical.com/press, https://www.conceptmedical.com/products, https://www.conceptmedical.com/magictouch-scb and https://www.conceptmedical.com/magictouch-avf and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
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 small tap targets
7 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 257 words of copy
The homepage carries about 257 words of visible text.
2 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Get In Touch”, “Contact Us” and “CONTACT US”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
9 cookies set on arrival
9Opening the homepage sets 9 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.
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 conceptmedical.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 Analytics | Google Tag Manager
- Hosting
- Airlink As Ap Airlink Teleservices Private Limited
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on conceptmedical.com, including 19 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.