20k.org website review

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

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

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

7 third-party services load with your homepage (Squarespace, jQuery CDN and sqspcdn.com and others), adding 2.4 MB and 649 ms of main-thread time.

Squarespace costs a phone 598 ms of main-thread work and 1.5 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.

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

About 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 601 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.

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

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

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

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

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

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

Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our show is an upbeat, inclusive celebration of the world o…”.

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 2.6 MB in 114 requests on a phone: scripts 1.1 MB (55), images 798 KiB (25) and fonts 441 KiB (14). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (114 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is 96 characters, so Google will cut it off around 60: “Twenty Thousand Hertz - The stories behind the world's most recognizable and interesting …”.

There are 9 <h1> headlines (“”, “The stories behind the world’s most recognizable …” and “Welcome to Twenty Thousand Hertz!”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/580fbaac440243d8731…”.

The homepage links to 35 pages on 20k.org and 31 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.20k.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.

https://www.20k.org/episodes-archive, https://www.20k.org/about, https://www.20k.org/newsletter, https://www.20k.org/episodes/netflix and https://www.20k.org/episodes/spaceaudity have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.20k.org/sponsors 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.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/580fbaac440243d8731ffc57/835/52e96934e4b0ea…”.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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 shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 335 words of visible text.

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