Website review, no card needed
cimas.co.zw website review
Visit site (opens in a new tab)Reviewed 26 October 202640 issues · 88 checks
This review found 40 issues worth fixing on cimas.co.zw, 14 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 218 ms |
| May 16, 2026 | 222 ms |
| May 23, 2026 | 227 ms |
| May 30, 2026 | 224 ms |
| Jun 6, 2026 | 228 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 211 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 201 ms |
| Jul 11, 2026 | 207 ms |
| Jul 18, 2026 | 219 ms |
| Jul 25, 2026 | 214 ms |
| Aug 1, 2026 | 214 ms |
| Aug 8, 2026 | 205 ms |
| Aug 15, 2026 | 199 ms |
| Aug 22, 2026 | 208 ms |
| Aug 29, 2026 | 203 ms |
| Sep 5, 2026 | 212 ms |
| Sep 12, 2026 | 223 ms |
| Sep 19, 2026 | 229 ms |
| Sep 26, 2026 | 252 ms |
| Oct 3, 2026 | 254 ms |
| Oct 10, 2026 | 258 ms |
| Oct 17, 2026 | 265 ms |
| Oct 24, 2026 | 258 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
Speed
Render-blocking requests
5.6 s71 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.6 s.
Reduce unused JavaScript
3.3 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Reduce unused CSS
1.1 s · 389 KiBAbout 389 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.
Main-thread work: 13.0 s
A phone's processor spends 13.0 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 35). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 3.4 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (powerapps.com, YouTube and Google Tag Manager and others), adding 4.3 MB and 1.7 s of main-thread time.
powerapps.com adds 828 ms
828 mspowerapps.com costs a phone 828 ms of main-thread work and 3.0 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.
YouTube adds 551 ms
551 msYouTube costs a phone 551 ms of main-thread work and 993 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.
2,140 HTML elements
The page has 2,140 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
156 KiB3 images could be 156 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 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: 22.0 s
22.0 sYour largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “2026 Benefits & Contributions Learn More”.
Total Blocking Time: 7.1 s
7.1 sScripts block taps and scrolling for 7.1 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 41.1 s
41.1 sThe page becomes fully interactive after 41.1 s. Good is under 3.8 s.
Speed Index: 13.3 s
13.3 sVisually, the page fills in at 13.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 273 ms
273 msReal visitors wait 273 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 998 ms
998 msReal visitors wait 998 ms for your server to start answering (75th percentile). Good is under 800 ms.
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) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 218 ms to 258 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.9 MB in 272 requests
6.9 MBYour homepage downloads 6.9 MB in 272 requests on a phone: scripts 4.6 MB (112), images 1.1 MB (37) and fonts 522 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
74 KiB1 image is downloaded at several times the size a phone draws it, for example Cimas-medical-aid-80-years-.webp at 1,920 px wide, shown at 370 px. Resized copies would save about 74 KiB.
About 2.0 g of CO₂ per visit
1.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.96 g of CO₂e: 234.7 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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
32 text elements with low contrast
32 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (25 characters)
Your title is only 25 characters: “Home - Cimas Health Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Medical Aid and Healthcare Services in Zimbabwe” and “Medication”). One clear main headline is easier for people and search engines.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
96 internal links, 33 external
The homepage links to 96 pages on cimas.co.zw and 33 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://cimas.co.zw/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://cimas.co.zw/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://cimas.co.zw/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 sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (661 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://cimas.co.zw/for-providers, https://cimas.co.zw/join-us, https://cimas.co.zw/our-history, https://cimas.co.zw/our-packages, https://cimas.co.zw/secure-packages and https://cimas.co.zw/medical-services and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://cimas.co.zw/for-providers, https://cimas.co.zw/our-packages, https://cimas.co.zw/secure-packages, https://cimas.co.zw/medical-services, https://cimas.co.zw/igo and https://cimas.co.zw/cimas-care and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://cimas.co.zw/medical-services, https://cimas.co.zw/igo and https://cimas.co.zw/cimas-care took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 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.
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.
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
5 small tap targets
5 of 17 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.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v6.7.2/css/all.css?ver=7.1.3' from origin 'https://ci…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 522 words of copy
The homepage carries about 522 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
15 calls to action
The homepage has 15 calls to action, for example “Join Us”, “Contact Us” and “Learn More”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 4 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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, 1 of them by other companies (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.
25 other companies contacted
Loading the homepage contacts 25 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 cimas.co.zw, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on cimas.co.zw, including 21 speed issues and 5 SEO issues. 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.