Website review, no card needed

manuhealii.com logo

manuhealii.com website review

Visit site (opens in a new tab)Reviewed 5 November 202627 issues · 76 checks

This review found 27 issues worth fixing on manuhealii.com, 7 of them high impact, across 76 checks. The most urgent: page weight: 6.9 MB in 142 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
697 ms556 msMay 16Oct 31572 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026681 ms
May 23, 2026669 ms
May 30, 2026639 ms
Jun 6, 2026616 ms
Jun 13, 2026588 ms
Jun 20, 2026584 ms
Jun 27, 2026588 ms
Jul 4, 2026598 ms
Jul 11, 2026594 ms
Jul 18, 2026583 ms
Jul 25, 2026584 ms
Aug 1, 2026583 ms
Aug 8, 2026588 ms
Aug 15, 2026616 ms
Aug 22, 2026642 ms
Aug 29, 2026614 ms
Sep 5, 2026623 ms
Sep 12, 2026630 ms
Sep 19, 2026625 ms
Sep 26, 2026655 ms
Oct 3, 2026602 ms
Oct 10, 2026587 ms
Oct 17, 2026580 ms
Oct 24, 2026579 ms
Oct 31, 2026572 ms
Real-visitor tap response (INP)75th percentile, phones
76 ms61 msMay 16Oct 3163 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202670 ms
May 23, 202671 ms
May 30, 202671 ms
Jun 6, 202670 ms
Jun 13, 202671 ms
Jun 20, 202671 ms
Jun 27, 202671 ms
Jul 4, 202671 ms
Jul 11, 202667 ms
Jul 18, 202663 ms
Jul 25, 202663 ms
Aug 1, 202663 ms
Aug 8, 202668 ms
Aug 15, 202671 ms
Aug 22, 202674 ms
Aug 29, 202671 ms
Sep 5, 202671 ms
Sep 12, 202671 ms
Sep 19, 202671 ms
Sep 26, 202672 ms
Oct 3, 202671 ms
Oct 10, 202670 ms
Oct 17, 202669 ms
Oct 24, 202666 ms
Oct 31, 202663 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

Full-page screenshot of manuhealii.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. manuhealii.com at 0.4 s0.4 s
  2. manuhealii.com at 0.8 s0.8 s
  3. manuhealii.com at 1.1 s1.1 s
  4. manuhealii.com at 1.5 s1.5 s
  5. manuhealii.com at 1.9 s1.9 s
  6. manuhealii.com at 2.3 s2.3 s
  7. manuhealii.com at 2.6 s2.6 s
  8. manuhealii.com at 3.0 s3.0 s

Speed

4 to fix64
  • Improve image delivery

    700 ms · 1.2 MB

    14 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 43 KiB

    About 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Render-blocking requests

    300 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Reduce unused JavaScript

    20 ms · 35 KiB

    About 35 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 20 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, shop.app and salessquad.co.uk), adding 69 KiB and 16 ms of main-thread time.

  • Use efficient cache lifetimes

    5 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (5 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 185 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 20.5 s

    20.5 s

    Your largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 21.9 s

    21.9 s

    The page becomes fully interactive after 21.9 s. Good is under 3.8 s.

  • Speed Index: 10.6 s

    10.6 s

    Visually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.2 s

    2.2 s

    The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

  • 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) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 70 ms to 63 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

    Real visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 63 ms

    63 ms

    Real visitors wait 63 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.6 s

    0.6 s

    Real visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 351 ms

    351 ms

    Real visitors wait 351 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 15% faster for real visitors

    -15%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 6.9 MB in 142 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 142 requests on a phone: images 5.9 MB (32), other files 606 KiB (56) and scripts 211 KiB (40). Under 2 MB keeps phones on slow connections fast.

  • 12 images below the first screen load straight away

    12 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images in older formats

    6 images (752 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 1.9 g of CO₂ per visit

    1.94 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.94 g of CO₂e: 233.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9493
  • 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 (26 elements)

    All page content should be contained by landmarks: 26 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.

  • 15 links without text

    15 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

  • Meta description is long (252 characters)

    Your meta description is 252 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 73 internal links, 5 external

    The homepage links to 73 pages on manuhealii.com and 5 external pages.

5 checks passed
  • Title: 39 characters

    Your title is a healthy 39 characters: “A modern aloha collective – Manuheali'i”.

  • Canonical URL set

    The canonical URL is https://manuhealii.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://manuhealii.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://manuhealii.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.

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 (219 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://manuhealii.com/collections/pua-kala and https://manuhealii.com/collections/tops have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    2 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 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 2 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    31 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • 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.

  • Only about 168 words

    The homepage has only about 168 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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.

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Return to shop”, “Shop it” and “Shop the Collection”.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 manuhealii.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

salessquad.co.uk

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on manuhealii.com, including 9 speed issues, 3 SEO issues and 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25