Website review, no card needed
childrensplace.com website review
Visit site (opens in a new tab)Reviewed 11 October 202650 issues · 101 checks
This review found 50 issues worth fixing on childrensplace.com, 19 of them high impact, across 101 checks. The most urgent: theplace.com adds 3.5 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.9 s |
| Apr 25, 2026 | 1.9 s |
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 400 ms |
| Apr 25, 2026 | 406 ms |
| May 2, 2026 | 414 ms |
| May 9, 2026 | 421 ms |
| May 16, 2026 | 420 ms |
| May 23, 2026 | 426 ms |
| May 30, 2026 | 433 ms |
| Jun 6, 2026 | 437 ms |
| Jun 13, 2026 | 453 ms |
| Jun 20, 2026 | 463 ms |
| Jun 27, 2026 | 478 ms |
| Jul 4, 2026 | 508 ms |
| Jul 11, 2026 | 530 ms |
| Jul 18, 2026 | 560 ms |
| Jul 25, 2026 | 578 ms |
| Aug 1, 2026 | 588 ms |
| Aug 8, 2026 | 597 ms |
| Aug 15, 2026 | 588 ms |
| Aug 22, 2026 | 572 ms |
| Aug 29, 2026 | 554 ms |
| Sep 5, 2026 | 529 ms |
| Sep 12, 2026 | 512 ms |
| Sep 19, 2026 | 494 ms |
| Sep 26, 2026 | 480 ms |
| Oct 3, 2026 | 475 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
How it loaded on a phone
2.0 s
4.1 s
6.1 s
8.2 s
10.2 s
12.3 s
14.3 s
16.4 s
Speed
theplace.com adds 3.5 s
3.5 stheplace.com costs a phone 3.5 s of main-thread work and 8.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 16.3 s
A phone's processor spends 16.3 s on main-thread work while loading, 10.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 100). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (theplace.com, Google Tag Manager and Quantum Metric and others), adding 11.0 MB and 5.4 s of main-thread time.
Reduce unused JavaScript
150 ms · 4.0 MBAbout 4.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.9 s. During a long task the page ignores taps.
Improve image delivery
650 ms · 688 KiB10 images could be 688 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Use efficient cache lifetimes
1.2 MB76 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Google Tag Manager adds 621 ms
621 msGoogle Tag Manager costs a phone 621 ms of main-thread work and 855 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.
Quantum Metric adds 355 ms
355 msQuantum Metric costs a phone 355 ms of main-thread work and 107 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.
Wunderkind adds 258 ms
258 msWunderkind costs a phone 258 ms of main-thread work and 783 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.
Adobe Tag Manager adds 261 ms
261 msAdobe Tag Manager costs a phone 261 ms of main-thread work and 174 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.
1,946 HTML elements
The page has 1,946 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
128 KiBPolyfills for old browsers add 128 KiB JavaScript that modern phones do not need.
Reduce unused CSS
124 KiBAbout 124 KiB of CSS is downloaded but never applied on this page.
Minify CSS
16 KiB16 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 100 but mobile only 26. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 186 ms
186 msYour server sent the HTML in 186 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user INP: 586 ms
586 msReal visitors wait 586 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.62
0.62For real visitors the layout shifts by 0.62 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three children wearing winter outerwear stand together in t…”.
Speed Index: 27.7 s
27.7 sVisually, the page fills in at 27.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 65.1 s
65.1 sThe page becomes fully interactive after 65.1 s. Good is under 3.8 s.
Total Blocking Time: 4.0 s
4.0 sScripts block taps and scrolling for 4.0 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Real-user TTFB: 929 ms
929 msReal visitors wait 929 ms for your server to start answering (75th percentile). Good is under 800 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 400 ms to 475 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-10-03, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 13.0 MB in 567 requests
13.0 MBYour homepage downloads 13.0 MB in 567 requests on a phone: scripts 6.1 MB (233), images 3.0 MB (110) and media 1.7 MB (1). Under 2 MB keeps phones on slow connections fast.
9 images below the first screen load straight away
9 images further down the page (778 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
40 KiB3 images are downloaded at several times the size a phone draws them, for example PJS_MB.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 40 KiB.
About 3.7 g of CO₂ per visit
3.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.67 g of CO₂e: 440.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Links must have discernible text (6 elements)
Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 31 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
105 internal links, 6 external
The homepage links to 105 pages on childrensplace.com and 6 external pages.
8 checks passed
Meta description: 113 characters
Your meta description is 113 characters: “Browse our comfortable baby & kids clothes collection featuring all our stylish and affordable options. Shop now!”.
One H1 headline
Your main headline reads: “Boys & Girls Clothes”.
Title: 51 characters
Your title is a healthy 51 characters: “Kids, Baby & Toddler Clothes | The Children's Place”.
Canonical URL set
The canonical URL is https://www.childrensplace.com/us/home.
Structured data in place
Structured data found: Organization, SiteNavigationElement 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.childrensplace.com/tcp_us_en_sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (880 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.childrensplace.com/llms.txt (132 KiB, 30 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.childrensplace.com/us/c/featured-pajama-pants-deal has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.childrensplace.com/us/c/featured-pajama-pants-deal is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.childrensplace.com/us/c/featured-pajama-pants-deal has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.childrensplace.com/us/c/gift-guide and https://www.childrensplace.com/us/c/featured-pajama-pants-deal have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.childrensplace.com/us/c/gift-guide 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.
5 pages slow to respond
https://www.childrensplace.com/us/c/childrens-shoes-kids-shoes, https://www.childrensplace.com/us/c/deals, https://www.childrensplace.com/us/c/featured-pajama-pants-deal, https://www.childrensplace.com/us/c/puffer-palooza and https://www.childrensplace.com/us/c/kids-school-uniform-shop took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
Best practices
12 small tap targets
12 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are 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 “Unexpected token '<'”.
14 distorted images
14 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 550 words of copy
The homepage carries about 550 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP GIRL” and “SHOP BOY”.
21 calls to action
The homepage has 21 calls to action, for example “Cold Weather Shop”, “Character Shop” and “Game Day Shop”.
1 short form
A short form (2 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Microsoft Ads and Pinterest Tag (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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
20 other companies contacted
Loading the homepage contacts 20 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 childrensplace.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on childrensplace.com, including 23 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.