namdhariseeds.com website review

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

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

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

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

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

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

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

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

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

1 third-party service load with your homepage (Google Tag Manager), adding 177 KiB and 121 ms of main-thread time.

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

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

About 14 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

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

16 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-31, real Chrome visitors' tap response (inp) went from 165 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.6 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.

Your homepage downloads 2.6 MB in 39 requests on a phone: scripts 921 KiB (13), other files 868 KiB (3) and images 723 KiB (22). Under 2 MB keeps phones on slow connections fast.

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

12 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is only 25 characters: “Welcome to Namdhari Seeds”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 26 characters: “Seeds for a better future.”. 70 to 160 characters is enough to sell the click.

There are 12 <h1> headlines (“Seed production that empowers smallholding farmer…”, “Production capabilities that are the best in thei…” and “Investing in research for bringing all seed devel…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

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

The homepage links to 33 pages on namdhariseeds.com and 10 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 https://namdhariseeds.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://namdhariseeds.com/careers, https://namdhariseeds.com/capabilities, https://namdhariseeds.com/casestudies, https://namdhariseeds.com/globalpresence and https://namdhariseeds.com/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://namdhariseeds.com/careers, https://namdhariseeds.com/seeds, https://namdhariseeds.com/casestudies and https://namdhariseeds.com/globalpresence have no <h1> headline, so visitors and search engines get no clear main topic.

https://namdhariseeds.com/casestudies and https://namdhariseeds.com/globalpresence 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 8 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads 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.

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