relatable.com website review

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

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

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

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

8 third-party services load with your homepage (Accessibe Accessibility Overlay, Clarity and Shopify and others), adding 706 KiB and 837 ms of main-thread time.

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

Accessibe Accessibility Overlay costs a phone 306 ms of main-thread work and 244 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.

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

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

About 11 KiB of CSS is downloaded but never applied on this page.

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

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

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Make the fun”.

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

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

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

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

7 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 100 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 221 requests on a phone: images 1.6 MB (34), scripts 1.1 MB (67) and other files 704 KiB (96). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example catpaw.png at 800 px wide, shown at 202 px. Resized copies would save about 58 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.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: 5 elements on the page fail this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is only 9 characters: “Relatable”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 45 characters: “Ridiculously Relatable Products For All Ages.”. 70 to 160 characters is enough to sell the click.

The homepage links to 36 pages on relatable.com and 8 external pages.

https://relatable.com/collections/all, https://relatable.com/collections/bee-street-games and https://relatable.com/collections/what-do-you-meme have no meta description, so Google writes the search snippet from whatever text it finds.

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

5 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) ReferenceError: fbq is not defined”.

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

The homepage has only about 242 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.

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