Website review, no card needed

thekiddospacestore.com logo

thekiddospacestore.com website review

Visit site (opens in a new tab)Reviewed 10 November 202640 issues · 87 checks

This review found 40 issues worth fixing on thekiddospacestore.com, 14 of them high impact, across 87 checks. The most urgent: render-blocking 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
3.3 s2.2 sMay 23Nov 72.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.9 s
May 30, 20262.7 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.5 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.8 s
Oct 3, 20263.1 s
Oct 10, 20263.2 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Oct 31, 20262.9 s
Nov 7, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
142 ms122 msMay 23Nov 7137 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026133 ms
May 30, 2026135 ms
Jun 6, 2026136 ms
Jun 13, 2026137 ms
Jun 20, 2026138 ms
Jun 27, 2026140 ms
Jul 4, 2026139 ms
Jul 11, 2026138 ms
Jul 18, 2026133 ms
Jul 25, 2026129 ms
Aug 1, 2026130 ms
Aug 8, 2026130 ms
Aug 15, 2026133 ms
Aug 22, 2026131 ms
Aug 29, 2026129 ms
Sep 5, 2026128 ms
Sep 12, 2026124 ms
Sep 19, 2026128 ms
Sep 26, 2026127 ms
Oct 3, 2026129 ms
Oct 10, 2026129 ms
Oct 17, 2026129 ms
Oct 24, 2026129 ms
Oct 31, 2026135 ms
Nov 7, 2026137 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 thekiddospacestore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix43
  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.8 s

    A phone's processor spends 4.8 s on main-thread work while loading, 2.6 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 (Stripe, Clarity and 506.io and others), adding 721 KiB and 1.2 s of main-thread time.

  • Use efficient cache lifetimes

    450 ms · 452 KiB

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

  • Stripe adds 516 ms

    516 ms

    Stripe costs a phone 516 ms of main-thread work and 304 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 JavaScript

    150 ms · 310 KiB

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

  • 18 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 20 KiB

    About 20 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.

  • Legacy JavaScript

    22 KiB

    Polyfills for old browsers add 22 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: 14 ms

    14 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 7.2 s

    7.2 s

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

  • Time to Interactive: 13.6 s

    13.6 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

5 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: 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 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.3 s

    1.3 s

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

  • 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: 2.5 MB in 169 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 169 requests on a phone: scripts 1.4 MB (61), other files 791 KiB (94) and fonts 147 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.71 g

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

8 to fixGoogle 7788
  • <svg> elements with an img or image role must have alternative text (4 elements)

    <svg> elements with an img or image role must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.

  • 3 text elements with low contrast

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

  • 3 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • All page content should be contained by landmarks (11 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 2 links without text

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

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

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 8389
  • No structured data

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • One H1 headline

    Your <h1> is empty.

  • 48 internal links, 19 external

    The homepage links to 48 pages on thekiddospacestore.com and 19 external pages.

6 checks passed
  • Meta description: 112 characters

    Your meta description is 112 characters: “TheKiddoSpace was founded with a very specific goal in mind: No more losing your child's clothes and belongings.”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “TheKiddoSpace US | Name Stamps for Clothes, Organizers & Toys”.

  • Canonical URL set

    The canonical URL is https://thekiddospacestore.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://thekiddospacestore.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 (631 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

7 to fix50
  • 1 page without a title

    https://thekiddospacestore.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 3 pages point its canonical at the homepage

    https://thekiddospacestore.com/products/kiddostamp-2-0-complete-stamping-set, https://thekiddospacestore.com/products/kiddospace-splash-pad and https://thekiddospacestore.com/products/kiddospace-reusable-water-sponge-ball declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 2 linked pages hidden from search

    https://thekiddospacestore.com/customer_authentication/redirect and https://thekiddospacestore.com/products/kiddospace%E2%84%A2-steel-tongue-drum are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a title

    /, https://thekiddospacestore.com/products/kiddostamp-2-0-complete-stamping-set, https://thekiddospacestore.com/products/kiddospace-splash-pad and https://thekiddospacestore.com/products/kiddospace-reusable-water-sponge-ball all use the title “TheKiddoSpace US | Name Stamps for Clothes, Organizers & Toys”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://thekiddospacestore.com/collections/our-bestseller, https://thekiddospacestore.com/collections/stamping-kits, https://thekiddospacestore.com/collections/educational, https://thekiddospacestore.com/pages/faqs, https://thekiddospacestore.com/pages/our-happy-customers and https://thekiddospacestore.com/customer_authentication/redirect and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://thekiddospacestore.com/products/kiddostamp-2-0-complete-stamping-set, https://thekiddospacestore.com/products/kiddospace-splash-pad and https://thekiddospacestore.com/products/kiddospace-reusable-water-sponge-ball use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://thekiddospacestore.com/pages/faqs and https://thekiddospacestore.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://thekiddospacestore.com/customer_authentication/redirect and https://thekiddospacestore.com/products/kiddospace%E2%84%A2-steel-tongue-drum took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 8885
  • 8 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'includes') https://thekiddospacestore.com/:19:555 NodeList.forEach (<anonymous…”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

  • About 374 words of copy

    The homepage carries about 374 words of visible text.

  • Urgency cues

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

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact us”, “Buy Toys and Education” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating and “Join 200K+ satisfied customers”.

  • Analytics in place

    Analytics detected: Google Analytics, Microsoft Clarity and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Microsoft Clarity (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.

  • 13 cookies set on arrival

    13

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 thekiddospacestore.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

Pagefly Ai Page Builder · Triplewhale · Cartix · Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Eg Auto Add To Cart · Applovin Shop Integration · loox.io · snapchat.com · creativecdn.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
Analytics
Google Analytics | Hotjar | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on thekiddospacestore.com, including 13 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