saasassembly.co website review

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

4 images could be 242 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 12 ms of main-thread time.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 image. Most of its time is element render delay (2.1 s).

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

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

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 images are downloaded at several times the size a phone draws them, for example Feast_It_trumans-social-club-TI6HVgQZMt.avif at 1,600 px wide, shown at 144 px. Resized copies would save about 300 KiB.

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

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 20 characters: “Home - SaaS Assembly”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 5 problems, for example “WebPage: url is not an absolute URL ("/")”.

The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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 https://saasassembly.co/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 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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.

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