suno.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 6.5 s

  6.5 s

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

• Real-user INP: 942 ms

  942 ms

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

• Real-user CLS: 0.16

  0.16

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

• Tap response (INP) got 75% slower for real visitors

  +75%

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

• Real-user FCP: 2.7 s

  2.7 s

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

• Real-user TTFB: 1.6 s

  1.6 s

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

• Largest content (LCP) held steady for real visitors

  -7%

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

• Page weight: 6.2 MB

  6.2 MB

  Your homepage downloads 6.2 MB on a phone, 2.7 MB of it images (43%). Under 2 MB keeps phones on slow connections fast.

• About 1.8 g of CO₂ per visit

  1.77 g

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

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Page should contain a level-one heading (1 element)

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

  Elements (1)

• All page content should be contained by landmarks (1 element)

  All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Headings skip levels

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

  View source

• Title is short (25 characters)

  Your title is only 25 characters: “Suno | AI Music Generator”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• 5 H1 headlines

  There are 5 <h1> headlines (“Make any song you can imagine”, “Mind blowing song quality” and “Everything you need to make music your way”). One clear main headline is easier for people and search engines.

  View source

• Meta description is long (165 characters)

  Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• 24 internal links, 15 external

  The homepage links to 24 pages on suno.com and 15 external pages.

• 1 page points its canonical at the homepage

  /home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  Elements (1)

• 1 linked page hidden from search

  /careers is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 2 pages share a title

  / and /home all use the title “Suno | AI Music Generator”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (2)

• 2 pages share a meta description

  /safety and /community-guidelines use the same meta description. A description written for each page earns more clicks.

• 2 pages without an H1

  /hub and /community-guidelines have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'getRegistrations')”.

• No call to action on the first screen

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

• Thin social proof

  Social proof on the homepage: “1M+ reviews”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

• Only about 12 words

  The homepage has only about 12 words of visible text; thin pages give Google and first-time buyers little to go on.

• No form on the homepage

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

• 3 cookies set on arrival

  3

  Opening the homepage sets 3 cookies (measured from a US location before any click).

• No consent tool detected

  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.

• 9 other companies contacted

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