bluestone.com website review

61 images could be 2.6 MB 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.

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

About 1.3 MB of JavaScript is downloaded but never used on this page.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and WebEngage and others), adding 1.3 MB and 840 ms of main-thread time.

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

The HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 575 ms on a phone.

Google Tag Manager costs a phone 431 ms of main-thread work and 726 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.6 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Your server takes 675 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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

10 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 11.0 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 25.0 s. Good is under 3.8 s.

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

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

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

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

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 7.4 MB in 157 requests on a phone: images 3.5 MB (75), scripts 1.9 MB (23) and media 1.7 MB (1). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example BS-MC-Offer_Oct_Mobile-Carousel-Sale-Banner---1500-x-1674.jp at 1,500 px wide, shown at 375 px. Resized copies would save about 618 KiB.

4 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (862 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

2 elements hidden from screen readers can still receive keyboard focus.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

12 visible links have no text or label, so screen readers cannot say where they go.

Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 89 characters, so Google will cut it off around 60: “BlueStone Online Jewellery Shopping Store - Buy Gold & Diamond Jewellery Designs In India”.

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

The homepage links to 341 pages on bluestone.com and 7 external pages.

There is no /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.

/recently-viewed and /jewellery/valentines+curation.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/jewellery/watch+jewellery.html, /jewellery/rings.html, /jewellery/earrings.html, /jewellery/pendants.html, /jewellery/preset+solitaires.html and /jewellery.html and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/offer-landing.html has no <h1> headline, so visitors and search engines get no clear main topic.

/jewellery/watch+jewellery.html, /jewellery/pendants.html, /jewellery/preset+solitaires.html, /jewellery.html and /jewellery/goldcoins.html took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://res.cloudinary.com/die12ywpb/image/upload/v1716182323/Logo_1_d3bnan.svg.

5 third-party cookies are 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: net::ERR_FAILED”.

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

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

15 links from your homepage to your own site are broken, for example https://www.bluestone.com/ (500).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example https://www.bluestone.com/tah?cartType=videoCallTah.

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.

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

bluestone.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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

Social proof on the homepage: 23 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage carries about 769 words of visible text.

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, Meta Pixel and Snap 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 32 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.