houseofhodgson.com website review

16 images could be 831 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (cleantalk.org, rewardStyle.com and WordPress Site Stats and others), adding 1.1 MB and 29 ms of main-thread time.

WordPress costs a phone 0 ms of main-thread work and 811 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.

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

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

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

5 KiB could be saved by minifying JavaScript.

Your largest element takes 8.1 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 8.1 s. Good is under 3.8 s.

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

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

The layout shifts by 0.136 while loading, so content jumps under the reader's thumb. Good is under 0.1.

1 image 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.

Your homepage downloads 6.6 MB in 162 requests on a phone: images 5.8 MB (105), other files 306 KiB (10) and fonts 185 KiB (5). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

15 images (3.7 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.

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

7 images are downloaded at several times the size a phone draws them, for example DSCF2315-1400x525.jpg at 1,400 px wide, shown at 390 px. Resized copies would save about 387 KiB.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

4 elements hidden from screen readers can still receive keyboard focus.

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 21 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4 and h1 → 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 14 characters: “Home - Welcome”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 47 pages on houseofhodgson.com and 22 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://houseofhodgson.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://houseofhodgson.com/category/style, https://houseofhodgson.com/category/travel, https://houseofhodgson.com/category/decor, https://houseofhodgson.com/category/beauty, https://houseofhodgson.com/blog and https://houseofhodgson.com/category/style/spring and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://houseofhodgson.com/category/decor, https://houseofhodgson.com/blog, https://houseofhodgson.com/category/lifestyle, https://houseofhodgson.com/blog-sidebar, https://houseofhodgson.com/contact and https://houseofhodgson.com/enchanted-afternoon have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Social proof on the homepage: 14 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 154 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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