kink.fm website review

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Rubicon Project, ad-score.com and Google/Doubleclick Ads and others), adding 2.8 MB and 2.2 s of main-thread time.

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

Rubicon Project costs a phone 464 ms of main-thread work and 118 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.

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

ad-score.com costs a phone 410 ms of main-thread work and 214 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.

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

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

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

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

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

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.30 (75th percentile). Good is under 0.1.

Your largest element takes 28.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “KINK's Rainy Day Fund!”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 7.4 MB in 1,291 requests on a phone: images 3.3 MB (427), scripts 2.8 MB (108) and other files 654 KiB (530). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example KINK-IsPink-Logo-1.jpg at 675 px wide, shown at 110 px. Resized copies would save about 541 KiB.

13 images (2.0 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.

4 images further down the page (654 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 2.09 g of CO₂e: 251.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 element hidden from screen readers can still receive keyboard focus.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

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

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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your title is only 10 characters: “101.9 KINK”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 22 characters: “Independent. Portland.”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 104 pages on kink.fm and 26 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

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.

https://www.kink.fm/shows, https://www.kink.fm/miss-something-on-the-show-listen-to-it-here, https://www.kink.fm/shows/mitch, https://www.kink.fm/shows/jared, https://www.kink.fm/shows/gustav and https://www.kink.fm/shows/iris and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kink.fm/shows/mitch, https://www.kink.fm/shows/gustav, https://www.kink.fm/shows/peggy-lapoint, https://www.kink.fm/category/win, https://www.kink.fm/category/wellness-wednesday and https://www.kink.fm/shows/talking-trash-with-peggy-lapoint and 1 other took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://ams-pageview-public.s3.amazonaws.com/1x1-pixel.png?id=6b1d899b867f.

29 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to execute 'insertBefore' on 'Node': Unexpected token '<'”.

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

Large scripts ship without source maps.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 510 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 2 mores (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 11 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 79 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.