Website review, no card needed
aloha.com website review
Visit site (opens in a new tab)Reviewed 3 November 202619 issues · 81 checks
This review found 19 issues worth fixing on aloha.com, 6 of them high impact, across 81 checks. The most urgent: page weight: 5.4 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for ALOHA
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 204 ms |
| May 23, 2026 | 199 ms |
| May 30, 2026 | 195 ms |
| Jun 6, 2026 | 192 ms |
| Jun 13, 2026 | 187 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 197 ms |
| Jul 25, 2026 | 184 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 164 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 167 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 171 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 180 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 192 ms |
| Oct 24, 2026 | 195 ms |
| Oct 31, 2026 | 195 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
Not measured in this review.
Core Web Vitals
Real-user TTFB: 884 ms
884 msReal visitors wait 884 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 204 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 193 ms
193 msReal visitors wait 193 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
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.
Images and page weight
Page weight: 5.4 MB
5.4 MBYour homepage downloads 5.4 MB on a phone, 1.7 MB of it images (32%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Fall_BOGO_Mobile.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
144 KiB1 image is downloaded at several times the size a phone draws it, for example Logo.svg at 3,760 px wide, shown at 120 px. Resized copies would save about 144 KiB.
5 images in older formats
5 images (418 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.
2 images below the first screen load straight away
2 images further down the page (139 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 184.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail 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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 5 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.
Meta description is long (239 characters)
Your meta description is 239 characters; Google truncates after about 160, so the end of your pitch is cut.
115 internal links, 14 external
The homepage links to 115 pages on aloha.com and 14 external pages.
6 checks passed
Title: 55 characters
Your title is a healthy 55 characters: “Welcome to ALOHA. The Better Plant-Based Protein Brand.”.
Canonical URL set
The canonical URL is https://aloha.com/.
Structured data in place
Structured data found: Organization 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://aloha.com/sitemap.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 (1,250 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
/collections/last-chance-savings is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without an H1
/products/gift-card, /pages/refer-a-friend and /pages/about-us-our-mission have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
/pages/about-us-our-mission took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 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.
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 a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=148020299&tm=gtm002&Ver=2&mid=6e299d97-b425-4171-9464-05e2b007b4a2&bo=1&sid=8442fb40d7c111f1a0fdd5709b74fa8d&vid=844314e0d7c111f18d21e19929619a28&vids=1&msclkid=N>m_.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “[splide] Already mounted!”.
2 checks passed
Tap targets are thumb-sized
49 of 60 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Short HSTS lifetime
HSTS is set, but max-age is 91 days; one year is the recommended minimum.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
7 checks passed
Served over HTTPS
The homepage is served over HTTPS (aloha.com).
Valid certificate (52 days left)
The certificate from Let's Encrypt · YE2 verifies for aloha.com and is valid for another 52 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://aloha.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 48 links work
All 48 links checked from your homepage (40 internal, 8 external) answered without errors; 13 did not answer within 5 s.
Domain and trust
No CAA record
aloha.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
aloha.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 28 years old
28 yearsaloha.com was registered in May 1998 through Tucows Domains Inc.. An established domain carries more trust with email providers and search engines.
Registered until Feb 2031
aloha.com is registered until Feb 2031.
Content and conversion
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 976 words of copy
The homepage carries about 976 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Free shipping on any order $40+” and “SHOP”.
22 calls to action
The homepage has 22 calls to action, for example “Join the Waitlist | Chocolate Pistachio”, “Peppermint is back! — Shop Now” and “Free shipping on any order $40+”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 30 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.
Email authentication
Email authentication score: 95/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:spf.mtasv.net include:mailgun.org include:mail.zendesk.com include:servers.mcsv.net include:spf.protect…”.
DKIM signing found
A DKIM key is published (selector “google”, “selector1” and “k1”), so receivers can verify mail really came from you.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 5 mores (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.
37 cookies set on arrival
37Opening the homepage sets 37 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.
65 other companies contacted
Loading the homepage contacts 65 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on aloha.com, including 1 speed issue, 2 SEO issues and 1 conversion gap. 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.