Website review, no card needed
cirtecmed.com website review
Visit site (opens in a new tab)Reviewed 26 October 202629 issues · 76 checks
This review found 29 issues worth fixing on cirtecmed.com, 12 of them high impact, across 76 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 91 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 91 ms |
| May 30, 2026 | 91 ms |
| Jun 6, 2026 | 92 ms |
| Jun 13, 2026 | 96 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 89 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 98 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 99 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 93 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 89 ms |
| Oct 17, 2026 | 92 ms |
| Oct 24, 2026 | 93 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
2.5 s · 2.1 MB12 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
1.8 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused JavaScript
1.1 s · 271 KiBAbout 271 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 77). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (JSDelivr CDN, Google CDN and cloudfront.net and others), adding 3.7 MB and 226 ms of main-thread time.
website-files.com adds 9 ms
9 mswebsite-files.com costs a phone 9 ms of main-thread work and 3.2 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.
Google CDN adds 95 ms
95 msGoogle CDN costs a phone 95 ms of main-thread work and 348 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.
Use efficient cache lifetimes
150 ms · 9 KiB9 files are served with short cache lifetimes, so returning visitors download them again (9 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 106 ms. During a long task the page ignores taps.
Reduce unused CSS
18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 204 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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: 11.4 s
11.4 sYour largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bringing Tomorrow's Medical Technologies to Life”.
Time to Interactive: 11.4 s
11.4 sThe page becomes fully interactive after 11.4 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.131
0.131The layout shifts by 0.131 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 91 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 85 ms
85 msReal visitors wait 85 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 711 ms
711 msReal visitors wait 711 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 56 ms
56 msScripts block the page for only 56 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.0 MB in 51 requests
5.0 MBYour homepage downloads 5.0 MB in 51 requests on a phone: images 2.9 MB (16), media 1.2 MB (3) and scripts 559 KiB (21). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
794 KiB6 images are downloaded at several times the size a phone draws them, for example 67fcc8cb439cf58595d75e8c_BraidingMIllingM_AR169.avif at 3,840 px wide, shown at 188 px. Resized copies would save about 794 KiB.
1 image below the first screen load straight away
1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.41 g of CO₂e: 169.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail 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.
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (21 characters)
Your title is only 21 characters: “Home | Cirtec Medical”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (180 characters)
Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization) but with 2 problems, for example “Organization: url is not an absolute URL ("/")”.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
100 internal links, 0 external
The homepage links to 100 pages on cirtecmed.com and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Bringing Tomorrow's Medical Technologies to Life”.
Canonical URL set
The canonical URL is https://www.cirtecmed.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://www.cirtecmed.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.cirtecmed.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (741 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
7 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.
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
37 small tap targets
37 of 63 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: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 636 words of copy
The homepage carries about 636 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
8 calls to action
The homepage has 8 calls to action, for example “Contact us”, “LEARN MORE” and “Learn More”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
12 cookies set on arrival
12Opening the homepage sets 12 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.
9 other companies contacted
Loading the homepage contacts 9 hosts 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 cirtecmed.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- Webflow
- Analytics
- Google Analytics
- Hosting
- Webflow
Company
- Employees
- 1,274
- Founded
- 1987
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on cirtecmed.com, including 14 speed issues, 4 SEO issues and 2 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.