Website review, no card needed

potterybarnkids.com logo

potterybarnkids.com website review

Visit site (opens in a new tab)Reviewed 12 October 202650 issues · 85 checks

This review found 50 issues worth fixing on potterybarnkids.com, 19 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
2.6 s2.2 sApr 18Oct 32.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.3 s
Apr 25, 20262.3 s
May 2, 20262.4 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 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.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
543 ms218 msApr 18Oct 3495 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026255 ms
Apr 25, 2026270 ms
May 2, 2026274 ms
May 9, 2026274 ms
May 16, 2026275 ms
May 23, 2026277 ms
May 30, 2026279 ms
Jun 6, 2026287 ms
Jun 13, 2026292 ms
Jun 20, 2026296 ms
Jun 27, 2026341 ms
Jul 4, 2026394 ms
Jul 11, 2026437 ms
Jul 18, 2026469 ms
Jul 25, 2026464 ms
Aug 1, 2026462 ms
Aug 8, 2026461 ms
Aug 15, 2026465 ms
Aug 22, 2026473 ms
Aug 29, 2026482 ms
Sep 5, 2026493 ms
Sep 12, 2026497 ms
Sep 19, 2026505 ms
Sep 26, 2026505 ms
Oct 3, 2026495 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 potterybarnkids.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. potterybarnkids.com at 2.0 s2.0 s
  2. potterybarnkids.com at 3.9 s3.9 s
  3. potterybarnkids.com at 5.9 s5.9 s
  4. potterybarnkids.com at 7.8 s7.8 s
  5. potterybarnkids.com at 9.8 s9.8 s
  6. potterybarnkids.com at 11.7 s11.7 s
  7. potterybarnkids.com at 13.7 s13.7 s
  8. potterybarnkids.com at 15.6 s15.6 s

Speed

15 to fix13
  • Use efficient cache lifetimes

    1.9 s · 1.7 MB

    50 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

  • Render-blocking requests

    3.5 s

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

  • Reduce unused CSS

    1.5 s · 401 KiB

    About 401 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Main-thread work: 15.0 s

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

  • Mobile performance score: 13

    13/100

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

  • 3,189 HTML elements

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

  • Reduce unused JavaScript

    920 ms · 3.2 MB

    About 3.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 920 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, site.com and Tealium and others), adding 3.3 MB and 2.0 s of main-thread time.

  • Improve image delivery

    750 ms · 437 KiB

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

  • Google Tag Manager adds 688 ms

    688 ms

    Google Tag Manager costs a phone 688 ms of main-thread work and 814 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.

  • 20 long tasks on the main thread

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

  • site.com adds 361 ms

    361 ms

    site.com costs a phone 361 ms of main-thread work and 1.4 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.

  • Facebook adds 253 ms

    253 ms

    Facebook costs a phone 253 ms of main-thread work and 306 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.

  • Tealium adds 257 ms

    257 ms

    Tealium costs a phone 257 ms of main-thread work and 176 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.

  • Evergage adds 100 ms

    100 ms

    Evergage costs a phone 100 ms of main-thread work and 319 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.

  • Legacy JavaScript

    200 ms · 170 KiB

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

  • Forced reflow

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 136 ms

    136 ms

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

Core Web Vitals

11 to fix0
  • 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.

  • Largest Contentful Paint: 16.5 s

    16.5 s

    Your largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hello, Halloween - Shop up to 40% off”.

  • Speed Index: 17.9 s

    17.9 s

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

  • Time to Interactive: 66.2 s

    66.2 s

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

  • Total Blocking Time: 3.8 s

    3.8 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Cumulative Layout Shift: 0.286

    0.286

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 313 ms

    313 ms

    Real visitors wait 313 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.12

    0.12

    For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 90% slower for real visitors

    +90%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

2 checks passed
  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 796 ms

    796 ms

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

Images and page weight

2 to fix64
  • Page weight: 12.5 MB in 286 requests

    12.5 MB

    Your homepage downloads 12.5 MB in 286 requests on a phone: scripts 6.6 MB (81), images 2.9 MB (83) and other files 1.9 MB (97). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    010.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).

  • 3 images in older formats

    3 images (220 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 3.5 g of CO₂ per visit

    3.53 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8691
  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (14 elements)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 14 elements on the page fail this check, rated serious by axe-core.

  • 2 tap targets too small

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

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

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

  • 11 links without text

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

  • Alternative text of images should not be repeated as text (10 elements)

    Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

7 to fixGoogle 7769
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Kids’ & Baby Furniture, Kids Bedding & Gifts | Baby Registry | Pottery Barn Kids”.

  • No structured data

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

  • 29 links crawlers can't follow

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

  • Meta description is long (184 characters)

    Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 162 internal links, 27 external

    The homepage links to 162 pages on potterybarnkids.com and 27 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.potterybarnkids.com/.

  • 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.potterybarnkids.com/netstorage/sitemaps/ecm-sitemap-index.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 (576 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

4 to fixGoogle 5483
  • 43 small tap targets

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 666 words of copy

    The homepage carries about 666 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “contact us” and “SIGN UP NOW”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Track Order”, “Track Your Order” and “Get Started”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 51 cookies set on arrival

    51

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

  • 39 other companies contacted

    Loading the homepage contacts 39 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 potterybarnkids.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 potterybarnkids.com, including 26 speed issues, 7 SEO issues and 2 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