Website review, no card needed

melorra.com logo

melorra.com website review

Visit site (opens in a new tab)Reviewed 18 November 202628 issues · 81 checks

This review found 28 issues worth fixing on melorra.com, 4 of them high impact, across 81 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
3.7 s1.9 sMay 30Nov 143.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.9 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Oct 24, 20263.3 s
Oct 31, 20263.4 s
Nov 7, 20263.5 s
Nov 14, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
281 ms134 msMay 30Nov 14245 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026156 ms
Jun 6, 2026155 ms
Jun 13, 2026154 ms
Jun 20, 2026152 ms
Jun 27, 2026151 ms
Jul 4, 2026151 ms
Jul 11, 2026152 ms
Jul 18, 2026151 ms
Jul 25, 2026153 ms
Aug 1, 2026156 ms
Aug 8, 2026160 ms
Aug 15, 2026171 ms
Aug 22, 2026186 ms
Aug 29, 2026199 ms
Sep 5, 2026205 ms
Sep 12, 2026216 ms
Sep 19, 2026232 ms
Sep 26, 2026237 ms
Oct 3, 2026251 ms
Oct 10, 2026251 ms
Oct 17, 2026257 ms
Oct 24, 2026264 ms
Oct 31, 2026257 ms
Nov 7, 2026256 ms
Nov 14, 2026245 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 melorra.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. melorra.com at 0.7 s0.7 s
  2. melorra.com at 1.3 s1.3 s
  3. melorra.com at 2.0 s2.0 s
  4. melorra.com at 2.7 s2.7 s
  5. melorra.com at 3.4 s3.4 s
  6. melorra.com at 4.0 s4.0 s
  7. melorra.com at 4.7 s4.7 s
  8. melorra.com at 5.4 s5.4 s

Speed

9 to fix78
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 78

    78/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and notifyvisitors.com and others), adding 908 KiB and 722 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 72 KiB

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

  • Use efficient cache lifetimes

    150 ms · 505 KiB

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

  • Reduce unused JavaScript

    561 KiB

    About 561 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 395 ms

    395 ms

    Google Tag Manager costs a phone 395 ms of main-thread work and 505 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,900 HTML elements

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

  • Main-thread work: 2.3 s

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

  • Improve image delivery

    150 ms · 140 KiB

    15 images could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 14 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    21 KiB

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

1 checks passed
  • Server response: 156 ms

    156 ms

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

Core Web Vitals

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

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Real-user CLS: 0.17

    0.17

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

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

    +61%

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

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

    +59%

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Men Jewellery”.

  • Total Blocking Time: 416 ms

    416 ms

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

7 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 198 ms

    198 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 759 ms

    759 ms

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

  • Cumulative Layout Shift: 0.094

    0.094

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

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 109 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 109 requests on a phone: scripts 1.3 MB (46), images 422 KiB (31) and fonts 121 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.58 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9796
  • All page content should be contained by landmarks (5 elements)

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

  • 41 text elements with low contrast

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

  • Alternative text of images should not be repeated as text (12 elements)

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

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 116 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295
  • Meta description is long (268 characters)

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

  • 367 internal links, 14 external

    The homepage links to 367 pages on melorra.com and 14 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Shop Gold Jewellery Online at Melorra”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Buy Trendy Gold & Diamond Jewellery Online for Women | Melorra”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, Organization and WebSite.

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

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

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix88
  • 11 linked pages hidden from search

    https://www.melorra.com/jewellery/9karat-yellow+gold, https://www.melorra.com/jewellery/9karat-white+gold, https://www.melorra.com/jewellery/9karat-rose+gold, https://www.melorra.com/jewellery/9karat-multiple+gold, https://www.melorra.com/jewellery/work+wear-9karat and https://www.melorra.com/jewellery/party+wear-9karat and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 1 page without an H1

    https://www.melorra.com/cookie-policy has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    13 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 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    38 of 44 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 583 words of copy

    The homepage carries about 583 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 Jewelry” and “📦 Track My Order”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Shop Gold Jewellery Online at Melorra” and “Buy Gold Jewellery Online with Melorra”.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 9 cookies set on arrival

    9

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 melorra.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on melorra.com, including 16 speed issues, 1 SEO issue 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