24chakra.com website review

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

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

20 images could be 728 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Bigcommerce, omnisnippet1.com and Privy and others), adding 1.9 MB and 314 ms of main-thread time.

Bigcommerce costs a phone 158 ms of main-thread work and 1.4 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.

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

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

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

Your largest element takes 3.4 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 5.6 s. Good is under 3.8 s.

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

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

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.

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

1 image is downloaded at several times the size a phone draws it, for example sharadha-store.jpg at 1,536 px wide, shown at 324 px. Resized copies would save about 39 KiB.

8 images (432 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.

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

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

Some list items are not inside a list.

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 71 characters, so Google will cut it off around 60: “Buy South Indian Sweets Online in USA | 24Chakra.com | Grand Sweets USA”.

Your meta description is only 8 characters: “24chakra”. 70 to 160 characters is enough to sell the click.

There are 4 <h1> headlines (“”, “Grand Sweets & Snacks” and “Crunchy Savories”). One clear main headline is easier for people and search engines.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 1)”.

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://24chakra.com/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 239 pages on 24chakra.com and 8 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.

/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /home all use the title “Buy South Indian Sweets Online in USA | 24Chakra.com | Grand Sweets U…”. Search engines can't tell which page to show for a search, so each competes with the others.

/sri-krishna-mysorepak, /home, /diwali-sweets-online, /indian-sweets-online, /sweets/all-sweets/milk-ghee-sweets and /sweets/all-sweets/halwa-sweets and 9 others use the same meta description. A description written for each page earns more clicks.

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

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

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

1 link go through two or more redirects, for example https://www.facebook.com/pages/category/Product-Service/IndianSweetsOnline-We-deliver-Grand-Sweets-Snacks-Sri-Krishna-More-167335913403051/.

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.

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

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

The homepage carries about 727 words of visible text.

DMARC is set to p=none, so mail pretending to be 24chakra.com is still delivered. Add a report address, check the reports, then move to quarantine.

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.

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