Website review, no card needed

tanoa.shop logo

tanoa.shop website review

Visit site (opens in a new tab)Reviewed 16 November 202626 issues · 81 checks

This review found 26 issues worth fixing on tanoa.shop, 6 of them high impact, across 81 checks. The most urgent: main-thread work: 7.2 s. 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
947 ms832 msMay 30Nov 14876 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026918 ms
Jun 6, 2026870 ms
Jun 13, 2026868 ms
Jun 20, 2026848 ms
Jun 27, 2026845 ms
Jul 4, 2026865 ms
Jul 11, 2026879 ms
Jul 18, 2026902 ms
Jul 25, 2026909 ms
Aug 1, 2026901 ms
Aug 8, 2026902 ms
Aug 15, 2026896 ms
Aug 22, 2026908 ms
Aug 29, 2026899 ms
Sep 5, 2026873 ms
Sep 12, 2026888 ms
Sep 19, 2026877 ms
Sep 26, 2026909 ms
Oct 3, 2026909 ms
Oct 10, 2026911 ms
Oct 17, 2026917 ms
Oct 24, 2026923 ms
Oct 31, 2026934 ms
Nov 7, 2026905 ms
Nov 14, 2026876 ms
Real-visitor tap response (INP)75th percentile, phones
105 ms85 msMay 30Nov 1495 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202687 ms
Jun 6, 202688 ms
Jun 13, 202688 ms
Jun 20, 202688 ms
Jun 27, 202688 ms
Jul 4, 202687 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202690 ms
Aug 22, 202690 ms
Aug 29, 202695 ms
Sep 5, 202695 ms
Sep 12, 202696 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 202697 ms
Oct 10, 2026100 ms
Oct 17, 2026100 ms
Oct 24, 2026103 ms
Oct 31, 2026103 ms
Nov 7, 202697 ms
Nov 14, 202695 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 tanoa.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tanoa.shop at 0.7 s0.7 s
  2. tanoa.shop at 1.5 s1.5 s
  3. tanoa.shop at 2.2 s2.2 s
  4. tanoa.shop at 3.0 s3.0 s
  5. tanoa.shop at 3.7 s3.7 s
  6. tanoa.shop at 4.5 s4.5 s
  7. tanoa.shop at 5.2 s5.2 s
  8. tanoa.shop at 6.0 s6.0 s

Speed

8 to fix78
  • Main-thread work: 7.2 s

    A phone's processor spends 7.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 5,145 HTML elements

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

  • Improve image delivery

    650 ms · 537 KiB

    23 images could be 537 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • Mobile performance score: 78

    78/100

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

  • Render-blocking requests

    600 ms

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

  • Reduce unused JavaScript

    404 KiB

    About 404 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    300 ms · 84 KiB

    About 84 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.

  • Shopify adds 69 ms

    69 ms

    Shopify costs a phone 69 ms of main-thread work and 365 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Privy, Shopify and Klaviyo and others), adding 866 KiB and 278 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 118 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    32 KiB

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

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

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 11.4 s

    11.4 s

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

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

  • Speed Index: 5.8 s

    5.8 s

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

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s 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: 1.5 s

    1.5 s

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

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 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.2 s

    1.2 s

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

  • Real-user TTFB: 527 ms

    527 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 73 ms

    73 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix64
  • Page weight: 5.2 MB in 385 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 385 requests on a phone: images 2.6 MB (49), other files 1.4 MB (240) and scripts 952 KiB (81). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Naupaka_Mobile_Homepage_Template.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).

  • About 1.5 g of CO₂ per visit

    1.47 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9597
  • 2 tap targets too small

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4, h2 → h4 and h2 → h4), 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).

2 checks passed
  • Every image has alt text

    All 201 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 9289
  • 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 (“Tanoa Hawaii” and “Tanoa Hawaii”). One clear main headline is easier for people and search engines.

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

  • 376 internal links, 19 external

    The homepage links to 376 pages on tanoa.shop and 19 external pages.

6 checks passed
  • Meta description: 100 characters

    Your meta description is 100 characters: “Polynesian apparel, Samoan clothing, Aloha Shirts, Hawaii fashion, Pacific Fashion, Island lifestyle”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Tanoa Hawaii - Pacific Fashion and Island Lifestyle”.

  • Canonical URL set

    The canonical URL is https://tanoa.shop/.

  • 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://tanoa.shop/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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,035 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix98
  • 10 pages share a meta description

    https://tanoa.shop/collections/new-arrivals, https://tanoa.shop/collections/shop-all, https://tanoa.shop/collections/tanoa-dress-shirts, https://tanoa.shop/collections/golf-polos, https://tanoa.shop/collections/mens-shorts and https://tanoa.shop/collections/hoodies and 4 others use the same meta description. A description written for each page earns more clicks.

  • 3 pages slow to respond

    https://tanoa.shop/collections/shop-all, https://tanoa.shop/collections/men and https://tanoa.shop/collections/tanoa-dress-shirts took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot destructure property 'name' of 'e' as it is undefined.”.

2 checks passed
  • Tap targets are thumb-sized

    96 of 98 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 29 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 1,242 words of copy

    The homepage carries about 1,242 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP HERE” and “SHOP NOW”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “SHOP”, “SHOP ALL” and “LEARN MORE”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 2 of them by other companies (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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 tanoa.shop, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Depict Search Merchandising · Mbcbundlesapp · prooffactor.com · privy.com · nfcube.com · omnisnippet1.com · fera.ai

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 26 issues on tanoa.shop, including 11 speed issues, 3 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

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