Website review, no card needed

saasdirectory.com logo

saasdirectory.com website review

Visit site (opens in a new tab)Reviewed 9 November 202630 issues · 74 checks

This review found 30 issues worth fixing on saasdirectory.com, 8 of them high impact, across 74 checks. The most urgent: document request latency. 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 saasdirectory.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saasdirectory.com at 0.4 s0.4 s
  2. saasdirectory.com at 0.8 s0.8 s
  3. saasdirectory.com at 1.1 s1.1 s
  4. saasdirectory.com at 1.5 s1.5 s
  5. saasdirectory.com at 1.9 s1.9 s
  6. saasdirectory.com at 2.3 s2.3 s
  7. saasdirectory.com at 2.7 s2.7 s
  8. saasdirectory.com at 3.0 s3.0 s

Speed

5 to fix84
  • Document request latency

    1.3 s

    The HTML itself could arrive about 1.3 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Render-blocking requests

    1.3 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

  • Avoid multiple page redirects

    1.2 s

    The page goes through 1 redirect before it starts loading, costing about 1.2 s. Link and advertise the final URL directly.

  • Mobile performance score: 84

    84/100

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

  • Reduce unused JavaScript

    300 ms · 36 KiB

    About 36 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 58 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Other Google APIs/SDKs, Google CDN and Cloudflare), adding 111 KiB and 54 ms of main-thread time.

  • Improve image delivery

    16 KiB

    2 images could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix85
  • Cumulative Layout Shift: 0.167

    0.167

    The layout shifts by 0.167 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 4.5 s

    4.5 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Largest Contentful Paint: 2.8 s

    2.8 s

    Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Saas Directory – Find and compare online software and appli…”. Most of its time is element render delay (2.5 s).

  • 5 images without width and height

    5 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
  • Time to Interactive: 2.8 s

    2.8 s

    The page is fully interactive after 2.8 s.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.08 g of CO₂ per visit

    0.08 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.08 g of CO₂e: 9.1 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: 274 KiB in 24 requests

    274 KiB

    Your homepage downloads 274 KiB in 24 requests on a phone: scripts 145 KiB (7), other files 76 KiB (4) and images 45 KiB (11). 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

8 to fixGoogle 7985
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 29 automated accessibility rules passed

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

SEO

3 to fixGoogle 10089
  • 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.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 193 internal links, 3 external

    The homepage links to 193 pages on saasdirectory.com and 3 external pages.

5 checks passed
  • Meta description: 106 characters

    Your meta description is 106 characters: “SaasDirectory is the Best SaaS & Cloud Directory in Internet, the Software as a Service, SaaS, PaaS & IaaS”.

  • One H1 headline

    Your main headline reads: “Saas Directory – Find and compare online software and applications”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “SaaS Directory, Cloud Computing. Online software SaaS PaaS IaaS”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.saasdirectory.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.saasdirectory.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 (859 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 2 pages without a meta description

    https://www.saasdirectory.com/register-saas-directory.php and https://www.saasdirectory.com/saas-applications/Collaborative-Platforms have no meta description, so Google writes the search snippet from whatever text it finds.

  • 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.saasdirectory.com/saas-applications.php, whose canonical is https://www.saasdirectory.com/saas-applications/saas-applications. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://www.saasdirectory.com/register-saas-directory.php, https://www.saasdirectory.com/saas-applications.php, https://www.saasdirectory.com/suggest-an-app.php, https://www.saasdirectory.com/contact.php, https://www.saasdirectory.com/saas-cloud-computing-events.php and https://www.saasdirectory.com/saas-applications/BPM and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.saasdirectory.com/register-saas-directory.php, https://www.saasdirectory.com/suggest-an-app.php, https://www.saasdirectory.com/contact.php and https://www.saasdirectory.com/saas-cloud-computing-events.php 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 161 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

3 to fixGoogle 7366
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 86 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 low-resolution images

    6 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • No console errors

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

Content and conversion

2 to fix75
  • 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.

  • 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 410 words of copy

    The homepage carries about 410 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 saasdirectory.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on saasdirectory.com, including 10 speed issues, 3 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

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