whoiselijah.uk website review

About 556 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

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

Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.4 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Klaviyo, returngo.ai and Shopify and others), adding 1.6 MB and 1.2 s of main-thread time.

Klaviyo costs a phone 413 ms of main-thread work and 616 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

returngo.ai costs a phone 340 ms of main-thread work and 236 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Shopify costs a phone 242 ms of main-thread work and 297 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

ZenDesk costs a phone 191 ms of main-thread work and 431 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 KiB could be saved by minifying JavaScript.

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

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

6 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Scripts block taps and scrolling for 662 ms in total while the page loads. Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.1 MB in 268 requests on a phone: scripts 1.5 MB (107), other files 768 KiB (97) and images 460 KiB (22). Under 2 MB keeps phones on slow connections fast.

1 image (33 KiB) is 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.

2 images further down the page (49 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.87 g of CO₂e: 104.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

There are 2 <h1> headlines (“” and “BLURRED LINES”). One clear main headline is easier for people and search engines.

The homepage links to 63 pages on whoiselijah.uk and 1 external page.

There is no https://whoiselijah.us/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://whoiselijah.us/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.

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

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

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 20 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.