pbskids.org website review

Your mobile performance score is 83 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

3 third-party services load with your homepage (Google Tag Manager, Sentry and Google Analytics), adding 499 KiB and 258 ms of main-thread time.

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

2 images could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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.

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

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Power Paige makes a Slime Storm! The Letter Ps cause chaos!…”.

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

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

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

Your title is only 8 characters: “PBS KIDS”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 11 pages on pbskids.org and 0 external pages.

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.

There is no https://pbskids.org/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://pbskids.org/grownups, https://pbskids.org/apps, https://pbskids.org/privacy and https://pbskids.org/privacy/termsofuse use the same meta description. A description written for each page earns more clicks.

https://pbskids.org/games, https://pbskids.org/videos, https://pbskids.org/videos/watch/slime-storm-invasion-of-the-party-crashers-eraser-problems/2786062, https://pbskids.org/videos/watch/outta-sun-whoa-baby-zip-zap-zoo/2786120, https://pbskids.org/videos/watch/attack-of-the-bookworm-the-perilous-pancake-picnic-space-race/2786102 and https://pbskids.org/grownups and 1 other have 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.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

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