Website review, no card needed

spicefruit.com logo

spicefruit.com website review

Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 68 checks

This review found 32 issues worth fixing on spicefruit.com, 10 of them high impact, across 68 checks. The most urgent: use efficient cache lifetimes. 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.6 s1.8 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.2 s
Aug 29, 20262.1 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.2 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
188 ms119 msMay 16Oct 31180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026127 ms
May 23, 2026127 ms
May 30, 2026128 ms
Jun 6, 2026129 ms
Jun 13, 2026133 ms
Jun 20, 2026132 ms
Jun 27, 2026135 ms
Jul 4, 2026132 ms
Jul 11, 2026133 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026131 ms
Aug 8, 2026136 ms
Aug 15, 2026138 ms
Aug 22, 2026138 ms
Aug 29, 2026138 ms
Sep 5, 2026144 ms
Sep 12, 2026152 ms
Sep 19, 2026162 ms
Sep 26, 2026171 ms
Oct 3, 2026177 ms
Oct 10, 2026179 ms
Oct 17, 2026179 ms
Oct 24, 2026178 ms
Oct 31, 2026180 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 spicefruit.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. spicefruit.com at 0.7 s0.7 s
  2. spicefruit.com at 1.5 s1.5 s
  3. spicefruit.com at 2.2 s2.2 s
  4. spicefruit.com at 2.9 s2.9 s
  5. spicefruit.com at 3.7 s3.7 s
  6. spicefruit.com at 4.4 s4.4 s
  7. spicefruit.com at 5.2 s5.2 s
  8. spicefruit.com at 5.9 s5.9 s

Speed

10 to fix60
  • Use efficient cache lifetimes

    1.8 s · 877 KiB

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

  • Render-blocking requests

    1.4 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Main-thread work: 7.0 s

    A phone's processor spends 7.0 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 (alia-prod.com, transcend-cdn.com and Klaviyo and others), adding 2.4 MB and 1.2 s of main-thread time.

  • Mobile performance score: 60

    60/100

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

  • Reduce unused JavaScript

    60 ms · 526 KiB

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

  • Improve image delivery

    300 ms · 160 KiB

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

  • alia-prod.com adds 315 ms

    315 ms

    alia-prod.com costs a phone 315 ms of main-thread work and 1,002 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.

  • 2,490 HTML elements

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

  • Klaviyo adds 195 ms

    195 ms

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

  • 13 long tasks on the main thread

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

  • Reduce unused CSS

    60 ms · 49 KiB

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

  • Legacy JavaScript

    48 KiB

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

  • Minify CSS

    14 KiB

    14 KiB could be saved by minifying CSS.

  • Duplicated JavaScript

    10 KiB

    10 KiB JavaScript is shipped twice across bundles.

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

    16 ms

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

Core Web Vitals

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

  • Time to Interactive: 25.2 s

    25.2 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Spicefruit GloSlim + StressAdapt”.

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

    +41%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Total Blocking Time: 299 ms

    299 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 4 images without width and height

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

  • 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 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 180 ms

    180 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 707 ms

    707 ms

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

  • Cumulative Layout Shift: 0.022

    0.022

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

Images and page weight

1 to fix0
  • Page weight: 4.8 MB in 444 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 444 requests on a phone: scripts 2.0 MB (147), images 1.1 MB (34) and other files 1.0 MB (185). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.37 g

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

Accessibility

2 to fix97
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

SEO

4 to fixGoogle 10079
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Spicefruit GloSlim + StressAdapt Weight Loss Supplement - Naomi Whittel – NaomiW”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“GloSlim + StressAdapt” and “GloSlim + StressAdapt”). One clear main headline is easier for people and search engines.

  • Meta description is long (210 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, FAQPage, Organization and ProductGroup) but with 1 problem, for example “ProductGroup: url is not an absolute URL ("https://naomiw.com/products/gloslim-spicefruit")”.

  • 83 internal links, 20 external

    The homepage links to 83 pages on spicefruit.com and 20 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://naomiw.com/products/gloslim-spicefruit.

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

AI search readiness

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • llms.txt published

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

Other pages

4 to fix79
  • 1 page points its canonical at the homepage

    https://naomiw.com/discount/BOOST25 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 6 pages without a meta description

    https://naomiw.com/pages/our-story, https://naomiw.com/pages/naomi-tv, https://naomiw.com/blogs/articles, https://naomiw.com/blogs/nutrition, https://naomiw.com/blogs/health and https://naomiw.com/blogs/recipes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://naomiw.com/discount/BOOST25 and https://naomiw.com/collections use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://naomiw.com/collections, https://naomiw.com/pages/our-story, https://naomiw.com/pages/press-media and https://naomiw.com/pages/naomi-tv 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 32 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

1 to fixGoogle 9693
  • 6 console errors

    6 errors were logged to the browser console during Google's test (“Access to script at 'https://cdn.intelligems.io/esm/d053af918c61/bundle.js' from origin 'https://na…”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 2,808 words of copy

    The homepage carries about 2,808 words of visible text.

  • Urgency cues

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

5 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “SHOP ALL”, “Subscribe & Save” and “Shop”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 174 testimonial or review blocks, 3 customer or partner logos, a star rating, 1 trust badge and “over 600,000+ Customers”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on 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 spicefruit.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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

Company

Headquarters
Gainesville

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on spicefruit.com, including 19 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