rwhyte.com website review

About 74 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.

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 178 KiB and 93 ms of main-thread time.

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “When knowledge lives in someone’s head or a Slack thread fr…”.

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.

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

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

Your title is 67 characters, so Google will cut it off around 60: “AI Documentation Systems & Technical Writing Automation — Rob Whyte”.

There are 2 <h1> headlines (“AI-Augmented Knowledge Systems” and “Featured work”). One clear main headline is easier for people and search engines.

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 13 pages on rwhyte.com and 4 external pages.

/category/ideas-lab has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /case-study-technical-writer-for-programmatic-advertising-platform, whose canonical is /case-study-illumin-documentation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/contact has 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.

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

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

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 ()”.

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