kinderfriendly.org website review

About 486 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

The page goes through 1 redirect before it starts loading, costing about 601 ms. Link and advertise the final URL directly.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

3 third-party services load with your homepage (Google CDN, google.com and Google Fonts), adding 127 KiB and 34 ms of main-thread time.

About 10 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “michael john roberts bojack horseman”.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 226 ms to 249 ms 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.29 g of CO₂e: 34.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 6 characters: “Google”. 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.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

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

The homepage links to 8 pages on kinderfriendly.org and 2 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://www.google.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.

https://www.google.com/intl/en/policies/privacy and https://www.google.com/intl/en/policies/terms have no <title>, so Google invents the link text in results.

https://www.google.com/advanced_search, https://www.google.com/intl/en/policies/privacy and https://www.google.com/intl/en/policies/terms have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.google.com/imghp, https://www.google.com/advanced_search, https://www.google.com/intl/en/policies/privacy and https://www.google.com/intl/en/policies/terms have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.google.com/imghp, https://www.google.com/intl/en/policies/privacy and https://www.google.com/intl/en/policies/terms 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.

https://www.google.com/intl/en/about.html took over 3 s to send its HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

Large scripts ship without source maps.

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 18 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Opening the homepage sets 4 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.