Website review, no card needed

tinysaints.com logo

tinysaints.com website review

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

This review found 19 issues worth fixing on tinysaints.com, 4 of them high impact, across 73 checks. The most urgent: 3,550 HTML elements. 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 s710 msMay 16Oct 31873 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026983 ms
May 23, 2026939 ms
May 30, 2026868 ms
Jun 6, 2026844 ms
Jun 13, 2026848 ms
Jun 20, 2026878 ms
Jun 27, 20261.0 s
Jul 4, 2026958 ms
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 2026988 ms
Aug 1, 20261.0 s
Aug 8, 2026949 ms
Aug 15, 2026923 ms
Aug 22, 2026833 ms
Aug 29, 2026789 ms
Sep 5, 2026772 ms
Sep 12, 2026765 ms
Sep 19, 2026750 ms
Sep 26, 2026777 ms
Oct 3, 2026782 ms
Oct 10, 2026786 ms
Oct 17, 2026889 ms
Oct 24, 2026841 ms
Oct 31, 2026873 ms
Real-visitor tap response (INP)75th percentile, phones
121 ms67 msMay 16Oct 3179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202693 ms
May 23, 202693 ms
May 30, 202694 ms
Jun 6, 202696 ms
Jun 13, 202696 ms
Jun 20, 2026103 ms
Jun 27, 2026111 ms
Jul 4, 2026112 ms
Jul 11, 2026115 ms
Jul 18, 2026115 ms
Jul 25, 2026113 ms
Aug 1, 2026107 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 202695 ms
Aug 29, 202687 ms
Sep 5, 202684 ms
Sep 12, 202679 ms
Sep 19, 202677 ms
Sep 26, 202677 ms
Oct 3, 202675 ms
Oct 10, 202673 ms
Oct 17, 202677 ms
Oct 24, 202678 ms
Oct 31, 202679 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 tinysaints.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tinysaints.com at 0.4 s0.4 s
  2. tinysaints.com at 0.8 s0.8 s
  3. tinysaints.com at 1.1 s1.1 s
  4. tinysaints.com at 1.5 s1.5 s
  5. tinysaints.com at 1.9 s1.9 s
  6. tinysaints.com at 2.3 s2.3 s
  7. tinysaints.com at 2.6 s2.6 s
  8. tinysaints.com at 3.0 s3.0 s

Speed

4 to fix87
  • 3,550 HTML elements

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

  • Mobile performance score: 87

    87/100

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

  • Improve image delivery

    500 ms · 103 KiB

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

  • Render-blocking requests

    450 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and Hubspot and others), adding 531 KiB and 287 ms of main-thread time.

  • Use efficient cache lifetimes

    128 KiB

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

  • Reduce unused JavaScript

    79 KiB

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    38 KiB

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

  • Duplicated JavaScript

    13 KiB

    13 KiB JavaScript is shipped twice across bundles.

  • Reduce unused CSS

    10 KiB

    About 10 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 721 ms of it running JavaScript. That is comfortably low.

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 8.2 s

    8.2 s

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

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

  • Cumulative Layout Shift: 0.103

    0.103

    The layout shifts by 0.103 while loading, so content jumps under the reader's thumb. Good is under 0.1.

11 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.3 s

    1.3 s

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

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 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: 1.0 s

    1.0 s

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

  • Real-user TTFB: 615 ms

    615 ms

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

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

  • Speed Index: 1.9 s

    1.9 s

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

  • Total Blocking Time: 11 ms

    11 ms

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    TSS101-thumb01a.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.51 g

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

3 checks passed
  • Page weight: 1.8 MB in 222 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 222 requests on a phone: other files 775 KiB (99), scripts 602 KiB (71) and images 298 KiB (21). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9698
  • 16 text elements with low contrast

    16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • Title is short (12 characters)

    Your title is only 12 characters: “Tiny Saints®”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (42 characters)

    Your meta description is only 42 characters: “Pretty much the coolest saint charms ever!”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 127 internal links, 2 external

    The homepage links to 127 pages on tinysaints.com and 2 external pages.

5 checks passed
  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

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

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://www.tinysaints.com/collections/charms, https://www.tinysaints.com/collections/stationery, https://www.tinysaints.com/collections/sidekicks and https://www.tinysaints.com/collections/board-books have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.tinysaints.com/collections/sidekicks has 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 55 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

Best practices

1 to fixGoogle 9693
  • 10 small tap targets

    10 of 26 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

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 595 words of visible text.

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Contact” and “Board Book - "I Am Little, Too"”.

  • 37 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 1 more (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.

  • 15 cookies set on arrival

    15

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

  • 26 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Freegifts · bogos.io · amazonaws.com · retention.com · hubapi.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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Winter Garden

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on tinysaints.com, including 7 speed issues, 3 SEO issues and 3 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