tinyrebel.co.uk website review

20 images could be 7.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.5 s faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 4.2 s.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.8 MB and 1.9 s of main-thread time.

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

Google CDN costs a phone 571 ms of main-thread work and 734 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 106 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.

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

Facebook costs a phone 297 ms of main-thread work and 227 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.

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

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

Desktop scores 38 but mobile only 9. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

Your largest element takes 19.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Please confirm you are at least 18 years of age, or are of …”.

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

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

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

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

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

6 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-17, real Chrome visitors' tap response (inp) went from 85 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.7 MB in 87 requests on a phone: images 8.4 MB (27), scripts 2.1 MB (30) and fonts 746 KiB (10). Under 2 MB keeps phones on slow connections fast.

6 images weigh 5.8 MB together. On a phone connection a single image that size takes seconds.

19 images (8.2 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.

1 image is downloaded at several times the size a phone draws it, for example 17835270211779957724Rectangle2.png at 1,300 px wide, shown at 370 px. Resized copies would save about 300 KiB.

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

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

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

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

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 120 pages on tinyrebel.co.uk and 16 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://www.tinyrebel.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.tinyrebel.co.uk/browse/c-BEERS-5, https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-CLEARANCE-107, https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-Flagship-47, https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-440S-96, https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-Limited-Releases-17 and https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-Gifting-90 and 2 others all use the title “Beers - Tiny Rebel Brewing”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tinyrebel.co.uk/browse/c-SPIRITS-109, https://www.tinyrebel.co.uk/browse/c-GEAR-6/c-Glassware-20, https://www.tinyrebel.co.uk/browse/c-GEAR-6/c-Clothing-63/c-T-shirts-18, https://www.tinyrebel.co.uk/browse/c-GEAR-6/c-Clothing-63/c-Sweats-Hoodies-29 and https://www.tinyrebel.co.uk/browse/c-GEAR-6/c-Clothing-63/c-Hats-Caps-28 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tinyrebel.co.uk/browse/c-BEERS-5, https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-CLEARANCE-107, https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-Flagship-47, https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-440S-96, https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-Limited-Releases-17 and https://www.tinyrebel.co.uk/browse/c-BEERS-5/c-Gifting-90 and 2 others use the same meta description. A description written for each page earns more clicks.

https://www.tinyrebel.co.uk/gift-vouchers has no <h1> headline, so visitors and search engines get no clear main topic.

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

Large scripts ship without source maps.

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

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

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