Website review, no card needed

thatsitfruit.com logo

thatsitfruit.com website review

Visit site (opens in a new tab)Reviewed 11 November 202632 issues · 80 checks

This review found 32 issues worth fixing on thatsitfruit.com, 8 of them high impact, across 80 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
1.7 s1.5 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20261.5 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
97 ms77 msMay 23Nov 788 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202687 ms
May 30, 202688 ms
Jun 6, 202693 ms
Jun 13, 202695 ms
Jun 20, 202693 ms
Jun 27, 202690 ms
Jul 4, 202688 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202685 ms
Aug 1, 202679 ms
Aug 8, 202680 ms
Aug 15, 202679 ms
Aug 22, 202680 ms
Aug 29, 202680 ms
Sep 5, 202680 ms
Sep 12, 202685 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202686 ms
Oct 17, 202686 ms
Oct 24, 202686 ms
Oct 31, 202686 ms
Nov 7, 202688 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 thatsitfruit.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thatsitfruit.com at 0.4 s0.4 s
  2. thatsitfruit.com at 0.8 s0.8 s
  3. thatsitfruit.com at 1.2 s1.2 s
  4. thatsitfruit.com at 1.6 s1.6 s
  5. thatsitfruit.com at 1.9 s1.9 s
  6. thatsitfruit.com at 2.3 s2.3 s
  7. thatsitfruit.com at 2.7 s2.7 s
  8. thatsitfruit.com at 3.1 s3.1 s

Speed

10 to fix54
  • Use efficient cache lifetimes

    4.7 s · 981 KiB

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

  • Reduce unused JavaScript

    3.5 s · 644 KiB

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

  • Minify JavaScript

    910 ms · 147 KiB

    147 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. 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 (rebuyengine.com, pearcommerce.com and Attentive and others), adding 2.0 MB and 676 ms of main-thread time.

  • Render-blocking requests

    550 ms

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

  • Main-thread work: 3.1 s

    A phone's processor spends 3.1 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Attentive adds 138 ms

    138 ms

    Attentive costs a phone 138 ms of main-thread work and 971 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.

  • pearcommerce.com adds 176 ms

    176 ms

    pearcommerce.com costs a phone 176 ms of main-thread work and 469 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.

  • rebuyengine.com adds 186 ms

    186 ms

    rebuyengine.com costs a phone 186 ms of main-thread work and 329 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.

  • 8 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 37 KiB

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

  • Improve image delivery

    30 KiB

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

  • Legacy JavaScript

    26 KiB

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 18.8 s

    18.8 s

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

  • Time to Interactive: 18.9 s

    18.9 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Total Blocking Time: 244 ms

    244 ms

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 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: 1.9 s

    1.9 s

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

  • Real-user INP: 73 ms

    73 ms

    Real visitors wait 73 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 FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 429 ms

    429 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.6 MB in 186 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 186 requests on a phone: scripts 1.3 MB (50), images 1.1 MB (14) and other files 794 KiB (97). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.02 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

4 to fixGoogle 10096
  • All page content should be contained by landmarks (5 elements)

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

  • 4 links without text

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

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

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

SEO

3 to fixGoogle 10084
  • Title is long (91 characters)

    Your title is 91 characters, so Google will cut it off around 60: “That's it. | Healthy fruit bars and snacks containing 100% real fruit | That's it Nutriti…”.

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

  • Structured data has 1 problem

    Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.thatsitfruit.com")”.

  • 56 internal links, 7 external

    The homepage links to 56 pages on thatsitfruit.com and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “<img src="//www.thatsitfruit.com/cdn/shop/files/Thatsit26_Apple_Month_Logo_small.jpg?v=1790816915" srcset="//www.thatsi…”.

  • Canonical URL set

    The canonical URL is https://www.thatsitfruit.com/.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.thatsitfruit.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.

  • Organization data: 5 of 6 facts

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.thatsitfruit.com/collections/shop-all-products has 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 25 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    1 page 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.

  • 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 1 page that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 16 small tap targets

    16 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix56
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • Only about 95 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 2 short forms

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 29 cookies set on arrival

    29

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

  • 29 other companies contacted

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

Apps your storefront loads

Geo Pro Geolocation · Attentive · Triplewhale · Seo Manager Venntov · Easylocation · attn.tv · rebuyengine.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

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Los Angeles

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 thatsitfruit.com, including 15 speed issues, 3 SEO issues and 6 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