Website review, no card needed

bhimajewels.com logo

bhimajewels.com website review

Visit site (opens in a new tab)Reviewed 28 October 202646 issues · 93 checks

This review found 46 issues worth fixing on bhimajewels.com, 12 of them high impact, across 93 checks. The most urgent: page weight: 20.2 MB in 156 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.2 s3.1 sAug 1Oct 244.1 s
Show as table
DateReal-visitor load time (LCP)
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.4 s
Aug 29, 20263.5 s
Sep 5, 20263.8 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Oct 17, 20264.0 s
Oct 24, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
230 ms135 msJul 25Oct 24219 ms
Show as table
DateReal-visitor tap response (INP)
Jul 25, 2026146 ms
Aug 1, 2026149 ms
Aug 8, 2026147 ms
Aug 15, 2026152 ms
Aug 22, 2026160 ms
Aug 29, 2026172 ms
Sep 5, 2026161 ms
Sep 12, 2026163 ms
Sep 19, 2026158 ms
Sep 26, 2026168 ms
Oct 3, 2026197 ms
Oct 10, 2026207 ms
Oct 17, 2026215 ms
Oct 24, 2026219 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

Full-page screenshot of bhimajewels.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bhimajewels.com at 1.1 s1.1 s
  2. bhimajewels.com at 2.1 s2.1 s
  3. bhimajewels.com at 3.2 s3.2 s
  4. bhimajewels.com at 4.3 s4.3 s
  5. bhimajewels.com at 5.4 s5.4 s
  6. bhimajewels.com at 6.5 s6.5 s
  7. bhimajewels.com at 7.5 s7.5 s
  8. bhimajewels.com at 8.6 s8.6 s

Speed

12 to fix61
  • Improve image delivery

    600 ms · 5.4 MB

    37 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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 (kartmax.in, Google Tag Manager and Clarity and others), adding 18.4 MB and 940 ms of main-thread time.

  • kartmax.in adds 380 ms

    380 ms

    kartmax.in costs a phone 380 ms of main-thread work and 8.8 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.

  • Mobile performance score: 61

    61/100

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

  • cloudflarestream.com adds 0 ms

    0 ms

    cloudflarestream.com costs a phone 0 ms of main-thread work and 9.0 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.

  • Document request latency

    900 ms

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

  • Reduce initial server response time

    883 ms

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

  • Reduce unused JavaScript

    150 ms · 440 KiB

    About 440 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Main-thread work: 3.4 s

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

  • Google Tag Manager adds 228 ms

    228 ms

    Google Tag Manager costs a phone 228 ms of main-thread work and 349 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.

  • 2,361 HTML elements

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

  • Server response: 983 ms

    983 ms

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

  • Reduce unused CSS

    221 KiB

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

  • Use efficient cache lifetimes

    218 KiB

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

  • Legacy JavaScript

    150 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 6 long tasks on the main thread

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

  • Render-blocking requests

    100 ms

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify CSS

    42 KiB

    42 KiB could be saved by minifying CSS.

  • Minify JavaScript

    42 KiB

    42 KiB could be saved by minifying JavaScript.

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “oceana-v2-mob”.

  • Speed Index: 12.4 s

    12.4 s

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

  • Time to Interactive: 18.8 s

    18.8 s

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

  • Real-user CLS: 0.19

    0.19

    For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 47% slower for real visitors

    +47%

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

  • Largest content (LCP) got 23% slower for real visitors

    +23%

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

  • Real-user TTFB: 858 ms

    858 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 180 ms

    180 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Total Blocking Time: 117 ms

    117 ms

    Scripts block the page for only 117 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.012

    0.012

    The layout barely moves while loading (CLS 0.012, good is under 0.1).

Images and page weight

2 to fix50
  • Page weight: 20.2 MB in 156 requests

    20.2 MB

    Your homepage downloads 20.2 MB in 156 requests on a phone: media 10.7 MB (1), images 7.8 MB (92) and scripts 967 KiB (31). Under 2 MB keeps phones on slow connections fast.

  • 16 images far larger than shown

    1.4 MB

    16 images are downloaded at several times the size a phone draws them, for example Diamonds-8a9d1056-7704-4c56-aa8f-25cf437778e5.jpg at 1,680 px wide, shown at 77 px. Resized copies would save about 1.4 MB.

  • 1 image in older formats

    1 image (102 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 5.7 g of CO₂ per visit

    5.72 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

11 to fixGoogle 7683
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 22 tap targets too small

    22 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • <marquee> elements are deprecated and must not be used (1 element)

    <marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

  • 39 images without alt text

    39 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (39 elements)

    All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 28 links without text

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

  • 4 form fields without a label

    4 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 (4 elements)

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

  • Headings skip levels

    Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8576
  • No H1 headline

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

  • Title is short (12 characters)

    Your title is only 12 characters: “Bhima Jewels”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (12 characters)

    Your meta description is only 12 characters: “Bhima Jewels”. 70 to 160 characters is enough to sell the click.

  • 2 links crawlers can't follow

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

  • 313 internal links, 14 external

    The homepage links to 313 pages on bhimajewels.com and 14 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.bhimajewels.com/.

  • Structured data in place

    Structured data found: OnlineStore and Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.bhimajewels.com/sitemap.xml.

AI search readiness

100
3 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • llms.txt published

    The site publishes https://www.bhimajewels.com/llms.txt (11 KiB, 99 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 3 pages share a title

    /, https://www.bhimajewels.com/bhima-gold-tree and https://www.bhimajewels.com/track-order all use the title “Bhima Jewels”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.bhimajewels.com/bhima-gold-tree and https://www.bhimajewels.com/track-order use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.bhimajewels.com/storelocator and https://www.bhimajewels.com/track-order have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.bhimajewels.com/category/diamond, https://www.bhimajewels.com/category/new-arrivals, https://www.bhimajewels.com/category/trending and https://www.bhimajewels.com/category/ring took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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

3 to fixGoogle 9285
  • 27 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 13 distorted images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Only about 149 words

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Talk to our experts”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Track My Order”, “Contact Us” and “Book Store Appointment”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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

    7

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 bhimajewels.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
Tailwind CSS
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on bhimajewels.com, including 21 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25