pandora.com website review

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

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

Your mobile performance score is 51 (desktop: 65). Pages that score under 90 lose visitors before the first paint.

2 images could be 738 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

px-cloud.net costs a phone 270 ms of main-thread work and 292 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.

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

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

3 third-party services load with your homepage (px-cloud.net, Optanon and browser-intake-datadoghq.com), adding 484 KiB and 346 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies on our site to customize and enhance your us…”.

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Scripts block taps and scrolling for 288 ms in total while the page loads. Good is under 200 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-03, real Chrome visitors' tap response (inp) went from 154 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 86 requests on a phone: scripts 1.5 MB (34), images 848 KiB (9) and other files 74 KiB (26). Under 2 MB keeps phones on slow connections fast.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

SVG elements with an img role do not have an accessible text alternative (6 elements).

Elements with visible text labels do not have matching accessible names. (1 element).

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

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.

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

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

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

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

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Content security policy”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

The homepage has only about 84 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 8 cookies (measured from a US location before any click).

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.