Website review, no card needed

islandoasis.com logo

islandoasis.com website review

Visit site (opens in a new tab)Reviewed 9 November 202628 issues · 75 checks

This review found 28 issues worth fixing on islandoasis.com, 11 of them high impact, across 75 checks. The most urgent: improve image delivery. 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
1.4 s1.2 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Oct 24, 20261.3 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
97 ms77 msMay 16Oct 3195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202680 ms
May 23, 202683 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202680 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202679 ms
Aug 8, 202680 ms
Aug 15, 202685 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202688 ms
Sep 26, 202693 ms
Oct 3, 202692 ms
Oct 10, 202692 ms
Oct 17, 202691 ms
Oct 24, 202688 ms
Oct 31, 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 islandoasis.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. islandoasis.com at 0.6 s0.6 s
  2. islandoasis.com at 1.2 s1.2 s
  3. islandoasis.com at 1.8 s1.8 s
  4. islandoasis.com at 2.5 s2.5 s
  5. islandoasis.com at 3.1 s3.1 s
  6. islandoasis.com at 3.7 s3.7 s
  7. islandoasis.com at 4.3 s4.3 s
  8. islandoasis.com at 4.9 s4.9 s

Speed

9 to fix63
  • Improve image delivery

    1.7 s · 575 KiB

    15 images could be 575 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

  • Reduce unused JavaScript

    1.8 s · 356 KiB

    About 356 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Use efficient cache lifetimes

    1.4 s · 223 KiB

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

  • Mobile performance score: 63

    63/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Optanon and azure.com and others), adding 1.4 MB and 581 ms of main-thread time.

  • Render-blocking requests

    450 ms

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

  • Google Tag Manager adds 370 ms

    370 ms

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

  • Optanon adds 96 ms

    96 ms

    Optanon costs a phone 96 ms of main-thread work and 419 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.

  • Shopify adds 37 ms

    37 ms

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    30 ms · 33 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 15.1 s

    15.1 s

    Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fruits including a lemon, lime, strawberry, and coconut wit…”.

  • Time to Interactive: 15.3 s

    15.3 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

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

    +12%

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.4 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: 2.0 s

    2.0 s

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

  • Real-user INP: 102 ms

    102 ms

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

  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (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.

  • Total Blocking Time: 186 ms

    186 ms

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

  • Cumulative Layout Shift: 0.054

    0.054

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

Images and page weight

3 to fix74
  • Page weight: 3.2 MB in 185 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 185 requests on a phone: images 1.1 MB (28), scripts 945 KiB (52) and other files 708 KiB (88). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Fruit_Explosion_Banner_IO_HOMEPAGE_mobile.png 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

    88 KiB

    1 image is downloaded at several times the size a phone draws it, for example Island_Oasis_Logo.jpg at 386 px wide, shown at 64 px. Resized copies would save about 88 KiB.

  • 2 images in older formats

    2 images (235 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.

  • 6 images below the first screen load straight away

    6 images further down the page (198 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.91 g

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

Accessibility

3 to fixGoogle 9094
  • 9 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 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.

  • 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
  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 8593
  • Meta description is long (190 characters)

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

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 44 internal links, 10 external

    The homepage links to 44 pages on islandoasis.com and 10 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Island Oasis”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Island Oasis Premium Beverage Mixes”.

  • Canonical URL set

    The canonical URL is https://islandoasis.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://islandoasis.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: 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 (269 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 7388
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    20 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • 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 188 words

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

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

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Register” and “Learn More”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies (measured from a US location before any click).

  • 17 other companies contacted

    Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 islandoasis.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Onetrust Consent Management · Tapita Seo Speed · Sc Easy Redirects · Social Widget · nfcube.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

Stack

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Employees
140
Headquarters
Walpole

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on islandoasis.com, including 13 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