littleenglish.com website review

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

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

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

POWr costs a phone 2.4 s of main-thread work and 13 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 4,862 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (POWr, route.com and Shopify and others), adding 2.1 MB and 3.7 s of main-thread time.

Your mobile performance score is 55 (desktop: 72). Pages that score under 90 lose visitors before the first paint.

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

route.com costs a phone 503 ms of main-thread work and 744 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.

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

Shopify costs a phone 270 ms of main-thread work and 658 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.

userway.org costs a phone 140 ms of main-thread work and 525 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.

Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

21 images could be 213 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

104 KiB JavaScript is shipped twice across bundles.

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

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

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.

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

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

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

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors wait 902 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 6.2 MB in 541 requests on a phone: scripts 1.9 MB (147), images 1.9 MB (72) and other files 1.9 MB (288). Under 2 MB keeps phones on slow connections fast.

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

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

[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

The homepage links to 179 pages on littleenglish.com and 8 external pages.

https://www.littleenglish.com/collections/best-sellers, https://www.littleenglish.com/collections/swim and https://www.littleenglish.com/collections/swim/boys have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.littleenglish.com/collections/new-arrivals, https://www.littleenglish.com/collections/best-sellers, https://www.littleenglish.com/collections/holiday, https://www.littleenglish.com/collections/swim, https://www.littleenglish.com/collections/the-uniform-shop and https://www.littleenglish.com/collections/all-day-every-day-essentials-for-fall and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Refused to execute script from 'https://www.littleenglish.com/apps/proxy/script/shopify/market/nosto.js?merchant=shopif…”.

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 1,132 words of visible text.

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