Website review, no card needed

shodhatoyota.com logo

shodhatoyota.com website review

Visit site (opens in a new tab)Reviewed 19 October 202654 issues · 87 checks

This review found 54 issues worth fixing on shodhatoyota.com, 19 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of shodhatoyota.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shodhatoyota.com at 1.9 s1.9 s
  2. shodhatoyota.com at 3.7 s3.7 s
  3. shodhatoyota.com at 5.6 s5.6 s
  4. shodhatoyota.com at 7.4 s7.4 s
  5. shodhatoyota.com at 9.3 s9.3 s
  6. shodhatoyota.com at 11.1 s11.1 s
  7. shodhatoyota.com at 13.0 s13.0 s
  8. shodhatoyota.com at 14.8 s14.8 s

Speed

11 to fix42
  • Use efficient cache lifetimes

    6.5 s · 1.5 MB

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

  • Improve image delivery

    5.4 s · 1.1 MB

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

  • Render-blocking requests

    3.6 s

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

  • Font display

    1.8 s

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

  • Reduce unused JavaScript

    1.1 s · 726 KiB

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

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42 (desktop: 50). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.2 s

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

  • 4 third-party services on the page

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

  • Google Tag Manager adds 804 ms

    804 ms

    Google Tag Manager costs a phone 804 ms of main-thread work and 1,002 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 adds 327 ms

    327 ms

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

  • Reduce unused CSS

    300 ms · 55 KiB

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

  • 8 long tasks on the main thread

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

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

Core Web Vitals

7 to fix44
  • Largest Contentful Paint: 16.3 s

    16.3 s

    Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Cool New Toyota Glanza”. Most of its time is resource load delay (7.9 s).

  • Speed Index: 13.6 s

    13.6 s

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

  • Time to Interactive: 19.2 s

    19.2 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Cumulative Layout Shift: 0.19

    0.19

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

  • Total Blocking Time: 405 ms

    405 ms

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

  • 13 images without width and height

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

  • Not enough real-visitor data yet

    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.

Images and page weight

3 to fix65
  • Page weight: 3.5 MB in 73 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 73 requests on a phone: images 2.0 MB (25), scripts 1.1 MB (21) and other files 117 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (489 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 far larger than shown

    243 KiB

    1 image is downloaded at several times the size a phone draws it, for example new-glanza-hompage-banner-1920x807.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 243 KiB.

  • 4 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.98 g

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

Accessibility

12 to fixGoogle 5680
  • Images must have alternative text (10 elements)

    Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.

  • 3 buttons without a name

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

  • Unlabelled dropdowns

    1 dropdown has no label.

  • Positive tabindex

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

  • <html> element must have a lang attribute (1 element)

    <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)

    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)

    Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

  • 5 form fields without a label

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

  • 4 links without text

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

  • No page language

    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)

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

1 checks passed
  • 30 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 8262
  • No H1 headline

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

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Shodha Toyota | Toyota Dealer | Hubli, Belgaum, Bijapur, Davangere”.

  • No structured data

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

  • No canonical URL

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

  • Meta description is long (301 characters)

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

  • No social preview image

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

  • No robots.txt

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

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 6 internal links, 0 external

    The homepage links to 6 pages on shodhatoyota.com and 0 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://shodhatoyota.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    5%

    A phone browser shows 336 words, but the HTML your server sends has only 18. 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.

  • No Organization structured data

    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.

  • No llms.txt

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

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

3 to fix86
  • 1 linked page hidden from search

    https://shodhatoyota.com/online-booking is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages share a meta description

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

  • 5 pages without an H1

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

  • 5 pages with very little text

    https://shodhatoyota.com/contact-hu01a.html, https://shodhatoyota.com/testdrive, https://shodhatoyota.com/pricelist, https://shodhatoyota.com/brochure and https://shodhatoyota.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.

  • 6 internal pages checked

    We fetched 6 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7374
  • 4 broken images

    4 images failed to load on a phone, for example https://static3.toyotabharat.com/images/news/2026/oct-09/thumb-311x175.webp.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://stats.g.doubleclick.net/g/collect?v=2&tid=G-ST34RD2MNP&cid=765115967.1792448414&gtm=45je6ag1v910…”.

  • Pasting is blocked

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

  • 4 distorted images

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

  • 2 low-resolution images

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

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    40 of 42 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • No social proof

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

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

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

  • No risk reducer

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

  • About 336 words of copy

    The homepage carries about 336 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REQUEST A CALLBACK”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at shodhatoyota.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on shodhatoyota.com, including 18 speed issues, 8 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25