Website review, no card needed
reliancejewels.com website review
Visit site (opens in a new tab)Reviewed 28 October 202647 issues · 91 checks
This review found 47 issues worth fixing on reliancejewels.com, 18 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Sep 12, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 374 ms |
| May 16, 2026 | 360 ms |
| May 23, 2026 | 374 ms |
| May 30, 2026 | 395 ms |
| Jun 6, 2026 | 403 ms |
| Jun 27, 2026 | 385 ms |
| Jul 4, 2026 | 380 ms |
| Jul 11, 2026 | 368 ms |
| Jul 25, 2026 | 397 ms |
| Aug 1, 2026 | 424 ms |
| Aug 8, 2026 | 417 ms |
| Aug 22, 2026 | 404 ms |
| Oct 10, 2026 | 337 ms |
| Oct 17, 2026 | 286 ms |
| Oct 24, 2026 | 300 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.5 s
3.0 s
4.5 s
6.0 s
7.5 s
9.0 s
10.5 s
12.0 s
Speed
Use efficient cache lifetimes
4.1 s · 1.4 MB48 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Render-blocking requests
5.5 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.
Reduce unused JavaScript
2.1 s · 447 KiBAbout 447 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Document request latency
1.8 s · 151 KiBThe HTML itself could arrive about 1.8 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.8 sReduce initial server response time. Google estimates savings of 1.8 s on a phone.
Server response: 1.9 s
1.9 sYour server takes 1.9 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 82). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 102 KiBAbout 102 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Google Tag Manager and saleassist.ai and others), adding 761 KiB and 547 ms of main-thread time.
Minify JavaScript
300 ms · 65 KiB65 KiB could be saved by minifying JavaScript.
1,839 HTML elements
The page has 1,839 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.
Improve image delivery
179 KiB8 images could be 179 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
13 KiB13 KiB could be saved by minifying CSS.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 82 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 549 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Speed Index: 17.6 s
17.6 sVisually, the page fills in at 17.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “New Festive Collection”.
Time to Interactive: 17.4 s
17.4 sThe page becomes fully interactive after 17.4 s. Good is under 3.8 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 239 ms
239 msScripts block taps and scrolling for 239 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 374 ms to 300 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 75 requests
2.6 MBYour homepage downloads 2.6 MB in 75 requests on a phone: scripts 1,011 KiB (24), other files 578 KiB (10) and images 386 KiB (23). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
slide_dt.avif 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).
1 image in older formats
1 image (40 KiB) is 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.
About 0.7 g of CO₂ per visit
0.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.73 g of CO₂e: 87.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (7 elements)
Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Reliance Jewels - Buy Gold & Diamond Jewellery Online For Women & Men”.
Meta description is long (169 characters)
Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
288 internal links, 22 external
The homepage links to 288 pages on reliancejewels.com and 22 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.reliancejewels.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.reliancejewels.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.reliancejewels.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,080 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages point its canonical at the homepage
https://www.reliancejewels.com/all-jewellery, https://www.reliancejewels.com/all-jewellery/sort:Popularity, https://www.reliancejewels.com/gold-jewellery and https://www.reliancejewels.com/diamond-jewellery declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages without a meta description
https://www.reliancejewels.com/gsv-brochure, https://www.reliancejewels.com/book-appointment and https://www.reliancejewels.com/callback have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.reliancejewels.com/all-jewellery/sort:Popularity, https://www.reliancejewels.com/gold-jewellery and https://www.reliancejewels.com/diamond-jewellery use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.reliancejewels.com/gsv-brochure and https://www.reliancejewels.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.reliancejewels.com/gsv-brochure has 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.
9 pages slow to respond
https://www.reliancejewels.com/all-jewellery, https://www.reliancejewels.com/all-jewellery/sort:Popularity, https://www.reliancejewels.com/gold-jewellery, https://www.reliancejewels.com/diamond-jewellery, https://www.reliancejewels.com/coins and https://www.reliancejewels.com/blog and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 131 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
8 broken images
8 images failed to load on a phone, for example https://image.reliancejewels.com/Jewels/images/productImages/321/oval-cascade-two-tone-diamond-necklace-set-medium_a2b8fe668a1c9d0ab1abdf2bcad8bc9a.jpg.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “handleImgError is not defined”.
2 checks passed
Tap targets are thumb-sized
35 of 39 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 432 words of copy
The homepage carries about 432 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Silver Jewellery” and “PRE-BOOK NOW”.
12 calls to action
The homepage has 12 calls to action, for example “Book an Appointment”, “Request a Callback” and “Book Appointment”.
4 short forms
4 short forms (6 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
No consent tool detected
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.
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at reliancejewels.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Reliance Industries Limited WAN Backbone Interface with ISPs in India
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on reliancejewels.com, including 21 speed issues, 5 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.