Website review, no card needed
digitalsaas.com website review
Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 74 checks
This review found 31 issues worth fixing on digitalsaas.com, 10 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
Site score
78CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.1 s
2.5 s
2.9 s
3.3 s
Speed
Render-blocking requests
1.6 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Reduce unused JavaScript
1.4 s · 262 KiBAbout 262 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Use efficient cache lifetimes
6.1 MB9 files are served with short cache lifetimes, so returning visitors download them again (6.1 MB).
6 third-party services on the page
6 third-party services load with your homepage (website-files.com, Clarity and cloudfront.net and others), adding 7.0 MB and 768 ms of main-thread time.
website-files.com adds 412 ms
412 mswebsite-files.com costs a phone 412 ms of main-thread work and 6.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.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,906 HTML elements
The page has 1,906 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
180 KiB5 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 178 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.4 s
6.4 sYour largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
45 images without width and height
45 images 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: 178 ms
178 msScripts block the page for only 178 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 7.2 MB in 60 requests
7.2 MBYour homepage downloads 7.2 MB in 60 requests on a phone: media 6.1 MB (4), scripts 588 KiB (16) and images 392 KiB (22). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (121 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 2.0 g of CO₂ per visit
2.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.04 g of CO₂e: 244.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
<svg> elements with an img or image role must have alternative text (3 elements)
<svg> elements with an img or image role must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (81 elements)
All page content should be contained by landmarks: 81 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 171 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
21 internal links, 14 external
The homepage links to 21 pages on digitalsaas.com and 14 external pages.
6 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Digital SaaS is a modern marketing agency that works with startups, enterprises and all around tech companies to help g…”.
One H1 headline
Your main headline reads: “Intelligent Marketingfor Tech & SaaS”.
Title: 47 characters
Your title is a healthy 47 characters: “Digital SaaS - Your SaaS Tech Marketing Partner”.
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.digitalsaas.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.digitalsaas.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,837 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.digitalsaas.com/privacy-policy and https://www.digitalsaas.com/tncs are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a meta description
https://www.digitalsaas.com/privacy-policy and https://www.digitalsaas.com/tncs use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.digitalsaas.com/privacy-policy and https://www.digitalsaas.com/tncs have no <h1> headline, so visitors and search engines get no clear main topic.
2 internal pages checked
We fetched 2 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 2 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 2 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 150 testimonial or review blocks. 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.
About 1,446 words of copy
The homepage carries about 1,446 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a Call”.
10 calls to action
The homepage has 10 calls to action, for example “Book a Call”, “Pricing” and “Contact”.
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 digitalsaas.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
- Webflow
- Analytics
- Google Tag Manager
- Hosting
- Webflow
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on digitalsaas.com, including 13 speed issues, 2 SEO issues and 2 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.