rinse.fm website review

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

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

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

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

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

105 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 163 KiB and 133 ms of main-thread time.

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

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.

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

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

Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (4.4 s).

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

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

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

Real visitors wait 209 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-10-10, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 16.1 MB in 160 requests on a phone: media 8.8 MB (12), images 6.3 MB (108) and scripts 665 KiB (24). Under 2 MB keeps phones on slow connections fast.

25 images are downloaded at several times the size a phone draws them, for example Spotlight.-Radio.-Thumbnail.jpg at 600 px wide, shown at 169 px. Resized copies would save about 627 KiB.

Photo_Sonar_Isa_Lab_Mangabeira-0395.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

368 buttons have no accessible name, so screen readers announce just “button”.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

There are 124 <h1> headlines (“DJ MARIA.”, “Silencer with Scorcher, Major, Chaos, Blair Bliz,…” and “Charles Green B2B Tim Reaper”). One clear main headline is easier for people and search engines.

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

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

There is no robots.txt at rinse.fm/robots.txt, the first file search crawlers ask for.

2 links have no real href, so search engines can't follow them.

The homepage links to 627 pages on rinse.fm and 31 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.rinse.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.

/, https://www.rinse.fm/schedule, https://www.rinse.fm/shop, https://www.rinse.fm/shows/tags/electronic, https://www.rinse.fm/shows/tags/multigenre and https://www.rinse.fm/shows/tags/grime and 2 others all use the title “Welcome to Rinse FM | Rinse FM”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rinse.fm/artists, https://www.rinse.fm/schedule, https://www.rinse.fm/shop, https://www.rinse.fm/episodes/live-from-s%C3%B3nar-2026-20-06-2026-2210, https://www.rinse.fm/shows/tags/electronic and https://www.rinse.fm/shows/tags/multigenre and 6 others use the same meta description. A description written for each page earns more clicks.

https://www.rinse.fm/artists 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.

https://www.rinse.fm/episodes/live-from-s%C3%B3nar-2026-20-06-2026-2210 took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

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.

The homepage carries about 2,679 words of visible text.

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