mankindag.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, infisecure.com and Cloudflare CDN and others), adding 893 KiB and 537 ms of main-thread time.

The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 560 ms on a phone.

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

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

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

Your server takes 660 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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.

4 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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 text “Mankind Agritech Limited headquartered in New Delhi is an I…”. Most of its time is element render delay (5.1 s).

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

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

1 dropdown has no label.

All page content should be contained by landmarks: 8 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.

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

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

25 tap targets are 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 skip levels (h1 → h4, h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.

Elements with role="none" or role="presentation" have conflicts (2 elements).

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

No XML sitemap at https://mankindag.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at mankindag.com/robots.txt, the first file search crawlers ask for.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 65 pages on mankindag.com and 31 external pages.

There is no https://mankindag.com/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.

https://mankindag.com/about-us, https://mankindag.com/policies-and-disclosures, https://mankindag.com/products, https://mankindag.com/product/herbicide, https://mankindag.com/product/insecticide and https://mankindag.com/product/fungicide and 9 others all use the title “Validation request”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mankindag.com/about-us, https://mankindag.com/policies-and-disclosures, https://mankindag.com/products, https://mankindag.com/product/herbicide, https://mankindag.com/product/insecticide and https://mankindag.com/product/fungicide and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://mankindag.com/about-us, https://mankindag.com/policies-and-disclosures, https://mankindag.com/products, https://mankindag.com/product/herbicide, https://mankindag.com/product/insecticide and https://mankindag.com/product/fungicide and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://mankindag.com/about-us, https://mankindag.com/policies-and-disclosures, https://mankindag.com/products, https://mankindag.com/product/herbicide, https://mankindag.com/product/insecticide and https://mankindag.com/product/fungicide and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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.

The homepage has only about 83 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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