orra.co.in website review

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

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

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

8 third-party services load with your homepage (orra.co.in, Google Tag Manager and Facebook and others), adding 4.6 MB and 1.8 s of main-thread time.

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

orra.co.in costs a phone 855 ms of main-thread work and 3.5 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.

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

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

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

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

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

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

16 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 373 requests on a phone: images 2.3 MB (66), scripts 1.6 MB (249) and fonts 441 KiB (7). Under 2 MB keeps phones on slow connections fast.

27 images (1.5 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.

Kalamkari-M.jpg 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).

8 images are downloaded at several times the size a phone draws them, for example org26lc1_1.jpg at 900 px wide, shown at 133 px. Resized copies would save about 343 KiB.

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

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

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

Some list items are not inside a list.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

Your title is 76 characters, so Google will cut it off around 60: “Buy Best Diamond Jewellery Online in India | Gold & Diamond Jewellery - ORRA”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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 at https://www.orra.co.in/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 415 pages on orra.co.in and 109 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

/necklaces-and-pendants has no <title>, so Google invents the link text in results.

/terms-and-conditions, /privacy-policy, /wishlist and /necklaces-and-pendants use the same meta description. A description written for each page earns more clicks.

/privacy-policy and /stores have no <h1> headline, so visitors and search engines get no clear main topic.

/rings/shop-by-metal/white-gold and /earrings/shop-by-metal/yellow-gold took over 3 s to send their HTML from our server.

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

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

6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://asset.fwcdn3.com/js/embed-feed.js' violates the following Content Security Policy directive…”.

Chrome logged issues while loading the page (“Content security policy”).

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

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.

X-XSS-Protection is set to “1; mode=block, 1; mode=block;”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

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

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

Your longest form asks for 9 fields (3 required). Every extra field lowers completion.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 577 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 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.

Opening the homepage sets 19 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.