Website review, no card needed
darcars.com website review
Visit site (opens in a new tab)Reviewed 3 November 202639 issues · 91 checks
This review found 39 issues worth fixing on darcars.com, 14 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 259 ms |
| May 23, 2026 | 253 ms |
| May 30, 2026 | 242 ms |
| Jun 6, 2026 | 238 ms |
| Jun 13, 2026 | 232 ms |
| Jun 20, 2026 | 217 ms |
| Jun 27, 2026 | 215 ms |
| Jul 4, 2026 | 218 ms |
| Jul 11, 2026 | 207 ms |
| Jul 18, 2026 | 201 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 179 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 183 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 171 ms |
| Oct 31, 2026 | 161 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.9 s
1.7 s
2.6 s
3.5 s
4.3 s
5.2 s
6.1 s
6.9 s
Speed
Improve image delivery
4.4 s · 970 KiB10 images could be 970 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.4 s faster on a phone.
Use efficient cache lifetimes
3.1 s · 662 KiB53 files are served with short cache lifetimes, so returning visitors download them again (662 KiB).
Reduce unused JavaScript
1.6 s · 594 KiBAbout 594 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.1 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 4.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 (dealeron.com, Google Tag Manager and complyauto.com and others), adding 1.3 MB and 2.5 s of main-thread time.
dealeron.com adds 736 ms
736 msdealeron.com costs a phone 736 ms of main-thread work and 111 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.
Google Tag Manager adds 533 ms
533 msGoogle Tag Manager costs a phone 533 ms of main-thread work and 543 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.
complyauto.com adds 463 ms
463 mscomplyauto.com costs a phone 463 ms of main-thread work and 122 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.
VWO adds 354 ms
354 msVWO costs a phone 354 ms of main-thread work and 194 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 310 ms. During a long task the page ignores taps.
1,934 HTML elements
The page has 1,934 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
19 KiB19 KiB could be saved by minifying JavaScript.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 20.8 s
20.8 sYour largest element takes 20.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WE’RE HERE FOR EVERY MILE. See why over 1 million people ch…”.
Time to Interactive: 24.1 s
24.1 sThe page becomes fully interactive after 24.1 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 424 ms
424 msReal visitors wait 424 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 259 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 163 requests
4.4 MBYour homepage downloads 4.4 MB in 163 requests on a phone: images 1.6 MB (46), scripts 1.6 MB (54) and other files 937 KiB (51). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
2 checks passed
Every image has alt text
All 68 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (86 characters)
Your title is 86 characters, so Google will cut it off around 60: “DARCARS Automotive Group | Mid-Atlantic, Virginia, and Maryland Automotive Dealerships”.
2 H1 headlines
There are 2 <h1> headlines (“EVERY MILE.” and “Why Shop with DARCARS?”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (AutomotiveBusiness and WebSite) but with 1 problem, for example “WebSite: missing name”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
173 internal links, 107 external
The homepage links to 173 pages on darcars.com and 107 external pages.
5 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “DARCARS Automotive Group provides a great car buying experience with our convenient Northeast, Mid-Atlantic, and Florid…”.
Canonical URL set
The canonical URL is https://www.darcars.com/.
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://www.darcars.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.
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
2 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,910 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.darcars.com/llms.txt (55 KiB, 244 links), a plain-text guide to the site for AI tools.
Other pages
5 linked pages hidden from search
https://www.darcars.com/all-locations.html, https://www.darcars.com/service.html, https://www.darcars.com/used-inventory-dealerships.html, https://www.darcars.com/mysavedvehicles and https://www.darcars.com/aboutus.aspx are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
1 page without a meta description
https://www.darcars.com/mysavedvehicles has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.darcars.com/mysavedvehicles has 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 39 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “DealerOnTrack is not defined”.
19 distorted images
19 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
52 of 53 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 36 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,507 words of copy
The homepage carries about 1,507 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “SHOP NEW”.
12 calls to action
The homepage has 12 calls to action, for example “Call”, “Schedule Service” and “Schedule Free Estimate”.
1 short form
A short form (3 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Meta Pixel and Umami.
Direct contact links
Visitors can reach you directly: 31 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
12 other companies contacted
Loading the homepage contacts 12 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 darcars.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
- jQuery
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on darcars.com, including 19 speed issues, 3 SEO issues and 2 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.