Website review, no card needed

vaoalavanilla.com logo

vaoalavanilla.com website review

Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 77 checks

This review found 30 issues worth fixing on vaoalavanilla.com, 8 of them high impact, across 77 checks. The most urgent: 43 text elements with low contrast. 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

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

How it loaded on a phone

  1. vaoalavanilla.com at 0.4 s0.4 s
  2. vaoalavanilla.com at 0.8 s0.8 s
  3. vaoalavanilla.com at 1.2 s1.2 s
  4. vaoalavanilla.com at 1.6 s1.6 s
  5. vaoalavanilla.com at 2.0 s2.0 s
  6. vaoalavanilla.com at 2.3 s2.3 s
  7. vaoalavanilla.com at 2.7 s2.7 s
  8. vaoalavanilla.com at 3.1 s3.1 s

Speed

4 to fix90
  • Use efficient cache lifetimes

    250 ms · 757 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and Judge.me and others), adding 2.0 MB and 584 ms of main-thread time.

  • Reduce unused JavaScript

    375 KiB

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

  • seguno.com adds 75 ms

    75 ms

    seguno.com costs a phone 75 ms of main-thread work and 1.3 MB 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

    250 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

  • Render-blocking requests

    250 ms

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

  • 3 long tasks on the main thread

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

  • Improve image delivery

    66 KiB

    4 images could be 66 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    55 KiB

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

  • Reduce unused CSS

    10 ms · 34 KiB

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

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

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

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.7 s

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

  • Server response: 98 ms

    98 ms

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

Core Web Vitals

4 to fix97
  • Time to Interactive: 10.6 s

    10.6 s

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

  • Speed Index: 6.6 s

    6.6 s

    Visually, the page fills in at 6.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.

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Welcome to our Store for Vaoala Vanilla. Our aim is to offe…”.

  • Total Blocking Time: 102 ms

    102 ms

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

  • Cumulative Layout Shift: 0.05

    0.05

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

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 111 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 111 requests on a phone: images 1.2 MB (18), scripts 1.0 MB (42) and other files 396 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.80 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 96.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

9 to fixGoogle 8287
  • 43 text elements with low contrast

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

  • 4 tap targets too small

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

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

  • 4 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Vaoala Vanilla | Ethical Samoan Vanilla Products & Organic Pacific Farming”.

  • 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 (“Organic Sun-cured Vanilla Beans - vacuum packed (…” and “Designer 'Bird of Paradise' Journal Notebook OR D…”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 59 internal links, 12 external

    The homepage links to 59 pages on vaoalavanilla.com and 12 external pages.

4 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “A 100% Samoan owned ethical business using indigenous story-telling and organic techniques of growing and producing van…”.

  • Canonical URL set

    The canonical URL is https://vaoalavanilla.com/.

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

Other pages

3 to fix86
  • 2 pages share a title

    https://vaoalavanilla.com/products/organic-sun-cured-vanilla-beans-vacuum-packed and https://vaoalavanilla.com/products/organic-sun-cured-vanilla-beans-vacuum-packed_variant-35597752926376 all use the title “Organic Sun-cured Vanilla Beans - vacuum packed (3) – vaoalavanilla”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://vaoalavanilla.com/collections/all and https://vaoalavanilla.com/blogs/vaoala-vanilla-blogs have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://vaoalavanilla.com/products/organic-sun-cured-vanilla-beans-vacuum-packed and https://vaoalavanilla.com/products/organic-sun-cured-vanilla-beans-vacuum-packed_variant-35597752926376 use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 21 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 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 9287
  • 10 small tap targets

    10 of 29 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 “Failed to load resource: net::ERR_FAILED”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 902 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop” and “Sign Up”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 59 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 1 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.

  • 21 other companies contacted

    Loading the homepage contacts 21 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 vaoalavanilla.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Seguno Popups · shopifyapps.com · judge.me · printful.com

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

  • The footer still says © 2023.

Stack

E-commerce
Shopify
Hosting
Cloudflare

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 vaoalavanilla.com, including 8 speed issues, 4 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

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