paulsaas.com website review

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

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

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

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

About 74 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

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

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 (Google Fonts), adding 48 KiB and 1 ms of main-thread time.

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.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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.

1 image is downloaded at several times the size a phone draws it, for example header.jpg at 1,456 px wide, shown at 390 px. Resized copies would save about 24 KiB.

5 images (246 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.

3 images further down the page (145 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No XML sitemap at https://paulsaas.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at paulsaas.com/robots.txt, the first file search crawlers ask for.

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

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

The homepage links to 11 pages on paulsaas.com and 2 external pages.

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://paulsaas.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.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 235 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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