Website review, no card needed

malabargoldanddiamonds.com logo

malabargoldanddiamonds.com website review

Visit site (opens in a new tab)Reviewed 1 November 202652 issues · 91 checks

This review found 52 issues worth fixing on malabargoldanddiamonds.com, 19 of them high impact, across 91 checks. The most urgent: render-blocking 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.7 s3.1 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.5 s
May 16, 20263.6 s
May 23, 20263.3 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.6 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20263.7 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
236 ms164 msMay 9Oct 24223 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026208 ms
May 16, 2026195 ms
May 23, 2026185 ms
May 30, 2026179 ms
Jun 6, 2026177 ms
Jun 13, 2026173 ms
Jun 20, 2026173 ms
Jun 27, 2026172 ms
Jul 4, 2026174 ms
Jul 11, 2026179 ms
Jul 18, 2026180 ms
Jul 25, 2026187 ms
Aug 1, 2026192 ms
Aug 8, 2026198 ms
Aug 15, 2026204 ms
Aug 22, 2026207 ms
Aug 29, 2026211 ms
Sep 5, 2026214 ms
Sep 12, 2026223 ms
Sep 19, 2026227 ms
Sep 26, 2026228 ms
Oct 3, 2026225 ms
Oct 10, 2026223 ms
Oct 17, 2026223 ms
Oct 24, 2026223 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 malabargoldanddiamonds.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. malabargoldanddiamonds.com at 0.5 s0.5 s
  2. malabargoldanddiamonds.com at 0.9 s0.9 s
  3. malabargoldanddiamonds.com at 1.4 s1.4 s
  4. malabargoldanddiamonds.com at 1.8 s1.8 s
  5. malabargoldanddiamonds.com at 2.3 s2.3 s
  6. malabargoldanddiamonds.com at 2.8 s2.8 s
  7. malabargoldanddiamonds.com at 3.2 s3.2 s
  8. malabargoldanddiamonds.com at 3.7 s3.7 s

Speed

12 to fix29
  • Render-blocking requests

    4.7 s

    40 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.

  • Reduce unused JavaScript

    1.4 s · 960 KiB

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

  • Reduce unused CSS

    1.2 s · 235 KiB

    About 235 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,408 HTML elements

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

  • Improve image delivery

    3.0 MB

    41 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    450 ms · 815 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Google Tag Manager adds 741 ms

    741 ms

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

  • Minify CSS

    310 ms · 55 KiB

    55 KiB could be saved by minifying CSS.

  • Facebook adds 230 ms

    230 ms

    Facebook costs a phone 230 ms of main-thread work and 322 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.

  • Main-thread work: 2.5 s

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

  • Legacy JavaScript

    150 ms · 41 KiB

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

  • 17 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify JavaScript

    21 KiB

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

1 checks passed
  • Server response: 477 ms

    477 ms

    Your server sent the HTML in 477 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • 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.

  • Real-user CLS: 0.70

    0.70

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

  • Largest Contentful Paint: 22.9 s

    22.9 s

    Your largest element takes 22.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Vyana Collection | Signature Gemstone Jewellery”.

  • Time to Interactive: 28.6 s

    28.6 s

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

  • First Contentful Paint: 6.7 s

    6.7 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Cumulative Layout Shift: 0.464

    0.464

    The layout shifts by 0.464 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • 27 images without width and height

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

  • Total Blocking Time: 308 ms

    308 ms

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

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

1 checks passed
  • Real-user INP: 112 ms

    112 ms

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

Images and page weight

3 to fix53
  • Page weight: 8.4 MB in 416 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 416 requests on a phone: images 5.7 MB (327), scripts 1.9 MB (31) and fonts 458 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 29 images in older formats

    29 images (2.6 MB) 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.

  • 11 images below the first screen load straight away

    11 images further down the page (853 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.4 g of CO₂ per visit

    2.38 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.38 g of CO₂e: 286.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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 7989
  • Unlabelled dropdowns

    1 dropdown has no label.

  • Orphan list items

    Some list items are not inside a list.

  • 4 images without alt text

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

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

  • 9 form fields without a label

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

  • 4 text elements with low contrast

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

  • 2 links without text

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

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

6 to fixGoogle 8573
  • No H1 headline

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

  • Meta description is short (19 characters)

    Your meta description is only 19 characters: “Default Description”. 70 to 160 characters is enough to sell the click.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: 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.

  • No XML sitemap

    No XML sitemap at https://www.malabargoldanddiamonds.com/sitemap.xml, so Google discovers your pages only by following links.

  • 6 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 692 internal links, 13 external

    The homepage links to 692 pages on malabargoldanddiamonds.com and 13 external pages.

3 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “Online Jewelry Shopping store in USA | Malabar Gold & Diamonds”.

  • Canonical URL set

    The canonical URL is https://www.malabargoldanddiamonds.com/us/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
4 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: 5 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,604 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.malabargoldanddiamonds.com/llms.txt (68 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

4 to fix83
  • 2 pages without a meta description

    https://www.malabargoldanddiamonds.com/in and https://www.malabargoldanddiamonds.com/stores have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.malabargoldanddiamonds.com/us/brand/mine.html and https://www.malabargoldanddiamonds.com/us/diamond-jewellery/ring/style.html use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.malabargoldanddiamonds.com/us/brand/precia.html, whose canonical is https://www.malabargoldanddiamonds.com/us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.malabargoldanddiamonds.com/in and https://www.malabargoldanddiamonds.com/stores have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.malabargoldanddiamonds.com/in, https://www.malabargoldanddiamonds.com/stores, https://www.malabargoldanddiamonds.com/us/diamond-jewellery.html, https://www.malabargoldanddiamonds.com/us/diamond-jewellery/ring/style.html and https://www.malabargoldanddiamonds.com/us/diamond-jewellery/ring/style/bands.html took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

4 to fixGoogle 7770
  • 10 broken images

    10 images failed to load on a phone, for example https://www.malabargoldanddiamonds.com/media/wysiwyg/offer_page/2023/010_Oct/intl-promises/assured-lifetime-maintence.svg.

  • 9 small tap targets

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

  • Deprecated browser APIs

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'hide')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

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

  • Thin social proof

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

  • About 347 words of copy

    The homepage carries about 347 words of visible text.

5 checks passed
  • 77 calls to action

    The homepage has 77 calls to action, for example “Sign Up”, “Shop By Style” and “Shop By Metal”.

  • 5 short forms

    5 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 4 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
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 malabargoldanddiamonds.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 | Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on malabargoldanddiamonds.com, including 24 speed issues, 6 SEO issues and 2 conversion gaps. 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