nanditoyota.com website review

6 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.8 s faster on a phone.

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, toyotabharat.com and Google Analytics and others), adding 3.5 MB and 754 ms of main-thread time.

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

Google Tag Manager costs a phone 494 ms of main-thread work and 1,007 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.

toyotabharat.com costs a phone 222 ms of main-thread work and 2.5 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.

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

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

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

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

7 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 20.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dasara Festival”. Most of its time is resource load delay (8.2 s).

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

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

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

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

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

12 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 129 ms to 132 ms 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 3.6 MB in 74 requests on a phone: images 2.1 MB (25), scripts 1.1 MB (22) and other files 150 KiB (20). Under 2 MB keeps phones on slow connections fast.

3 images (501 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 image-handler.ashx at 1,920 px wide, shown at 390 px. Resized copies would save about 251 KiB.

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

By the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 121.0 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: 10 elements on the page fail this check, rated critical by axe-core.

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

1 dropdown has no label.

6 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

Heading levels should only increase by one: 3 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.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

2 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 6 pages on nanditoyota.com and 0 external pages.

A phone browser shows 346 words, but the HTML your server sends has only 15. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://nanditoyota.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://nanditoyota.com/online-booking is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://nanditoyota.com/contact-bl02a.html, https://nanditoyota.com/testdrive, https://nanditoyota.com/pricelist, https://nanditoyota.com/brochure and https://nanditoyota.com/buynow use the same meta description. A description written for each page earns more clicks.

https://nanditoyota.com/testdrive, https://nanditoyota.com/pricelist, https://nanditoyota.com/online-booking, https://nanditoyota.com/brochure and https://nanditoyota.com/buynow have no <h1> headline, so visitors and search engines get no clear main topic.

https://nanditoyota.com/contact-bl02a.html, https://nanditoyota.com/testdrive, https://nanditoyota.com/pricelist, https://nanditoyota.com/brochure and https://nanditoyota.com/buynow 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 6 pages linked from your homepage and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://embed.tawk.to/5983236cd1385b2b2e2856ab/default' violates the following Content Security Pol…”.

A form field blocks pasting, which frustrates password managers and people on phones.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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