Website review, no card needed
autoformindia.com website review
Visit site (opens in a new tab)Reviewed 25 October 202647 issues · 73 checks
This review found 47 issues worth fixing on autoformindia.com, 22 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
47FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.1 s |
| May 9, 2026 | 5.1 s |
| May 16, 2026 | 5.1 s |
| May 23, 2026 | 5.1 s |
| May 30, 2026 | 5.1 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.2 s |
| Jun 20, 2026 | 5.2 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 5.2 s |
| Aug 1, 2026 | 5.2 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.1 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 5.1 s |
| Sep 5, 2026 | 5.1 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 5.0 s |
| Sep 26, 2026 | 5.0 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 5.1 s |
| Oct 17, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 318 ms |
| May 9, 2026 | 312 ms |
| May 16, 2026 | 315 ms |
| May 23, 2026 | 318 ms |
| May 30, 2026 | 316 ms |
| Jun 6, 2026 | 311 ms |
| Jun 13, 2026 | 313 ms |
| Jun 20, 2026 | 320 ms |
| Jun 27, 2026 | 322 ms |
| Jul 4, 2026 | 331 ms |
| Jul 11, 2026 | 331 ms |
| Jul 18, 2026 | 328 ms |
| Jul 25, 2026 | 326 ms |
| Aug 1, 2026 | 327 ms |
| Aug 8, 2026 | 322 ms |
| Aug 15, 2026 | 321 ms |
| Aug 22, 2026 | 322 ms |
| Aug 29, 2026 | 321 ms |
| Sep 5, 2026 | 323 ms |
| Sep 12, 2026 | 321 ms |
| Sep 19, 2026 | 319 ms |
| Sep 26, 2026 | 314 ms |
| Oct 3, 2026 | 308 ms |
| Oct 10, 2026 | 307 ms |
| Oct 17, 2026 | 308 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.9 s
3.7 s
5.6 s
7.4 s
9.3 s
11.1 s
13.0 s
14.8 s
Speed
Use efficient cache lifetimes
10.8 s · 6.8 MB42 files are served with short cache lifetimes, so returning visitors download them again (6.8 MB).
Reduce unused JavaScript
2.4 s · 473 KiBAbout 473 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Minify JavaScript
1.8 s · 383 KiB383 KiB could be saved by minifying JavaScript.
Mobile performance score: 20
20/100Your mobile performance score is 20 (desktop: 34). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,804 HTML elements
The page has 4,804 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
850 ms · 3.1 MB36 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 865 ms. During a long task the page ignores taps.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts and others), adding 3.0 MB and 133 ms of main-thread time.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
299 KiBAbout 299 KiB of CSS is downloaded but never applied on this page.
Amazon Web Services adds 0 ms
0 msAmazon Web Services costs a phone 0 ms of main-thread work and 2.7 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.
Minify CSS
251 KiB251 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.
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 5.2 s
5.2 sReal visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 560 ms
560 msReal visitors wait 560 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.62
0.62For real visitors the layout shifts by 0.62 (75th percentile). Good is under 0.1.
Real-user FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 19.8 s
19.8 sYour largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “. SHOP NOW”. Most of its time is resource load delay (9.8 s).
Speed Index: 20.3 s
20.3 sVisually, the page fills in at 20.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 20.1 s
20.1 sThe page becomes fully interactive after 20.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.698
0.698The layout shifts by 0.698 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 708 ms
708 msScripts block taps and scrolling for 708 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
72 images without width and height
72 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 318 ms to 308 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.1 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 7.3 MB in 81 requests
7.3 MBYour homepage downloads 7.3 MB in 81 requests on a phone: images 3.6 MB (39), scripts 1.8 MB (4) and media 1.6 MB (1). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
192 KiB2 images are downloaded at several times the size a phone draws them, for example balonkun-logo.0e05807638ffa574217b.png at 1,920 px wide, shown at 70 px. Resized copies would save about 192 KiB.
2 images in older formats
2 images (195 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 below the first screen load straight away
1 image further down the page (97 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.07 g of CO₂e: 249.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (18 elements).
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (150 characters)
Your title is 150 characters, so Google will cut it off around 60: “Buy 2 Wheeler and 4 Wheelers Seat Covers and Accessories from Autofrom Brand Store | Shop…”.
30 links with vague text
30 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
4 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Seat Cover and Accessories: Buy Exclusive Car Accessories at AutoForm Stores. Shop a Wide Range of Seat Covers and Acce…”.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://autoformindia.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 397 words, but the HTML your server sends has only 0. 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 llms.txt
There is no https://autoformindia.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Best practices
1 broken image
1 image failed to load on a phone, for example https://autoformindia.com/assets/images/loader-image.png.
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code. See http…”.
15 distorted images
15 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 397 words of copy
The homepage carries about 397 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
7 other companies contacted
Loading the homepage contacts 7 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 autoformindia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on autoformindia.com, including 25 speed issues, 6 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.