Website review, no card needed

riverside.fm logo

riverside.fm website review

Visit site (opens in a new tab)Reviewed 6 November 202637 issues · 86 checks

This review found 37 issues worth fixing on riverside.fm, 18 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.6 s4.2 sMay 16Oct 314.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.4 s
May 23, 20265.0 s
May 30, 20264.9 s
Jun 6, 20264.9 s
Jun 13, 20264.8 s
Jun 20, 20264.9 s
Jun 27, 20264.8 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20264.7 s
Jul 25, 20264.7 s
Aug 1, 20264.7 s
Aug 8, 20264.6 s
Aug 15, 20264.5 s
Aug 22, 20264.6 s
Aug 29, 20264.4 s
Sep 5, 20264.5 s
Sep 12, 20264.5 s
Sep 19, 20264.4 s
Sep 26, 20264.4 s
Oct 3, 20264.4 s
Oct 10, 20264.4 s
Oct 17, 20264.4 s
Oct 24, 20264.5 s
Oct 31, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
311 ms208 msMay 16Oct 31220 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026299 ms
May 23, 2026288 ms
May 30, 2026280 ms
Jun 6, 2026282 ms
Jun 13, 2026278 ms
Jun 20, 2026276 ms
Jun 27, 2026274 ms
Jul 4, 2026268 ms
Jul 11, 2026262 ms
Jul 18, 2026260 ms
Jul 25, 2026261 ms
Aug 1, 2026263 ms
Aug 8, 2026269 ms
Aug 15, 2026272 ms
Aug 22, 2026273 ms
Aug 29, 2026272 ms
Sep 5, 2026267 ms
Sep 12, 2026266 ms
Sep 19, 2026258 ms
Sep 26, 2026250 ms
Oct 3, 2026240 ms
Oct 10, 2026228 ms
Oct 17, 2026223 ms
Oct 24, 2026222 ms
Oct 31, 2026220 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of riverside.fm (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. riverside.fm at 0.4 s0.4 s
  2. riverside.fm at 0.8 s0.8 s
  3. riverside.fm at 1.1 s1.1 s
  4. riverside.fm at 1.5 s1.5 s
  5. riverside.fm at 1.9 s1.9 s
  6. riverside.fm at 2.3 s2.3 s
  7. riverside.fm at 2.6 s2.6 s
  8. riverside.fm at 3.0 s3.0 s

Speed

12 to fix35
  • Use efficient cache lifetimes

    3.3 s · 10.3 MB

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

  • Reduce unused JavaScript

    4.8 s · 1.5 MB

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

  • Avoid multiple page redirects

    4.8 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 4.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Segment and website-files.com and others), adding 3.2 MB and 1.0 s of main-thread time.

  • Improve image delivery

    350 ms · 612 KiB

    15 images could be 612 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Render-blocking requests

    650 ms

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

  • website-files.com adds 138 ms

    138 ms

    website-files.com costs a phone 138 ms of main-thread work and 2.0 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.

  • 20 long tasks on the main thread

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

  • Facebook adds 227 ms

    227 ms

    Facebook costs a phone 227 ms of main-thread work and 374 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.

  • ZenDesk adds 110 ms

    110 ms

    ZenDesk costs a phone 110 ms of main-thread work and 355 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.

  • Legacy JavaScript

    63 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    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-user LCP: 4.7 s

    4.7 s

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

  • Largest Contentful Paint: 29.2 s

    29.2 s

    Your largest element takes 29.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 40.9 s

    40.9 s

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

  • Speed Index: 12.7 s

    12.7 s

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

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Total Blocking Time: 948 ms

    948 ms

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

  • Real-user INP: 220 ms

    220 ms

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 949 ms

    949 ms

    Real visitors wait 949 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 4 images without width and height

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

4 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Tap response (INP) got 25% faster for real visitors

    -25%

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 20.5 MB in 240 requests

    20.5 MB

    Your homepage downloads 20.5 MB in 240 requests on a phone: media 14.1 MB (7), scripts 3.6 MB (91) and images 1.3 MB (65). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6a6867116d601b84f1967abf_HP Hero Test_Mobile_2026_05 (4)-p-5 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).

  • About 5.8 g of CO₂ per visit

    5.82 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9792
  • 18 text elements with low contrast

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

  • 1 tap target too small

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

  • 1 image without alt text

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

  • All page content should be contained by landmarks (120 elements)

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

1 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 6182
  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 148 internal links, 19 external

    The homepage links to 148 pages on riverside.fm and 19 external pages.

8 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Riverside is your online studio for high-quality podcast and video recording and editing. Powered by AI, built for huma…”.

  • One H1 headline

    Your main headline reads: “Create your best content yet”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Riverside: HD Podcast & Video Software | Free Recording & Editing”.

  • Canonical URL set

    The canonical URL is https://riverside.com/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://riverside.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://riverside.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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,160 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56339638&tm=gtm002&Ver=2&mid=6db4805e-56d5-4345-bdd6-e98ffeb2ec61&bo=3&sid=2e0e4330d99211f18dbbfd9596395722&vid=2e0e3350d99211f1ad593f3a0cabb07b&vids=0&msclkid=N&pi=91.

  • 2 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

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

  • No direct contact details

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

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

  • No risk reducer

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

  • About 970 words of copy

    The homepage carries about 970 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start for Free”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Contact support”, “Pricing” and “Contact Sales”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, 16 customer or partner logos and 5 trust badges.

  • Analytics in place

    Analytics detected: Meta Pixel, Microsoft Clarity, Segment and Cloudflare Web Analytics.

Privacy and tracking

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Tag Manager, HubSpot, LinkedIn Insight, Meta Pixel and Microsoft Ads and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies, 1 of them by other companies (measured from a US location before any click).

  • 58 other companies contacted

    Loading the homepage contacts 58 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at riverside.fm, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Segment | Microsoft Clarity
Hosting
Cloudflare

Hiring

Hiring
9 open roles
Job board
careers page

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on riverside.fm, including 23 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25