Website review, no card needed
helloalma.com website review
Visit site (opens in a new tab)Reviewed 4 November 202630 issues · 78 checks
This review found 30 issues worth fixing on helloalma.com, 12 of them high impact, across 78 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 95 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 96 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 103 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 107 ms |
| Aug 22, 2026 | 105 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 99 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 101 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 106 ms |
| Oct 10, 2026 | 107 ms |
| Oct 17, 2026 | 110 ms |
| Oct 24, 2026 | 109 ms |
| Oct 31, 2026 | 109 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
Use efficient cache lifetimes
2.4 s · 11.0 MB75 files are served with short cache lifetimes, so returning visitors download them again (11.0 MB).
Reduce unused JavaScript
1.1 s · 669 KiBAbout 669 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.
Render-blocking requests
1.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and Google Maps and others), adding 836 KiB and 1.3 s of main-thread time.
Improve image delivery
150 ms · 861 KiB15 images could be 861 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 537 ms
537 msGoogle Tag Manager costs a phone 537 ms of main-thread work and 186 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 404 ms. During a long task the page ignores taps.
Optanon adds 272 ms
272 msOptanon costs a phone 272 ms of main-thread work and 208 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.
Google Maps adds 247 ms
247 msGoogle Maps costs a phone 247 ms of main-thread work and 328 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.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need.
Reduce unused CSS
38 KiBAbout 38 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 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.
Time to Interactive: 18.7 s
18.7 sThe page becomes fully interactive after 18.7 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 854 ms
854 msReal visitors wait 854 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.032
0.032The layout barely moves while loading (CLS 0.032, good is under 0.1).
Images and page weight
Page weight: 11.8 MB in 122 requests
11.8 MBYour homepage downloads 11.8 MB in 122 requests on a phone: media 8.9 MB (1), scripts 1.3 MB (32) and images 1.3 MB (38). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
644 KiB6 images are downloaded at several times the size a phone draws them, for example alma_provider_daley_renee_reneedaley_01a.jpg at 960 px wide, shown at 95 px. Resized copies would save about 644 KiB.
3 images in older formats
3 images (330 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 3.4 g of CO₂ per visit
3.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.36 g of CO₂e: 402.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 checks passed
Every image has alt text
All 22 images in the HTML carry an alt attribute.
SEO
Structured data has 1 problem
Structured data found (FAQPage, MedicalOrganization, Organization and Service) but with 1 problem, for example “Service: no offers (price) block”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
31 internal links, 148 external
The homepage links to 31 pages on helloalma.com and 148 external pages.
7 checks passed
Meta description: 71 characters
Your meta description is 71 characters: “Alma makes it easy to find high-quality, affordable mental health care.”.
One H1 headline
Your main headline reads: “Find the right therapist who accepts your insurance”.
Title: 36 characters
Your title is a healthy 36 characters: “Alma — Simplifying Access to Therapy”.
Canonical URL set
The canonical URL is https://helloalma.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://helloalma.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
60%The HTML your server sends has 519 of the 869 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://helloalma.com/llms.txt (4 KiB, 17 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://helloalma.com/providers-landing is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://helloalma.com/providers-landing and https://helloalma.com/client-tou have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://helloalma.com/providers-landing has no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://helloalma.com/careers, https://helloalma.com/providers-landing, https://helloalma.com/refer-a-provider, https://helloalma.com/types-of-therapy and https://helloalma.com/client-tou took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.
4 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
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”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
20 of 23 tappable elements near the top are at least 24 px.
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: 18 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 869 words of copy
The homepage carries about 869 words of visible text.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Join as a Provider” and “Join Alma”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 helloalma.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on helloalma.com, including 19 speed issues, 2 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.