anitadongre.com website review

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

22 images could be 527 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

Google Tag Manager costs a phone 1.1 s of main-thread work and 522 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.9 MB and 2.9 s of main-thread time.

Google CDN costs a phone 727 ms of main-thread work and 733 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.

Facebook costs a phone 582 ms of main-thread work and 316 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 92 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 430 ms faster on a phone.

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

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

Desktop scores 48 but mobile only 10. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 14.1 MB in 131 requests on a phone: media 10.2 MB (2), scripts 2.5 MB (39) and images 731 KiB (45). Under 2 MB keeps phones on slow connections fast.

6 images (508 KiB) 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.

1 image is downloaded at several times the size a phone draws it, for example 516X774_2_SHOP_BY_CATEGORY.jpg at 516 px wide, shown at 157 px. Resized copies would save about 43 KiB.

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 240 pages on anitadongre.com and 14 external pages.

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.

/wedding/love-is-home, /on/demandware.store/Sites-AD-US-Site/default/Wishlist-Show, /on/demandware.store/Sites-AD-US-Site/default/ContactUs-Show, /on/demandware.store/Sites-AD-US-Site/default/Account-EditProfile and /book-an-appointment all use the title “Sites-AD-US-Site”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/wedding/love-is-home, /on/demandware.store/Sites-AD-US-Site/default/Wishlist-Show, /on/demandware.store/Sites-AD-US-Site/default/ContactUs-Show, /on/demandware.store/Sites-AD-US-Site/default/Account-EditProfile, /book-an-appointment and /on/demandware.store/Sites-AD-US-Site/default/Stores-Find and 2 others use the same meta description. A description written for each page earns more clicks.

/wedding/love-is-home, /on/demandware.store/Sites-AD-US-Site/default/Account-EditProfile, /women/ready-to-ship, /women/new-arrivals, /women/festive-edit-1 and /women/clothing and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Large scripts ship without source maps.

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

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.

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

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

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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