Website review, no card needed
opgmobility.com website review
Visit site (opens in a new tab)Reviewed 28 October 202658 issues · 96 checks
This review found 58 issues worth fixing on opgmobility.com, 29 of them high impact, across 96 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
52F- #117,626 of 118,024 reviewed websitesbeats 0%
- #67,037 of 67,072 online storesbeats 0%
- #2,704 of 2,706 WooCommerce storesbeats 0%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.5 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 177 ms |
| May 16, 2026 | 175 ms |
| May 23, 2026 | 161 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 151 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 151 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 166 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 189 ms |
| Oct 10, 2026 | 203 ms |
| Oct 17, 2026 | 205 ms |
| Oct 24, 2026 | 203 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
2.5 s
5.0 s
7.6 s
10.1 s
12.6 s
15.1 s
17.6 s
20.1 s
Speed
Use efficient cache lifetimes
14.2 s · 15.3 MB128 files are served with short cache lifetimes, so returning visitors download them again (15.3 MB).
Improve image delivery
4.1 s · 6.8 MB20 images could be 6.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
8.6 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.6 s.
Reduce unused CSS
4.2 s · 809 KiBAbout 809 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Reduce unused JavaScript
3.6 s · 856 KiBAbout 856 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Document request latency
1.7 s · 332 KiBThe HTML itself could arrive about 1.7 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.7 sReduce initial server response time. Google estimates savings of 1.7 s on a phone.
Mobile performance score: 20
20/100Your mobile performance score is 20 (desktop: 53). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,503 HTML elements
The page has 4,503 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 1.8 s
1.8 sYour server takes 1.8 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.3 MB and 1.4 s of main-thread time.
Google Tag Manager adds 599 ms
599 msGoogle Tag Manager costs a phone 599 ms of main-thread work and 531 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 adds 544 ms
544 msFacebook costs a phone 544 ms of main-thread work and 307 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.
Minify JavaScript
380 ms · 103 KiB103 KiB could be saved by minifying JavaScript.
Legacy JavaScript
400 ms · 68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 255 ms. During a long task the page ignores taps.
Cloudflare CDN adds 0 ms
0 msCloudflare CDN costs a phone 0 ms of main-thread work and 378 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.
Minify CSS
210 ms · 50 KiB50 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 53 but mobile only 20. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
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 FCP: 4.6 s
4.6 sReal visitors see the first content after 4.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.1 s
3.1 sReal visitors wait 3.1 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 14.5 s
14.5 sThe first text or image appears after 14.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 31.0 s
31.0 sYour largest element takes 31.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 30.4 s
30.4 sVisually, the page fills in at 30.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 31.6 s
31.6 sThe page becomes fully interactive after 31.6 s. Good is under 3.8 s.
Total Blocking Time: 913 ms
913 msScripts block taps and scrolling for 913 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.282
0.282The layout shifts by 0.282 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 225 ms
225 msReal visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
58 images without width and height
58 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 177 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 17.0 MB in 223 requests
17.0 MBYour homepage downloads 17.0 MB in 223 requests on a phone: images 13.1 MB (74), scripts 2.0 MB (58) and stylesheets 896 KiB (27). Under 2 MB keeps phones on slow connections fast.
About 4.8 g of CO₂ per visit
4.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.80 g of CO₂e: 576.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
[role]s are not contained by their required parent element
[role]s are not contained by their required parent element (3 elements).
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Unlabelled dropdowns
1 dropdown has no label.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings skip levels
Headings skip levels (h1 → h5, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
4 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 4 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“OPG Mobility: India's Leading EV Company” and “FEV 650”). One clear main headline is easier for people and search engines.
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
82 internal links, 12 external
The homepage links to 82 pages on opgmobility.com and 12 external pages.
6 checks passed
Title: 57 characters
Your title is a healthy 57 characters: “OPG Mobility Pvt. Ltd | Electric Vehicle Company in India”.
Canonical URL set
The canonical URL is https://opgmobility.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://opgmobility.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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.
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.
llms.txt published
The site publishes https://opgmobility.com/llms.txt (4 KiB, 42 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://opgmobility.com/landing-page/referral has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://opgmobility.com/product/defy22, whose canonical is https://opgmobility.com/product/defy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://opgmobility.com/contact-us, https://opgmobility.com/landing-page/referral, https://opgmobility.com/about-us, https://opgmobility.com/ev-dealership-subsidies-india and https://opgmobility.com/ev-dealer-marketing have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages slow to respond
https://opgmobility.com/contact-us, https://opgmobility.com/product/fev650, https://opgmobility.com/product/defy22, https://opgmobility.com/product/faast-f4, https://opgmobility.com/product/faast-f2b and https://opgmobility.com/product/opg-mobility-freedum-li and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
4 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 7,482 words of copy
The homepage carries about 7,482 words of visible text.
4 checks passed
21 calls to action
The homepage has 21 calls to action, for example “CONTACT US”, “Contact Us” and “Book Now”.
Social proof on the page
Social proof on the homepage: a star rating, 1 trust badge and “65,000+ Riders”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
9 other companies contacted
Loading the homepage contacts 9 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 opgmobility.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 58 issues on opgmobility.com, including 31 speed issues, 4 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.