reteacups.com website review

About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, getdeviceinf.com and rebuyengine.com and others), adding 3.0 MB and 2.0 s of main-thread time.

Google Tag Manager costs a phone 834 ms of main-thread work and 953 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

About 93 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.

getdeviceinf.com costs a phone 320 ms of main-thread work and 174 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.

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

rebuyengine.com costs a phone 201 ms of main-thread work and 332 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.

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

tidio.co costs a phone 93 ms of main-thread work and 515 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.

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

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

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

12 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 19.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 37.0 s. Good is under 3.8 s.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 6.0 MB in 373 requests on a phone: scripts 4.4 MB (176), other files 907 KiB (147) and fonts 281 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

[role="img"] and [role="image"] elements must have alternative text: 6 elements on the page fail 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.

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.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.reteacups.com")”.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 180 pages on reteacups.com and 8 external pages.

There is no https://www.reteacups.com/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.reteacups.com/collections has no <h1> headline, so visitors and search engines get no clear main topic.

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

5 of 18 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 (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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

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