Website review, no card needed

wholesomesweet.com logo

wholesomesweet.com website review

Visit site (opens in a new tab)Reviewed 9 November 202643 issues · 86 checks

This review found 43 issues worth fixing on wholesomesweet.com, 17 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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.6 s1.3 sMay 23Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.6 s
Jul 25, 20261.5 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
188 ms130 msMay 23Nov 7154 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026142 ms
May 30, 2026137 ms
Jun 6, 2026138 ms
Jun 13, 2026137 ms
Jun 20, 2026138 ms
Jun 27, 2026138 ms
Jul 4, 2026142 ms
Jul 11, 2026157 ms
Jul 18, 2026155 ms
Jul 25, 2026162 ms
Aug 1, 2026162 ms
Aug 8, 2026154 ms
Aug 15, 2026171 ms
Aug 22, 2026162 ms
Aug 29, 2026179 ms
Sep 5, 2026179 ms
Sep 12, 2026175 ms
Sep 19, 2026181 ms
Sep 26, 2026171 ms
Oct 3, 2026173 ms
Oct 10, 2026170 ms
Oct 17, 2026162 ms
Oct 24, 2026162 ms
Oct 31, 2026155 ms
Nov 7, 2026154 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 wholesomesweet.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wholesomesweet.com at 0.7 s0.7 s
  2. wholesomesweet.com at 1.3 s1.3 s
  3. wholesomesweet.com at 2.0 s2.0 s
  4. wholesomesweet.com at 2.7 s2.7 s
  5. wholesomesweet.com at 3.3 s3.3 s
  6. wholesomesweet.com at 4.0 s4.0 s
  7. wholesomesweet.com at 4.7 s4.7 s
  8. wholesomesweet.com at 5.3 s5.3 s

Speed

13 to fix42
  • Reduce unused JavaScript

    8.6 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.6 s faster on a phone.

  • Improve image delivery

    2.4 s · 2.1 MB

    21 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

  • Reduce unused CSS

    1.2 s · 286 KiB

    About 286 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.5 s

    A phone's processor spends 6.5 s on main-thread work while loading, 3.8 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 (YouTube, Klaviyo and reddit and others), adding 3.3 MB and 2.0 s of main-thread time.

  • YouTube adds 882 ms

    882 ms

    YouTube costs a phone 882 ms of main-thread work and 1.9 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.

  • Render-blocking requests

    900 ms

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

  • Minify JavaScript

    600 ms · 56 KiB

    56 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    450 ms · 189 KiB

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

  • Legacy JavaScript

    300 ms · 89 KiB

    Polyfills for old browsers add 89 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Klaviyo adds 281 ms

    281 ms

    Klaviyo costs a phone 281 ms of main-thread work and 623 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.

  • reddit adds 267 ms

    267 ms

    reddit costs a phone 267 ms of main-thread work and 28 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.

  • 20 long tasks on the main thread

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

  • Minify CSS

    150 ms · 6 KiB

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

  • 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: 7 ms

    7 ms

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

Core Web Vitals

8 to fix100
  • Fails Core Web Vitals for real visitors

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

  • First Contentful Paint: 10.1 s

    10.1 s

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

  • Largest Contentful Paint: 30.7 s

    30.7 s

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

  • Speed Index: 16.3 s

    16.3 s

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

  • Time to Interactive: 35.8 s

    35.8 s

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

  • Real-user TTFB: 896 ms

    896 ms

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

  • Total Blocking Time: 499 ms

    499 ms

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

  • 3 images without width and height

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

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

5 checks passed
  • 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: 171 ms

    171 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix28
  • Page weight: 8.9 MB in 355 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 355 requests on a phone: scripts 3.7 MB (132), images 3.7 MB (47) and other files 772 KiB (123). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    1.4 MB

    8 images are downloaded at several times the size a phone draws them, for example RZ93564_1.jpg at 5,000 px wide, shown at 300 px. Resized copies would save about 1.4 MB.

  • 1 image over 500 KB

    RZ93564_1.jpg weighs 827 KiB. On a phone connection a single image that size takes seconds.

  • 5 images below the first screen load straight away

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

  • About 2.5 g of CO₂ per visit

    2.52 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8992
  • Hidden but focusable

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

  • 2 text elements with low contrast

    2 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 (8 elements)

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

  • 6 links without text

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

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

SEO

5 to fixGoogle 7780
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Wholesome Sugar & Sweeteners | Fair Trade and Organic Sugar – Wholesome Sweet”.

  • 6 H1 headlines

    There are 6 <h1> headlines (“”, “ALL THE BEST FOR ALL THAT'S WHOLESOME.” and “WHOLESOME INFUSIONS ARE HERE”). One clear main headline is easier for people and search engines.

  • Meta description is long (263 characters)

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

  • 7 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 96 internal links, 16 external

    The homepage links to 96 pages on wholesomesweet.com and 16 external pages.

5 checks passed
  • Canonical URL set

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

  • llms.txt published

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

Other pages

2 to fix90
  • 9 pages without a meta description

    https://wholesomesweet.com/collections/all, https://wholesomesweet.com/policies/shipping-policy, https://wholesomesweet.com/pages/faq, https://wholesomesweet.com/pages/who-we-are, https://wholesomesweet.com/pages/mission-values and https://wholesomesweet.com/pages/history and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://wholesomesweet.com/pages/faq, https://wholesomesweet.com/pages/history and https://wholesomesweet.com/pages/all-the-best 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 43 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://px.adentifi.com/Pixels?a_id=29073;uq=663507757583.7178;p_url=https%3A%2F%2Fwholesomesweet.com%2F.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 14 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 371 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: “LEARN MORE” and “SHOP NOW”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop Products”, “Where to Buy” and “LEARN MORE”.

  • 2 short forms

    2 short forms (1 field 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
  • 8 trackers load before any consent

    8

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

  • 28 cookies set on arrival

    28

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

  • 49 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Promotion Popup Allnew · Aov Cart Drawer

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Sugar Land

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on wholesomesweet.com, including 21 speed issues, 5 SEO issues and 2 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