legrand.co.in website review

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

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

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

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

18 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

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

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

Google Tag Manager costs a phone 546 ms of main-thread work and 529 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 547 ms of main-thread work and 305 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.

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

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

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

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

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

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

26 KiB could be saved by minifying CSS.

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

12 KiB could be saved by minifying JavaScript.

Desktop scores 87 but mobile only 56. 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.

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.

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

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

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

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

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

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

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your favourite Legrand products, just a click away”. Most of its time is element render delay (2.9 s).

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

lp_mobile_banner_v2.jpg weighs 526 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.6 MB in 97 requests on a phone: scripts 1.1 MB (26), images 902 KiB (27) and fonts 316 KiB (6). Under 2 MB keeps phones on slow connections fast.

lp_mobile_banner_v2.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images (790 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.75 g of CO₂e: 90.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

7 tap targets are too small or too close together to hit reliably with a finger.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

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

Your title is 73 characters, so Google will cut it off around 60: “Legrand India - Modular Switches Home Automation Switch Board IoT Devices”.

There are 4 <h1> headlines (“Your favourite Legrand products, just a click away”, “Arteor Advance.Intuitive by design” and “Data Center Solutions: Built for agility”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 375 pages on legrand.co.in and 91 external pages.

Your Organization JSON-LD is missing name, url, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.legrand.co.in/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://www.legrand.co.in/boq-cart 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 https://www.legrand.co.in/boq-cart all use the title “Legrand India - Modular Switches Home Automation Switch Board IoT Dev…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.legrand.co.in/smart-spaces/everything-you-need-to-know-about-surge-protection-devices has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.legrand.co.in/support, https://www.legrand.co.in/contact-us, https://www.legrand.co.in/boq-cart, https://www.legrand.co.in/switches-accessories/living-now and https://www.legrand.co.in/switches-accessories/arteor-advance took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://www.legrand.co.in/.

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 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 8,133 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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 10 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.