Website review, no card needed

alohas.com logo

alohas.com website review

Visit site (opens in a new tab)Reviewed 19 October 202638 issues · 87 checks

This review found 38 issues worth fixing on alohas.com, 11 of them high impact, across 87 checks. The most urgent: page weight: 5.2 MB in 375 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
2.1 s1.8 sApr 25Oct 101.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.0 s
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
236 ms156 msApr 25Oct 10227 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026171 ms
May 2, 2026170 ms
May 9, 2026165 ms
May 16, 2026169 ms
May 23, 2026188 ms
May 30, 2026209 ms
Jun 6, 2026215 ms
Jun 13, 2026211 ms
Jun 20, 2026193 ms
Jun 27, 2026188 ms
Jul 4, 2026192 ms
Jul 11, 2026195 ms
Jul 18, 2026197 ms
Jul 25, 2026195 ms
Aug 1, 2026196 ms
Aug 8, 2026198 ms
Aug 15, 2026202 ms
Aug 22, 2026206 ms
Aug 29, 2026209 ms
Sep 5, 2026208 ms
Sep 12, 2026206 ms
Sep 19, 2026206 ms
Sep 26, 2026212 ms
Oct 3, 2026220 ms
Oct 10, 2026227 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 alohas.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alohas.com at 0.4 s0.4 s
  2. alohas.com at 0.8 s0.8 s
  3. alohas.com at 1.2 s1.2 s
  4. alohas.com at 1.6 s1.6 s
  5. alohas.com at 2.0 s2.0 s
  6. alohas.com at 2.4 s2.4 s
  7. alohas.com at 2.8 s2.8 s
  8. alohas.com at 3.2 s3.2 s

Speed

9 to fix54
  • 5,173 HTML elements

    The page has 5,173 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 4.9 s

    A phone's processor spends 4.9 s on main-thread work while loading, 2.9 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 (Clarity, Google Tag Manager and Shopify and others), adding 1.1 MB and 1.6 s of main-thread time.

  • Improve image delivery

    1.1 MB

    14 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 72). Pages that score under 90 lose visitors before the first paint.

  • Clarity adds 783 ms

    783 ms

    Clarity costs a phone 783 ms of main-thread work and 29 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.

  • Render-blocking requests

    750 ms

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

  • Reduce unused JavaScript

    150 ms · 571 KiB

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

  • Google Tag Manager adds 557 ms

    557 ms

    Google Tag Manager costs a phone 557 ms of main-thread work and 522 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.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    203 KiB

    18 files are served with short cache lifetimes, so returning visitors download them again (203 KiB).

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    12 KiB

    About 12 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 KiB

    2 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 88 ms

    88 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 11.7 s

    11.7 s

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

  • Time to Interactive: 15.5 s

    15.5 s

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

  • Tap response (INP) got 31% slower for real visitors

    +31%

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

  • Total Blocking Time: 536 ms

    536 ms

    Scripts block taps and scrolling for 536 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 5.1 s

    5.1 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 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.

  • Largest content (LCP) held steady for real visitors

    -9%

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

7 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: 1.8 s

    1.8 s

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

  • Real-user INP: 196 ms

    196 ms

    Real visitors wait 196 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: 1.4 s

    1.4 s

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

  • Real-user TTFB: 667 ms

    667 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 5.2 MB in 375 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 375 requests on a phone: images 2.5 MB (51), scripts 1.4 MB (97) and other files 1.0 MB (172). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (380 KiB) is 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.5 g of CO₂ per visit

    1.48 g

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

2 checks passed
  • 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

7 to fixGoogle 8590
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 13 tap targets too small

    13 tap targets are too small or too close together to hit reliably with a finger.

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • 35 links without text

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

  • 7 form fields without a label

    7 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 50 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: 50 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9288
  • Title is short (26 characters)

    Your title is only 26 characters: “ALOHAS | On-demand Fashion”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • One H1 headline

    Your <h1> is empty.

  • 177 internal links, 60 external

    The homepage links to 177 pages on alohas.com and 60 external pages.

6 checks passed
  • Meta description: 111 characters

    Your meta description is 111 characters: “Shop responsibly now for an early bird discount and receive your shoes on-demand right on time for next season.”.

  • Canonical URL set

    The canonical URL is https://alohas.com/en-us.

  • 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://alohas.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://alohas.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix63
  • 1 page without a title

    https://alohas.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://alohas.com/customer_authentication/redirect 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://alohas.com/customer_authentication/redirect and https://alohas.com/en-us/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://alohas.com/en-us/collections/fall-winter, whose canonical is https://alohas.com/collections/best-sellers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://alohas.com/customer_authentication/redirect, https://alohas.com/en-us/products/gabe-rift-black-leather-loafers, https://alohas.com/en-us/products/aven-burgundy-vegan-leather-loafers, https://alohas.com/en-us/products/gabe-vintage-effect-brown-leather-loafers, https://alohas.com/en-us/products/aven-brown-vegan-leather-loafers and https://alohas.com/en-us/products/south-bicolor-black-brown-leather-ankle-boots and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

Best practices

2 to fixGoogle 9687
  • 44 small tap targets

    44 of 69 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'value')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

  • 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 473 words of copy

    The homepage carries about 473 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get exclusive discounts | Subscribe” and “Learn more”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Pre-order 15%”, “Pre-order” and “Track my order”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and TikTok Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Microsoft Clarity, Pinterest Tag and Snap Pixel (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.

  • 21 cookies set on arrival

    21

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

  • 38 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on alohas.com, including 16 speed issues, 2 SEO issues and 4 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