Website review, no card needed
liacars.com website review
Visit site (opens in a new tab)Reviewed 3 November 202630 issues · 75 checks
This review found 30 issues worth fixing on liacars.com, 12 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 161 ms |
| May 23, 2026 | 162 ms |
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 224 ms |
| Jun 20, 2026 | 215 ms |
| Jun 27, 2026 | 230 ms |
| Jul 4, 2026 | 221 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 186 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 173 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 188 ms |
| Aug 29, 2026 | 193 ms |
| Sep 5, 2026 | 183 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 217 ms |
| Sep 26, 2026 | 258 ms |
| Oct 3, 2026 | 296 ms |
| Oct 10, 2026 | 298 ms |
| Oct 17, 2026 | 312 ms |
| Oct 24, 2026 | 297 ms |
| Oct 31, 2026 | 281 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
3.5 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Reduce unused JavaScript
2.3 s · 451 KiBAbout 451 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 242 KiB10 files are served with short cache lifetimes, so returning visitors download them again (242 KiB).
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (secureoffersites.com, Google Tag Manager and complyauto.com and others), adding 1.8 MB and 577 ms of main-thread time.
secureoffersites.com adds 189 ms
189 mssecureoffersites.com costs a phone 189 ms of main-thread work and 559 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 148 ms
148 msGoogle Tag Manager costs a phone 148 ms of main-thread work and 821 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.
Improve image delivery
150 ms · 144 KiB3 images could be 144 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 119 ms. During a long task the page ignores taps.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 700 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 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 CLS: 0.56
0.56For real visitors the layout shifts by 0.56 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 6.1 s
6.1 sThe first text or image appears after 6.1 s on a phone. Good is under 1.8 s.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 79% slower for real visitors
+79%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 161 ms to 281 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
7 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 INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 527 ms
527 msReal visitors wait 527 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 117 ms
117 msScripts block the page for only 117 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 51 requests
2.1 MBYour homepage downloads 2.1 MB in 51 requests on a phone: scripts 1.6 MB (28), images 304 KiB (6) and other files 108 KiB (12). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (225 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 (87 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 72.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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 (18 elements)
All page content should be contained by landmarks: 18 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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Welcome to Lia Auto Group” and “Buy Your Next Car From Lia Auto Group”). One clear main headline is easier for people and search engines.
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.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Lia Auto Group has 21 car dealers across NY, CT & MA. Our dealerships offer a great selection of new & used cars for sa…”.
Title: 53 characters
Your title is a healthy 53 characters: “Lia Auto Group - Car Dealerships Across NY, CT and MA”.
Canonical URL set
The canonical URL is https://www.liacars.com/.
Structured data in place
Structured data found: AutoDealer, GeoCoordinates, ImageObject, PostalAddress 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://www.liacars.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.liacars.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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (513 words), so crawlers that don't run JavaScript still read it.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
12 of 14 tappable elements near the top are at least 24 px.
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 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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 662 words of copy
The homepage carries about 662 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
19 other companies contacted
Loading the homepage contacts 19 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 liacars.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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Fastly
Hiring
- Hiring
- 95 open roles
- Teams
- Lia Honda Brewster NY (10), Lia Toyota of Northampton (10), Lia Honda Albany NY (8), Lia Toyota of Colonie (7)
- Job board
- applicantpro
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on liacars.com, including 15 speed issues, 3 SEO issues and 5 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.