bebe.com website review

The page goes through 1 redirect before it starts loading, costing about 3.5 s. Link and advertise the final URL directly.

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

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

8 third-party services load with your homepage (rebuyengine.com, Klaviyo and Yotpo and others), adding 3.2 MB and 1.1 s of main-thread time.

Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

About 776 KiB of JavaScript is downloaded but never used on this page.

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

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

rebuyengine.com costs a phone 263 ms of main-thread work and 1,023 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.

The page has 2,797 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 109 ms of main-thread work and 1.2 MB 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.

Klaviyo costs a phone 170 ms of main-thread work and 318 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.

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

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

15 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.

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 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Real visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 163 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 2.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.3 MB in 670 requests on a phone: scripts 2.7 MB (257), images 2.4 MB (124) and other files 1.5 MB (238). Under 2 MB keeps phones on slow connections fast.

Denim_Sept_HP_Refresh2.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 134 pages on bebe.com and 7 external pages.

/pages/archive and /pages/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /pages/wishlist, whose canonical is /apps/wishlist. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/archive, /pages/wishlist, /collections/back-in-stock and /collections/best-sellers have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/back-in-stock and /collections/best-sellers 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.

/pages/archive, /pages/wishlist, /collections/back-in-stock and /collections/best-sellers took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 “%cKlarna Web SDK: Invalid clientInstanceName attribute. Only lowercase letters from a-z and numbers are allowed. color:…”.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example http://www.facebook.com/bebe.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bebe.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 370 words of visible text.

DMARC is set to p=none, so mail pretending to be bebe.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 6 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 41 cookies, 1 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.