Website review, no card needed

saasweb.pro logo

saasweb.pro website review

Visit site (opens in a new tab)Reviewed 10 November 202618 issues · 61 checks

This review found 18 issues worth fixing on saasweb.pro, 4 of them high impact, across 61 checks. The most urgent: 2 tap targets too small. 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

Full-page screenshot of saasweb.pro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saasweb.pro at 0.6 s0.6 s
  2. saasweb.pro at 1.1 s1.1 s
  3. saasweb.pro at 1.7 s1.7 s
  4. saasweb.pro at 2.3 s2.3 s
  5. saasweb.pro at 2.9 s2.9 s
  6. saasweb.pro at 3.4 s3.4 s
  7. saasweb.pro at 4.0 s4.0 s
  8. saasweb.pro at 4.6 s4.6 s

Speed

3 to fix83
  • Mobile performance score: 83

    83/100

    Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    400 ms

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

  • Use efficient cache lifetimes

    300 ms · 36 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 66 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    21 KiB

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

  • 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: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 204 ms of it running JavaScript. That is comfortably low.

  • Server response: 205 ms

    205 ms

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

Core Web Vitals

4 to fix83
  • Largest Contentful Paint: 4.0 s

    4.0 s

    Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir benötigen Ihre Einwilligung, bevor Sie unsere Website w…”. Most of its time is element render delay (4.4 s).

  • Speed Index: 5.6 s

    5.6 s

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

  • Time to Interactive: 4.0 s

    4.0 s

    The page becomes fully interactive after 4.0 s. Good is under 3.8 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.

3 checks passed
  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 16 ms

    16 ms

    Scripts block the page for only 16 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.1 g of CO₂ per visit

    0.10 g

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

4 checks passed
  • Page weight: 375 KiB in 31 requests

    375 KiB

    Your homepage downloads 375 KiB in 31 requests on a phone: fonts 189 KiB (5), scripts 122 KiB (18) and HTML 46 KiB (1). That is a lean page.

  • 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

3 to fixGoogle 10095
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

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

  • 4 links without text

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 60 internal links, 1 external

    The homepage links to 60 pages on saasweb.pro and 1 external page.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Die Small Business Server Alternative: Hosted Groupware mit Open-Source-Anwendungen für Mail, Dateien, Chat und Projekt…”.

  • One H1 headline

    Your main headline reads: “SaaS Web Business Toolbox: Open Source Groupware für Unternehmen”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Managed Business Server & Hosted Groupware | SaaS Web”.

  • Canonical URL set

    The canonical URL is https://www.saasweb.pro/.

  • Structured data in place

    Structured data found: Article, FAQPage, ImageObject, Organization and Person.

  • 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.saasweb.pro/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.saasweb.pro/llms.txt (8 KiB, 32 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.saasweb.pro/bestellen has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.saasweb.pro/bestellen and https://www.saasweb.pro/funktionen/chat 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.

  • 15 internal pages checked

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

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

  • 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    15 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix20
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • About 1,170 words of copy

    The homepage carries about 1,170 words of visible text.

Privacy and tracking

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

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 saasweb.pro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on saasweb.pro, including 7 speed issues, 1 SEO issue 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

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