wordwall.net website review

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

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

12 images could be 1,008 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

Google Tag Manager costs a phone 353 ms of main-thread work and 676 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.

7 third-party services load with your homepage (Google Tag Manager, Bing Ads and openai.com and others), adding 754 KiB and 399 ms of main-thread time.

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

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

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

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

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

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 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance our site features, support usage …”.

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

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

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

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

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

5 images are downloaded at several times the size a phone draws them, for example printanyactivity.2ffrfymiocjwvrqawpc5nfq2.png at 1,543 px wide, shown at 199 px. Resized copies would save about 659 KiB.

Your homepage downloads 3.0 MB in 104 requests on a phone: images 1.4 MB (39), scripts 1.0 MB (26) and fonts 496 KiB (9). Under 2 MB keeps phones on slow connections fast.

8 images (1.0 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.

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

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

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

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

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

There are 6 <h1> headlines (“More teaching, less prep.”, “More teaching, less prep.” and “Backed by independent classroom research”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

The homepage links to 18 pages on wordwall.net and 2 external pages.

There is no https://wordwall.net/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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97269216&tm=gtm002&Ver=2&mid=efe301c9-d76b-4ba3-a5db-775c2548733a&bo=1&sid=0a1f81b0c5b311f19726d191567dad41&vid=0a1fba90c5b311f19b72f74824861eb4&vids=1&msclkid=N&gtm_t.

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

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

Large scripts ship without source maps.

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

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

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