supertalk.fm website review

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

9 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.

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

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

7 third-party services load with your homepage (themediacdn.com, Google/Doubleclick Ads and adtrafficquality.google and others), adding 1.1 MB and 597 ms of main-thread time.

themediacdn.com costs a phone 356 ms of main-thread work and 534 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.

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

Google/Doubleclick Ads costs a phone 211 ms of main-thread work and 293 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.

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

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

15 KiB could be saved by minifying JavaScript.

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

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.

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.

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

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

Your largest element takes 33.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SuperTalk Mississippi”.

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

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

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

Your homepage downloads 8.1 MB in 88 requests on a phone: images 6.9 MB (38), scripts 859 KiB (27) and fonts 271 KiB (6). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

24 images (4.3 MB) 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.

17 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

11 images are downloaded at several times the size a phone draws them, for example Horhn2use-768x432.png at 390 px wide, shown at 100 px. Resized copies would save about 452 KiB.

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

1 text element doesn'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.

All page content should be contained by landmarks: 5 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

Structured data found (Article, ImageObject, ItemList and Organization) but with 1 problem, for example “Organization: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.supertalk.fm/sitemap_index.xml, so Google discovers your pages only by following links.

The homepage links to 366 pages on supertalk.fm and 79 external pages.

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

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

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

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

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

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 332 words of visible text.

Before a visitor clicks anything, the page loads Google Ads (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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.