Website review, no card needed

tootiepieco.com logo

tootiepieco.com website review

Visit site (opens in a new tab)Reviewed 5 November 202635 issues · 79 checks

This review found 35 issues worth fixing on tootiepieco.com, 11 of them high impact, across 79 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.1 s898 msJun 20Oct 31972 ms
Show as table
DateReal-visitor load time (LCP)
Jun 20, 20261.1 s
Oct 10, 2026957 ms
Oct 17, 2026957 ms
Oct 24, 2026920 ms
Oct 31, 2026972 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 tootiepieco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tootiepieco.com at 1.0 s1.0 s
  2. tootiepieco.com at 1.9 s1.9 s
  3. tootiepieco.com at 2.9 s2.9 s
  4. tootiepieco.com at 3.8 s3.8 s
  5. tootiepieco.com at 4.8 s4.8 s
  6. tootiepieco.com at 5.7 s5.7 s
  7. tootiepieco.com at 6.7 s6.7 s
  8. tootiepieco.com at 7.7 s7.7 s

Speed

12 to fix55
  • Reduce unused JavaScript

    3.8 s · 705 KiB

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

  • Main-thread work: 4.1 s

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

  • Improve image delivery

    350 ms · 2.5 MB

    4 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (chatra.io, Klaviyo and Shopify and others), adding 2.4 MB and 970 ms of main-thread time.

  • Mobile performance score: 55

    55/100

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

  • Render-blocking requests

    450 ms

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

  • Use efficient cache lifetimes

    350 ms · 67 KiB

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

  • chatra.io adds 381 ms

    381 ms

    chatra.io costs a phone 381 ms of main-thread work and 336 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.

  • Reduce unused CSS

    300 ms · 56 KiB

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

  • Legacy JavaScript

    300 ms · 29 KiB

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

  • Klaviyo adds 260 ms

    260 ms

    Klaviyo costs a phone 260 ms of main-thread work and 385 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 145 ms

    145 ms

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

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • 9 long tasks on the main thread

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

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

    5 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 23.3 s

    23.3 s

    Your largest element takes 23.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a group of plates of pastries”.

  • First Contentful Paint: 7.0 s

    7.0 s

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

  • Time to Interactive: 23.7 s

    23.7 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

8 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: 0.9 s

    0.9 s

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

  • Real-user INP: 97 ms

    97 ms

    Real visitors wait 97 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.6 s

    0.6 s

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

  • Real-user TTFB: 283 ms

    283 ms

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

  • Total Blocking Time: 148 ms

    148 ms

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix70
  • Page weight: 7.0 MB in 473 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 473 requests on a phone: images 2.9 MB (10), other files 2.0 MB (325) and scripts 1.7 MB (109). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    1.97 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.97 g of CO₂e: 236.7 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

5 to fixGoogle 8993
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

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

  • Frames without titles

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 10089
  • Title is short (14 characters)

    Your title is only 14 characters: “Tootie Pie Co.”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 49 internal links, 10 external

    The homepage links to 49 pages on tootiepieco.com and 10 external pages.

6 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “Texas Hill Country Bakery - Handcrafted sweets and savory eats made with quality ingredients and tender loving care.”.

  • One H1 headline

    Your main headline reads: “Tootie Pie Co”.

  • Canonical URL set

    The canonical URL is https://www.tootiepieco.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.tootiepieco.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (199 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix85
  • 7 pages without a meta description

    https://www.tootiepieco.com/collections/thanksgiving-collection, https://www.tootiepieco.com/collections/pie, https://www.tootiepieco.com/pages/business-gifts, https://www.tootiepieco.com/pages/pie-perks, https://www.tootiepieco.com/blogs/news and https://www.tootiepieco.com/collections/fruit-butter and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.tootiepieco.com/products/build-your-own-empienada%E2%84%A2, whose canonical is https://www.tootiepieco.com/products/build-your-own-empienada%e2%84%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://www.tootiepieco.com/collections/thanksgiving-collection, https://www.tootiepieco.com/collections/pie, https://www.tootiepieco.com/collections/snackables, https://www.tootiepieco.com/pages/contact-us, https://www.tootiepieco.com/collections/fruit-butter and https://www.tootiepieco.com/collections/all-products-except-route have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.tootiepieco.com/collections has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'start')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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 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 233 words

    The homepage has only about 233 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BUY NOW”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop All”, “Buy Now” and “Order for shipping”.

  • 2 short forms

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, 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.

  • 12 cookies set on arrival

    12

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

  • 27 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Loyalty Rewards And Referrals · Chatra Live Chat Chatbot · Giftship · Zapiet Pickup Delivery · Simple Bundle · Accessibly App · Forms · Navidium Shipping Protection · rechargecdn.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
jQuery
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Dripping Springs

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on tootiepieco.com, including 16 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