soundtrap.com website review

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

37 files are served with short cache lifetimes, so returning visitors download them again (682 KiB).

22 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and Hubspot and others), adding 907 KiB and 292 ms of main-thread time.

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

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

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.

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

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

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

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

Real visitors wait 306 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-17, real Chrome visitors' tap response (inp) went from 309 ms to 403 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

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

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

Your homepage downloads 11.2 MB in 142 requests on a phone: media 6.8 MB (2), scripts 2.1 MB (54) and images 1.8 MB (40). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 64 pages on soundtrap.com and 12 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 /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.

/studio/fork/8rHNvQM6SKmr64_cMOoV7Q, /studio/fork/PA1UlV2jQ3eCapNmnUa6Gg, /studio/fork/NVcw1N4GQCSYRhyZJdRVxg, /studio/fork/8xMe-IFYTmewjTDEMsLNUQ, /studio/fork/EwVWkQqQSia9g58d1a7Glg and /studio/fork/T11wgPxoTKON98cx2DHBoA and 1 other all use the title “Soundtrap Login”. Search engines can't tell which page to show for a search, so each competes with the others.

/studio/fork/8rHNvQM6SKmr64_cMOoV7Q, /studio/fork/PA1UlV2jQ3eCapNmnUa6Gg, /studio/fork/NVcw1N4GQCSYRhyZJdRVxg, /studio/fork/8xMe-IFYTmewjTDEMsLNUQ, /studio/fork/EwVWkQqQSia9g58d1a7Glg and /studio/fork/T11wgPxoTKON98cx2DHBoA and 1 other use the same meta description. A description written for each page earns more clicks.

Your homepage links to 7 pages by a URL that isn't their canonical one, for example /studio/fork/8rHNvQM6SKmr64_cMOoV7Q, whose canonical is /login. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pricing has no <h1> headline, so visitors and search engines get no clear main topic.

/studio/fork/8rHNvQM6SKmr64_cMOoV7Q, /studio/fork/PA1UlV2jQ3eCapNmnUa6Gg, /studio/fork/NVcw1N4GQCSYRhyZJdRVxg, /studio/fork/8xMe-IFYTmewjTDEMsLNUQ, /studio/fork/EwVWkQqQSia9g58d1a7Glg and /studio/fork/T11wgPxoTKON98cx2DHBoA and 1 other have 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.

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=56026266&tm=gtm002&Ver=2&mid=44c5b4f2-d580-4c3a-80c8-e64b1898abf9&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Free%20Online%20Music%20%26%20Beat%20Maker%20.

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

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

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

10 links go through two or more redirects, for example https://www.soundtrap.com/studio/fork/8rHNvQM6SKmr64_cMOoV7Q/.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

soundtrap.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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.

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

DMARC is set to p=none, so mail pretending to be soundtrap.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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