Website review, no card needed

santacruzpaleo.com logo

santacruzpaleo.com website review

Visit site (opens in a new tab)Reviewed 7 November 202613 issues · 73 checks

This review found 13 issues worth fixing on santacruzpaleo.com, 3 of them high impact, across 73 checks. The most urgent: page weight: 6.1 MB in 313 requests. 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
861 ms732 msMay 16Oct 31795 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026826 ms
May 23, 2026825 ms
May 30, 2026836 ms
Jun 6, 2026835 ms
Jun 13, 2026827 ms
Jun 20, 2026846 ms
Jun 27, 2026826 ms
Jul 4, 2026827 ms
Jul 11, 2026836 ms
Jul 18, 2026809 ms
Jul 25, 2026809 ms
Aug 1, 2026788 ms
Aug 8, 2026790 ms
Aug 15, 2026805 ms
Aug 22, 2026796 ms
Aug 29, 2026809 ms
Sep 5, 2026800 ms
Sep 12, 2026794 ms
Sep 19, 2026798 ms
Sep 26, 2026776 ms
Oct 3, 2026764 ms
Oct 10, 2026747 ms
Oct 17, 2026752 ms
Oct 24, 2026767 ms
Oct 31, 2026795 ms
Real-visitor tap response (INP)75th percentile, phones
87 ms78 msMay 16Oct 3182 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202683 ms
May 23, 202684 ms
May 30, 202684 ms
Jun 6, 202686 ms
Jun 13, 202685 ms
Jun 20, 202684 ms
Jun 27, 202683 ms
Jul 4, 202683 ms
Jul 11, 202683 ms
Jul 18, 202683 ms
Jul 25, 202683 ms
Aug 1, 202680 ms
Aug 8, 202681 ms
Aug 15, 202681 ms
Aug 22, 202680 ms
Aug 29, 202682 ms
Sep 5, 202682 ms
Sep 12, 202684 ms
Sep 19, 202684 ms
Sep 26, 202685 ms
Oct 3, 202683 ms
Oct 10, 202680 ms
Oct 17, 202679 ms
Oct 24, 202679 ms
Oct 31, 202682 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 santacruzpaleo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. santacruzpaleo.com at 0.7 s0.7 s
  2. santacruzpaleo.com at 1.4 s1.4 s
  3. santacruzpaleo.com at 2.1 s2.1 s
  4. santacruzpaleo.com at 2.8 s2.8 s
  5. santacruzpaleo.com at 3.5 s3.5 s
  6. santacruzpaleo.com at 4.2 s4.2 s
  7. santacruzpaleo.com at 4.9 s4.9 s
  8. santacruzpaleo.com at 5.6 s5.6 s

Speed

2 to fix92
  • Render-blocking requests

    500 ms

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

  • Klaviyo adds 111 ms

    111 ms

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

  • Improve image delivery

    244 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Klaviyo, Shopify and 9gtb.com and others), adding 723 KiB and 171 ms of main-thread time.

  • Reduce unused JavaScript

    116 KiB

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

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    55 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

3 checks passed
  • Mobile performance score: 92

    92/100

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

  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 689 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

2 to fix100
  • Time to Interactive: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A surfer catching a wave off Santa Cruz at dusk”.

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

10 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.0 s

    1.0 s

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

  • Real-user INP: 111 ms

    111 ms

    Real visitors wait 111 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 377 ms

    377 ms

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

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

1 to fix70
  • Page weight: 6.1 MB in 313 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 313 requests on a phone: media 2.7 MB (2), images 1.5 MB (67) and other files 807 KiB (114). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (70 KiB) is 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.

  • About 1.7 g of CO₂ per visit

    1.72 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9798
  • 2 tap targets too small

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

2 checks passed
  • Every image has alt text

    All 100 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 10090
  • Title is short (21 characters)

    Your title is only 21 characters: “Santa Cruz Paleo Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 64 internal links, 7 external

    The homepage links to 64 pages on santacruzpaleo.com and 7 external pages.

6 checks passed
  • Meta description: 89 characters

    Your meta description is 89 characters: “Home of Santa Cruz Paleo. The best source for natural and limited ingredient supplements.”.

  • One H1 headline

    Your main headline reads: “Simple Products With Nothing Artificial”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

  • llms.txt published

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

Other pages

1 to fix95
  • 9 pages without a meta description

    https://santacruzpaleo.com/collections/all, https://santacruzpaleo.com/collections/electrolytes, https://santacruzpaleo.com/collections/protein-1, https://santacruzpaleo.com/collections/creatine, https://santacruzpaleo.com/collections/essentials and https://santacruzpaleo.com/collections/sleep and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

1 to fixGoogle 9693
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

    23 of 24 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
  • 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 347 words of copy

    The homepage carries about 347 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: “SHOP NOW” and “SHOP ALL”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop Now”, “Contact Us” and “SHOP ALL”.

  • 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: 1 testimonial or review block and 3 customer or partner logos.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies (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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 santacruzpaleo.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

Uppromote Affiliate · Klaviyo Email Marketing Sms · Affliate By Secomapp

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 13 issues on santacruzpaleo.com, including 4 speed issues, 2 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