Website review, no card needed
mitsubishicars.com website review
Visit site (opens in a new tab)Reviewed 11 October 202642 issues · 82 checks
This review found 42 issues worth fixing on mitsubishicars.com, 20 of them high impact, across 82 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 4.9 s |
| Apr 25, 2026 | 5.0 s |
| May 2, 2026 | 4.9 s |
| May 9, 2026 | 4.8 s |
| May 16, 2026 | 4.9 s |
| May 23, 2026 | 5.3 s |
| May 30, 2026 | 6.1 s |
| Jun 6, 2026 | 7.1 s |
| Jun 13, 2026 | 7.5 s |
| Jun 20, 2026 | 7.2 s |
| Jun 27, 2026 | 6.5 s |
| Jul 4, 2026 | 6.0 s |
| Jul 11, 2026 | 5.7 s |
| Jul 18, 2026 | 5.5 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.0 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.1 s |
| Sep 12, 2026 | 5.1 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 208 ms |
| Apr 25, 2026 | 209 ms |
| May 2, 2026 | 208 ms |
| May 9, 2026 | 222 ms |
| May 16, 2026 | 246 ms |
| May 23, 2026 | 282 ms |
| May 30, 2026 | 323 ms |
| Jun 6, 2026 | 343 ms |
| Jun 13, 2026 | 358 ms |
| Jun 20, 2026 | 358 ms |
| Jun 27, 2026 | 326 ms |
| Jul 4, 2026 | 292 ms |
| Jul 11, 2026 | 260 ms |
| Jul 18, 2026 | 230 ms |
| Jul 25, 2026 | 219 ms |
| Aug 1, 2026 | 211 ms |
| Aug 8, 2026 | 209 ms |
| Aug 15, 2026 | 209 ms |
| Aug 22, 2026 | 211 ms |
| Aug 29, 2026 | 217 ms |
| Sep 5, 2026 | 215 ms |
| Sep 12, 2026 | 220 ms |
| Sep 19, 2026 | 231 ms |
| Sep 26, 2026 | 242 ms |
| Oct 3, 2026 | 268 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
0.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.2 s
3.7 s
Speed
Use efficient cache lifetimes
7.4 s · 2.2 MB68 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Improve image delivery
3.0 s · 2.3 MB12 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Reduce unused JavaScript
3.3 s · 945 KiBAbout 945 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
1.4 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.
Reduce unused CSS
1.1 s · 235 KiBAbout 235 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 21). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, shiftdigitalapps.io and Facebook and others), adding 1.7 MB and 1.9 s of main-thread time.
Google Tag Manager adds 957 ms
957 msGoogle Tag Manager costs a phone 957 ms of main-thread work and 689 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 760 ms. During a long task the page ignores taps.
shiftdigitalapps.io adds 310 ms
310 msshiftdigitalapps.io costs a phone 310 ms of main-thread work and 242 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 284 ms
284 msFacebook costs a phone 284 ms of main-thread work and 228 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.
2,202 HTML elements
The page has 2,202 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Optanon adds 122 ms
122 msOptanon costs a phone 122 ms of main-thread work and 311 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.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
6 KiB6 KiB JavaScript is shipped twice across bundles.
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: 7 ms
7 msYour server sent the HTML in 7 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.
Largest Contentful Paint: 24.5 s
24.5 sYour largest element takes 24.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “YEAR END SALES EVENT 1.99% APR for 72 Months On All 2026 Ou…”.
Time to Interactive: 33.3 s
33.3 sThe page becomes fully interactive after 33.3 s. Good is under 3.8 s.
First Contentful Paint: 7.2 s
7.2 sThe first text or image appears after 7.2 s on a phone. Good is under 1.8 s.
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Real-user INP: 206 ms
206 msReal visitors wait 206 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.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 208 ms to 268 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 4.9 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 437 ms
437 msReal visitors wait 437 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.058
0.058The layout barely moves while loading (CLS 0.058, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 171 requests
7.6 MBYour homepage downloads 7.6 MB in 171 requests on a phone: images 3.7 MB (36), scripts 2.4 MB (42) and fonts 1.2 MB (21). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
mitsubishi-3-under-30k-suv-lineup-m-v2.png weighs 981 KiB. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (2.6 MB) 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.
9 images below the first screen load straight away
9 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
469 KiB3 images are downloaded at several times the size a phone draws them, for example 2025-mitsubishi-eclipse-cross-interior-m.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 469 KiB.
About 2.2 g of CO₂ per visit
2.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.16 g of CO₂e: 259.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Orphan list items
Some list items are not inside a list.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
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 favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
140 internal links, 38 external
The homepage links to 140 pages on mitsubishicars.com and 38 external pages.
5 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Explore Mitsubishi cars, SUVs, crossovers, sedans, hatchbacks and electric vehicles. Build & price your vehicle, see of…”.
Title: 62 characters
Your title is a healthy 62 characters: “Cars, SUVs, Electric Vehicles & Crossovers | Mitsubishi Motors”.
Canonical URL set
The canonical URL is https://www.mitsubishicars.com/.
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://www.mitsubishicars.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (895 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without an H1
https://www.mitsubishicars.com/configure-your-mitsubishi/configurator, https://www.mitsubishicars.com/trail-edition and https://www.mitsubishicars.com/finance-plans have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 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 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
60 small tap targets
60 of 131 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
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.
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 714 words of copy
The homepage carries about 714 words of visible text.
2 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Sign Up Now”, “Request a Quote” and “Book a Test Drive”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
24 other companies contacted
Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 mitsubishicars.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on mitsubishicars.com, including 23 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.