Website review, no card needed
saasscaled.com website review
Visit site (opens in a new tab)Reviewed 9 November 202636 issues · 69 checks
This review found 36 issues worth fixing on saasscaled.com, 14 of them high impact, across 69 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Reduce unused JavaScript
5.9 s · 850 KiBAbout 850 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.
Use efficient cache lifetimes
3.1 s · 381 KiB5 files are served with short cache lifetimes, so returning visitors download them again (381 KiB).
Improve image delivery
1.8 s · 1.1 MB9 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Reduce unused CSS
1.0 s · 158 KiBAbout 158 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Squarespace, spotifycdn.com and Hubspot and others), adding 3.9 MB and 950 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Squarespace adds 382 ms
382 msSquarespace costs a phone 382 ms of main-thread work and 920 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.
spotifycdn.com adds 374 ms
374 msspotifycdn.com costs a phone 374 ms of main-thread work and 717 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
300 ms · 94 KiBPolyfills for old browsers add 94 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Hubspot adds 159 ms
159 msHubspot costs a phone 159 ms of main-thread work and 401 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.
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 1.7 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 181 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 42 ms
42 msYour server sent the HTML in 42 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.3 s
8.3 sThe first text or image appears after 8.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 21.2 s
21.2 sYour largest element takes 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.5 s
21.5 sThe page becomes fully interactive after 21.5 s. Good is under 3.8 s.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 151 ms
151 msScripts block the page for only 151 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 113 requests
4.1 MBYour homepage downloads 4.1 MB in 113 requests on a phone: scripts 1.9 MB (61), images 1.6 MB (14) and fonts 286 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 139.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (11 characters)
Your title is only 11 characters: “SaaS Scaled”. Between 30 and 65 characters leaves room to say what you do and for whom.
7 H1 headlines
There are 7 <h1> headlines (“Interviews with experts on scaling SaaS”, “ABOUT THE PODCAST” and “6774”). One clear main headline is easier for people and search engines.
Meta description is long (224 characters)
Your meta description is 224 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6189559b46cd3312f22…”.
25 internal links, 13 external
The homepage links to 25 pages on saasscaled.com and 13 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.saasscaled.com/.
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://www.saasscaled.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.saasscaled.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.
1 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.
Other pages
4 linked pages hidden from search
https://www.saasscaled.com/episodes, https://www.saasscaled.com/about, https://www.saasscaled.com/contact and https://www.saasscaled.com/episodes/steve-cox-ceo-at-salesloft-the-revenue-orchestration-platform-that-closes-the-gap-between-what-revenue-teams-know-and-what-they-do-next are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.saasscaled.com/book-recommendations and https://www.saasscaled.com/guest-recommendations all use the title “General 2 — SaaS Scaled”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.saasscaled.com/newsletters, https://www.saasscaled.com/book-recommendations, https://www.saasscaled.com/cities and https://www.saasscaled.com/guest-recommendations have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.saasscaled.com/episodes, https://www.saasscaled.com/about and https://www.saasscaled.com/contact use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.saasscaled.com/guest-recommendations, whose canonical is https://www.saasscaled.com/book-recommendations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_UNKNOWN_URL_SCHEME”.
2 checks passed
Tap targets are thumb-sized
15 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 142 words
The homepage has only about 142 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.
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.
1 checks passed
Analytics in place
Analytics detected: HubSpot.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 2 of them by other companies (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.
19 other companies contacted
Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 saasscaled.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Squarespace
- Hosting
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on saasscaled.com, including 17 speed issues, 4 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.