Website review, no card needed
vitalize.care website review
Visit site (opens in a new tab)Reviewed 23 October 202625 issues · 68 checks
This review found 25 issues worth fixing on vitalize.care, 3 of them high impact, across 68 checks. The most urgent: 13 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Vitalize
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 828 ms |
| May 9, 2026 | 895 ms |
| May 16, 2026 | 947 ms |
| May 23, 2026 | 884 ms |
| May 30, 2026 | 851 ms |
| Jun 6, 2026 | 851 ms |
| Jun 13, 2026 | 862 ms |
| Jun 20, 2026 | 912 ms |
| Jun 27, 2026 | 923 ms |
| Jul 4, 2026 | 964 ms |
| Jul 11, 2026 | 985 ms |
| Jul 18, 2026 | 954 ms |
| Jul 25, 2026 | 982 ms |
| Aug 1, 2026 | 965 ms |
| Aug 8, 2026 | 939 ms |
| Aug 15, 2026 | 982 ms |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 81 ms |
| May 9, 2026 | 85 ms |
| May 16, 2026 | 93 ms |
| May 23, 2026 | 74 ms |
| May 30, 2026 | 70 ms |
| Jun 6, 2026 | 74 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 78 ms |
| Jun 27, 2026 | 83 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 84 ms |
| Jul 18, 2026 | 83 ms |
| Jul 25, 2026 | 82 ms |
| Aug 1, 2026 | 78 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 91 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 90 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
Mobile performance score: 85
85/100Your mobile performance score is 85 (desktop: 99). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 95 KiBAbout 95 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
framerusercontent.com adds 277 ms
277 msframerusercontent.com costs a phone 277 ms of main-thread work and 600 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.
5 third-party services on the page
5 third-party services load with your homepage (framerusercontent.com, framer.com and zi-scripts.com and others), adding 662 KiB and 291 ms of main-thread time.
Improve image delivery
97 KiB5 images could be 97 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
22 KiB4 files are served with short cache lifetimes, so returning visitors download them again (22 KiB).
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, 406 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.8 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 4.0 s
4.0 sYour largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
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.
Time to Interactive: 4.0 s
4.0 sThe page becomes fully interactive after 4.0 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 81 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Speed Index: 2.3 s
2.3 sVisually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.19 g of CO₂e: 23.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 700 KiB in 47 requests
700 KiBYour homepage downloads 700 KiB in 47 requests on a phone: scripts 335 KiB (27), images 187 KiB (7) and fonts 136 KiB (4). That is a lean page.
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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
13 text elements with low contrast
13 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 (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h5, h1 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (8 characters)
Your title is only 8 characters: “Vitalize”. 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.
5 H1 headlines
There are 5 <h1> headlines (“Transforming how health systems optimize labor”, “<90 days” and “65%”). One clear main headline is easier for people and search engines.
63 internal links, 2 external
The homepage links to 63 pages on vitalize.care and 2 external pages.
5 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Vitalize is the one AI platform that unifies staffing, scheduling, flow, and capacity—replacing reactivity with proacti…”.
Canonical URL set
The canonical URL is https://vitalize.care/.
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://vitalize.care/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.
No llms.txt
There is no https://vitalize.care/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.
2 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 (514 words), so crawlers that don't run JavaScript still read it.
Other pages
9 linked pages hidden from search
https://vitalize.care/blog/vitalize-series-a, https://vitalize.care/solutions, https://vitalize.care/intelligence, https://vitalize.care/why-vitalize, https://vitalize.care/blog and https://vitalize.care/careers and 3 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
9 pages share a title
/, https://vitalize.care/solutions, https://vitalize.care/intelligence, https://vitalize.care/why-vitalize, https://vitalize.care/blog and https://vitalize.care/careers and 3 others all use the title “Vitalize”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages share a meta description
https://vitalize.care/solutions, https://vitalize.care/intelligence, https://vitalize.care/why-vitalize, https://vitalize.care/blog, https://vitalize.care/careers and https://vitalize.care/contact and 2 others use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://vitalize.care/blog/vitalize-series-a, https://vitalize.care/blog, https://vitalize.care/contact, https://vitalize.care/legal/terms-of-use and https://vitalize.care/legal/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 9 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 9 pages that loaded have a meta description.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
9 of 10 tappable elements near the top are at least 24 px.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 348 words of copy
The homepage carries about 348 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a demo” and “Contact”.
13 calls to action
The homepage has 13 calls to action, for example “Contact”, “Book a demo” and “Join our team”.
Privacy and tracking
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.
6 other companies contacted
Loading the homepage contacts 6 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 vitalize.care, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Framer
Hiring
- Hiring
- 20 open roles
- Teams
- Customer Experience (7), Product & Eng (7), Growth (5), G&A (1)
- Job board
- ashby
- Careers page
- jobs.ashbyhq.com/vitalize (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on vitalize.care, including 7 speed issues, 4 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.