Website review, no card needed

charlieplay.com logo

charlieplay.com website review

Visit site (opens in a new tab)Reviewed 4 November 202630 issues · 79 checks

This review found 30 issues worth fixing on charlieplay.com, 7 of them high impact, across 79 checks. The most urgent: 6,335 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.0 s757 msMay 16Oct 31785 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026924 ms
May 23, 2026889 ms
May 30, 2026884 ms
Jun 6, 2026892 ms
Jun 13, 2026918 ms
Jun 20, 2026953 ms
Jun 27, 2026972 ms
Jul 4, 2026882 ms
Jul 11, 2026871 ms
Jul 18, 2026870 ms
Jul 25, 2026858 ms
Aug 1, 2026896 ms
Aug 8, 2026893 ms
Aug 15, 2026872 ms
Aug 22, 2026865 ms
Aug 29, 2026866 ms
Sep 5, 2026883 ms
Sep 12, 2026912 ms
Sep 19, 2026940 ms
Sep 26, 2026938 ms
Oct 3, 2026888 ms
Oct 10, 2026872 ms
Oct 17, 2026856 ms
Oct 24, 2026831 ms
Oct 31, 2026785 ms
Real-visitor tap response (INP)75th percentile, phones
98 ms82 msMay 16Oct 3188 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202685 ms
May 23, 202684 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202690 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202692 ms
Jul 11, 202689 ms
Jul 18, 202689 ms
Jul 25, 202689 ms
Aug 1, 202691 ms
Aug 8, 202692 ms
Aug 15, 202689 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202692 ms
Oct 3, 202695 ms
Oct 10, 202696 ms
Oct 17, 202696 ms
Oct 24, 202695 ms
Oct 31, 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 charlieplay.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix78
  • 6,335 HTML elements

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

  • Improve image delivery

    700 ms · 1.7 MB

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

  • Mobile performance score: 78

    78/100

    Your mobile performance score is 78. 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 (rise-ai.com, rebuyengine.com and Klaviyo and others), adding 1.7 MB and 508 ms of main-thread time.

  • Render-blocking requests

    600 ms

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

  • Use efficient cache lifetimes

    432 KiB

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

  • Reduce unused JavaScript

    335 KiB

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

  • Main-thread work: 3.2 s

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

  • rise-ai.com adds 178 ms

    178 ms

    rise-ai.com costs a phone 178 ms of main-thread work and 789 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 169 ms

    169 ms

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

    33 ms

    Shopify costs a phone 33 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

    150 ms · 158 KiB

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    68 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

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

3 to fix100
  • Time to Interactive: 19.6 s

    19.6 s

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

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

  • Total Blocking Time: 371 ms

    371 ms

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

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 85 ms to 88 ms 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.8 s

    1.8 s

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

  • Real-user INP: 79 ms

    79 ms

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

    1.6 s

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

  • Real-user TTFB: 571 ms

    571 ms

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

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

  • Speed Index: 3.3 s

    3.3 s

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

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix33
  • Page weight: 6.0 MB in 293 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 293 requests on a phone: images 3.0 MB (54), scripts 1.4 MB (101) and other files 1.1 MB (115). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.69 g

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

Accessibility

5 to fixGoogle 9287
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

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

  • 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 476 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

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

SEO

3 to fixGoogle 10091
  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • One H1 headline

    Your <h1> is empty.

  • 561 internal links, 12 external

    The homepage links to 561 pages on charlieplay.com and 12 external pages.

6 checks passed
  • Meta description: 77 characters

    Your meta description is 77 characters: “The softest clothing for the family. Natural bamboo & luxurious soft fabrics.”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Charlie's Project Kids Clothing – Charlies Project Kids”.

  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

    There is no https://charlieplay.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: 4 of 6 facts

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://charlieplay.com/collections/new-arrivals 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 197 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

2 to fixGoogle 7389
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 analytics detected

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

  • Only about 10 words

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

2 checks passed
  • 154 calls to action

    The homepage has 154 calls to action, for example “SHOP”, “Pre Order Sept/Oct Status” and “Contact us”.

  • 5 short forms

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

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 charlieplay.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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Oxi Social Login Wishlist · Ecomsend Restock · Restockrocket · rise-ai.com · klaviyo.com · trafficmanager.net · postscript.io · 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

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 30 issues on charlieplay.com, including 14 speed issues, 3 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