rebagg.com website review

66 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

Google Tag Manager costs a phone 1.2 s of main-thread work and 548 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.

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

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

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

Wunderkind costs a phone 337 ms of main-thread work and 234 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 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

2 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “10% Off Everything”.

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

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

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

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

Your homepage downloads 3.7 MB in 234 requests on a phone: scripts 2.9 MB (65), fonts 378 KiB (12) and stylesheets 175 KiB (9). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

A phone browser shows 260 words, but the HTML your server sends has only 46. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no https://www.rebag.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.

/ and https://www.rebag.com/sell-now all use the title “Rebag: Buy & Sell Designer Bags, Watches, Jewelry & More”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rebag.com/thevault has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.rebag.com/trade and https://www.rebag.com/sell-now have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.rebag.com/trade and https://www.rebag.com/sell-now have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=56170434&tm=gtm002&Ver=2&mid=85bb1cfa-ad7d-4cac-a7fa-3f01b7535eb4&bo=1&sid=d23479b0d99d11f1badcf99899d2aed9&vid=d23497f0d99d11f1949f25bd38e62b22&vids=1&msclkid=N&pi=91.

17 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 415 ()”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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

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