littlefae.co.uk website review

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

42 images could be 8.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

8 third-party services load with your homepage (Amazon Web Services, JSDelivr CDN and ecommercedns.uk and others), adding 10.8 MB and 526 ms of main-thread time.

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

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

ecommercedns.uk costs a phone 21 ms of main-thread work and 6.1 MB 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.

1 long task block the main thread while loading, the longest for 489 ms. During a long task the page ignores taps.

Instagram costs a phone 0 ms of main-thread work and 4.4 MB 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.

Amazon Web Services costs a phone 412 ms of main-thread work and 81 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 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.

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

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.

3 KiB could be saved by minifying CSS.

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.

For real visitors the layout shifts by 0.51 (75th percentile). Good is under 0.1.

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

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop our latest collection of premium foam baby Playmats, e…”.

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

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

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

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

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

Your homepage downloads 10.9 MB in 82 requests on a phone: images 10.5 MB (55), scripts 182 KiB (9) and stylesheets 73 KiB (12). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

14 images are downloaded at several times the size a phone draws them, for example 53524652035-4b9e456364-o.jpg at 5,016 px wide, shown at 308 px. Resized copies would save about 3.8 MB.

13 images further down the page (4.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (1.2 MB) 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.

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

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

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

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

1 element hidden from screen readers can still receive keyboard focus.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

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

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

8 links have no real href, so search engines can't follow them.

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 139 pages on littlefae.co.uk and 3 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.

The HTML your server sends has 945 of the 2,720 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.littlefae.co.uk/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.littlefae.co.uk/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://www.littlefae.co.uk/tracker?uri=%2F.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://hq-apps-sw.s3.eu-west-1.amazonaws.com/instagram-app/live/v2/main.css' from origin …”.

Social proof on the homepage: 7 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.

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 2,720 words of visible text.

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