Website review, no card needed

dchparamushonda.com logo

dchparamushonda.com website review

Visit site (opens in a new tab)Reviewed 22 October 202639 issues · 91 checks

This review found 39 issues worth fixing on dchparamushonda.com, 17 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.4 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
359 ms247 msMay 2Oct 17312 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026346 ms
May 9, 2026342 ms
May 16, 2026321 ms
May 23, 2026311 ms
May 30, 2026312 ms
Jun 6, 2026313 ms
Jun 13, 2026304 ms
Jun 20, 2026304 ms
Jun 27, 2026288 ms
Jul 4, 2026272 ms
Jul 11, 2026262 ms
Jul 18, 2026260 ms
Jul 25, 2026260 ms
Aug 1, 2026263 ms
Aug 8, 2026283 ms
Aug 15, 2026286 ms
Aug 22, 2026301 ms
Aug 29, 2026306 ms
Sep 5, 2026294 ms
Sep 12, 2026286 ms
Sep 19, 2026275 ms
Sep 26, 2026283 ms
Oct 3, 2026295 ms
Oct 10, 2026304 ms
Oct 17, 2026312 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

Full-page screenshot of dchparamushonda.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dchparamushonda.com at 1.6 s1.6 s
  2. dchparamushonda.com at 3.2 s3.2 s
  3. dchparamushonda.com at 4.9 s4.9 s
  4. dchparamushonda.com at 6.5 s6.5 s
  5. dchparamushonda.com at 8.1 s8.1 s
  6. dchparamushonda.com at 9.7 s9.7 s
  7. dchparamushonda.com at 11.3 s11.3 s
  8. dchparamushonda.com at 13.0 s13.0 s

Speed

14 to fix26
  • Reduce unused JavaScript

    3.4 s · 2.9 MB

    About 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.

  • Use efficient cache lifetimes

    3.7 s · 1.4 MB

    119 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • Google Tag Manager adds 3.1 s

    3.1 s

    Google Tag Manager costs a phone 3.1 s of main-thread work and 4.2 MB 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.

  • Render-blocking requests

    1.8 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Main-thread work: 13.4 s

    A phone's processor spends 13.4 s on main-thread work while loading, 9.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • autodriven.com adds 1.0 s

    1.0 s

    autodriven.com costs a phone 1.0 s of main-thread work and 331 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: 26

    26/100

    Your mobile performance score is 26 (desktop: 49). 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, autodriven.com and orb.ee and others), adding 5.8 MB and 6.6 s of main-thread time.

  • Improve image delivery

    550 ms · 271 KiB

    13 images could be 271 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

  • orb.ee adds 720 ms

    720 ms

    orb.ee costs a phone 720 ms of main-thread work and 317 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.

  • dealeron.com adds 681 ms

    681 ms

    dealeron.com costs a phone 681 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.

  • complyauto.com adds 546 ms

    546 ms

    complyauto.com costs a phone 546 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 543 ms. During a long task the page ignores taps.

  • Minify JavaScript

    340 ms · 36 KiB

    36 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 27 KiB

    Polyfills for old browsers add 27 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

    112 KiB

    About 112 KiB of CSS is downloaded but never applied on this page.

  • 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: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • 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.27

    0.27

    For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 22.1 s

    22.1 s

    Your largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Starting as low as $89 per month”.

  • Speed Index: 15.8 s

    15.8 s

    Visually, the page fills in at 15.8 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 62.3 s

    62.3 s

    The page becomes fully interactive after 62.3 s. Good is under 3.8 s.

  • First Contentful Paint: 6.5 s

    6.5 s

    The first text or image appears after 6.5 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 3.2 s

    3.2 s

    Scripts block taps and scrolling for 3.2 s in total while the page loads. Good is under 200 ms.

  • Real-user INP: 220 ms

    220 ms

    Real visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) got 15% slower for real visitors

    +15%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 407 ms

    407 ms

    Real visitors wait 407 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 346 ms to 312 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.015

    0.015

    The layout barely moves while loading (CLS 0.015, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 9.4 MB in 361 requests

    9.4 MB

    Your homepage downloads 9.4 MB in 361 requests on a phone: scripts 6.4 MB (150), other files 1.1 MB (142) and images 801 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • About 2.7 g of CO₂ per visit

    2.66 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.66 g of CO₂e: 319.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 8996
  • 8 text elements with low contrast

    8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • [role="img"] and [role="image"] elements must have alternative text (3 elements)

    [role="img"] and [role="image"] elements must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 52 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: 52 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • Structured data has 2 problems

    Structured data found ((untyped), AutoDealer and WebSite) but with 2 problems, for example “block has no @type”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 169 internal links, 18 external

    The homepage links to 169 pages on dchparamushonda.com and 18 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “DCH Paramus Honda is a new and used Honda dealership in Paramus, NJ, that proudly serves the drivers of Bergen County. …”.

  • One H1 headline

    Your main headline reads: “DCH Paramus Honda in Paramus, NJ”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “New & Used Honda Dealer Paramus NJ | DCH Paramus Honda”.

  • Canonical URL set

    The canonical URL is https://www.dchparamushonda.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.dchparamushonda.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

3 checks passed
  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,291 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.dchparamushonda.com/llms.txt (44 KiB, 217 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix78
  • 1 linked page hidden from search

    https://www.dchparamushonda.com/mysavedvehicles is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.dchparamushonda.com/mysavedvehicles 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://www.dchparamushonda.com/serviceappmt.aspx, whose canonical is https://www.dchparamushonda.com/schedule-service-paramus-nj.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.dchparamushonda.com/mysavedvehicles and https://www.dchparamushonda.com/honda-vehicle-reviews-paramus-nj 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 71 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

3 to fixGoogle 4688
  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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 “Failed to load resource: the server responded with a status of 403 ()”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    56 of 57 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Thin social proof

    Social proof on the homepage: 6 testimonial or review blocks. 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,005 words of copy

    The homepage carries about 1,005 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Body Shop”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “Contact”, “Call 551-201-0538” and “Shop by Honda Model”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Umami.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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.

  • 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

1 to fix
  • 3 trackers load before any consent

    3

    Before 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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 dchparamushonda.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 39 issues on dchparamushonda.com, including 23 speed issues, 2 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25