amritasingh.com website review

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

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

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

About 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, pxucdn.com and revy.io and others), adding 694 KiB and 257 ms of main-thread time.

1 long task block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.0 MB in 257 requests on a phone: images 1.0 MB (33), other files 1,011 KiB (154) and scripts 881 KiB (58). Under 2 MB keeps phones on slow connections fast.

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

5 images are downloaded at several times the size a phone draws them, for example FER_113_MODEL_450x450.jpg at 450 px wide, shown at 126 px. Resized copies would save about 74 KiB.

1 image (43 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.

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

1 dropdown has no label.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 108 characters, so Google will cut it off around 60: “Amrita Singh Jewelry: Designer Indian Jewelry and Fashion Accessories — Amrita Singh Jewe…”.

There are 55 <h1> headlines (“”, “18k Gold Turquoise and Onyx Orchha Necklace” and “18k Gold Coral Smokey Quartz Izma Necklace”). One clear main headline is easier for people and search engines.

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

Structured data found (BreadcrumbList and WebSite) but with 1 problem, for example “BreadcrumbList: itemListElement is an empty list”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 173 pages on amritasingh.com and 7 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.

/collections/earrings, /collections/necklaces, /collections/bangles-1, /collections/bangles-2, /collections/pendants and /pages/contact-us-1 have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example /collections/all-fine-jewelry/products/18k-gold-turquoise-and-onyx-orchha-necklace, whose canonical is /products/18k-gold-turquoise-and-onyx-orchha-necklace. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

3 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

3 links go through two or more redirects, for example https://amritasingh.com/account/login.

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

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

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

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

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 523 words of visible text.

amritasingh.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 and Google Tag Manager (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 8 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.