Website review, no card needed
matthewsmotors.com website review
Visit site (opens in a new tab)Reviewed 22 October 202642 issues · 80 checks
This review found 42 issues worth fixing on matthewsmotors.com, 16 of them high impact, across 80 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
67DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.4 s
1.9 s
2.4 s
2.9 s
3.3 s
3.8 s
Speed
Use efficient cache lifetimes
3.5 s · 2.2 MB32 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Reduce unused JavaScript
1.1 s · 731 KiBAbout 731 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.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 619 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 96). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google Maps and userway.org and others), adding 1.3 MB and 1.5 s of main-thread time.
Improve image delivery
500 ms · 590 KiB12 images could be 590 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 322 ms
322 msGoogle Maps costs a phone 322 ms of main-thread work and 427 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 352 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
91 KiBAbout 91 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 96 but mobile only 43. 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.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.5 s
14.5 sYour largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Background Image”.
Time to Interactive: 19.3 s
19.3 sThe page becomes fully interactive after 19.3 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 786 ms
786 msScripts block taps and scrolling for 786 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
10 images without width and height
10 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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
6 images far larger than shown
573 KiB6 images are downloaded at several times the size a phone draws them, for example d9289156f35a5a1677505500771c7880.png at 1,920 px wide, shown at 390 px. Resized copies would save about 573 KiB.
Page weight: 3.7 MB in 74 requests
3.7 MBYour homepage downloads 3.7 MB in 74 requests on a phone: images 1.9 MB (30), scripts 1.3 MB (26) and fonts 330 KiB (4). Under 2 MB keeps phones on slow connections fast.
9 images below the first screen load straight away
9 images further down the page (780 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 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.
2 form fields without a label
2 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.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
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.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 2 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 (“More From Matthews Motors” and “"Give People More Than They Expect And Do It Chee…”). One clear main headline is easier for people and search engines.
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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
76 internal links, 8 external
The homepage links to 76 pages on matthewsmotors.com and 8 external pages.
4 checks passed
Meta description: 97 characters
Your meta description is 97 characters: “New & Used Car needs in Clayton, NC. Shop cars for sale, browse lease deals, or schedule service.”.
Title: 49 characters
Your title is a healthy 49 characters: “New & Used Car Dealership Clayton NC | Wilmington”.
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.matthewsmotors.com/sitemap-pages.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.
No llms.txt
There is no https://www.matthewsmotors.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.
Text is in the HTML
Your server sends the page's text in the HTML (784 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a title
https://www.matthewsmotors.com/used-inventory, https://www.matthewsmotors.com/certified-inventory, https://www.matthewsmotors.com/bargain-inventory, https://www.matthewsmotors.com/wilmington-inventory, https://www.matthewsmotors.com/electric-hybrid-inventory and https://www.matthewsmotors.com/current-offers and 9 others have no <title>, so Google invents the link text in results.
15 pages without an H1
https://www.matthewsmotors.com/used-inventory, https://www.matthewsmotors.com/certified-inventory, https://www.matthewsmotors.com/bargain-inventory, https://www.matthewsmotors.com/wilmington-inventory, https://www.matthewsmotors.com/electric-hybrid-inventory and https://www.matthewsmotors.com/current-offers and 9 others 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 17 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
20 of 23 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 764 words of copy
The homepage carries about 764 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: “SHOP OUR SELECTION” and “SCHEDULE SERVICE”.
19 calls to action
The homepage has 19 calls to action, for example “Shop Inventory”, “Shop Wilmington” and “We Buy Cars”.
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.
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.
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 matthewsmotors.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Gatsby
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on matthewsmotors.com, including 15 speed issues, 6 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.