saaslibrary.dev website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

3 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

7 long tasks block the main thread while loading, the longest for 445 ms. During a long task the page ignores taps.

About 273 KiB of JavaScript is downloaded but never used on this page.

4 third-party services load with your homepage (Google Tag Manager, tailwindcss.com and Cloudflare and others), adding 313 KiB and 441 ms of main-thread time.

1 image could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

2 images have no width and height attributes, so the layout jumps as each one loads.

surge-casino-pokies.png weighs 2.6 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example surge-casino-pokies.png at 1,800 px wide, shown at 294 px. Resized copies would save about 2.1 MB.

Your homepage downloads 3.1 MB in 9 requests on a phone: images 2.8 MB (2), scripts 312 KiB (3) and HTML 8 KiB (1). Under 2 MB keeps phones on slow connections fast.

2 images (2.8 MB) 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.

1 image further down the page (2.6 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

The page declares lang=“x-default”, which is not a usable language code, so screen readers and translation tools guess.

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

Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (FAQPage, Organization, WebPage and WebSite) but with 2 problems, for example “Organization: sameAs is an empty list”.

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

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

The homepage links to 16 pages on saaslibrary.dev and 1 external page.

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.

There is no https://www.alconburydrivingcentre.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.

https://www.alconburydrivingcentre.com/go has no <title>, so Google invents the link text in results.

https://www.alconburydrivingcentre.com/go is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.alconburydrivingcentre.com/go has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.alconburydrivingcentre.com/go has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 1 page linked from your homepage and read each the way a search engine does.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 1,581 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.