Website review, no card needed

andymohrford.com logo

andymohrford.com website review

Visit site (opens in a new tab)Reviewed 22 October 202636 issues · 86 checks

This review found 36 issues worth fixing on andymohrford.com, 17 of them high impact, across 86 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.2 s1.7 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.9 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.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
333 ms148 msMay 2Oct 17180 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026308 ms
May 9, 2026312 ms
May 16, 2026299 ms
May 23, 2026288 ms
May 30, 2026286 ms
Jun 6, 2026277 ms
Jun 13, 2026250 ms
Jun 20, 2026213 ms
Jun 27, 2026187 ms
Jul 4, 2026177 ms
Jul 11, 2026171 ms
Jul 18, 2026169 ms
Jul 25, 2026170 ms
Aug 1, 2026171 ms
Aug 8, 2026179 ms
Aug 15, 2026186 ms
Aug 22, 2026187 ms
Aug 29, 2026182 ms
Sep 5, 2026181 ms
Sep 12, 2026180 ms
Sep 19, 2026178 ms
Sep 26, 2026180 ms
Oct 3, 2026177 ms
Oct 10, 2026172 ms
Oct 17, 2026180 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 andymohrford.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. andymohrford.com at 0.7 s0.7 s
  2. andymohrford.com at 1.3 s1.3 s
  3. andymohrford.com at 2.0 s2.0 s
  4. andymohrford.com at 2.7 s2.7 s
  5. andymohrford.com at 3.3 s3.3 s
  6. andymohrford.com at 4.0 s4.0 s
  7. andymohrford.com at 4.7 s4.7 s
  8. andymohrford.com at 5.3 s5.3 s

Speed

10 to fix18
  • Reduce unused JavaScript

    4.2 s · 2.1 MB

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

  • Use efficient cache lifetimes

    1.3 s · 2.1 MB

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

  • Google Tag Manager adds 1.6 s

    1.6 s

    Google Tag Manager costs a phone 1.6 s of main-thread work and 2.6 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.2 s

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

  • Mobile performance score: 18

    18/100

    Your mobile performance score is 18 (desktop: 47). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.9 s

    A phone's processor spends 6.9 s on main-thread work while loading, 4.4 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, dealeron.com and complyauto.com and others), adding 3.8 MB and 2.7 s of main-thread time.

  • Improve image delivery

    1.2 MB

    17 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • dealeron.com adds 430 ms

    430 ms

    dealeron.com costs a phone 430 ms of main-thread work and 107 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 Maps adds 140 ms

    140 ms

    Google Maps costs a phone 140 ms of main-thread work and 458 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 236 ms. During a long task the page ignores taps.

  • Minify JavaScript

    150 ms · 47 KiB

    47 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    77 KiB

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

  • Legacy JavaScript

    50 ms · 16 KiB

    Polyfills for old browsers add 16 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Phones get a much slower page than desktops

    Desktop scores 47 but mobile only 18. 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

10 to fix67
  • 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.31

    0.31

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

  • Largest Contentful Paint: 24.5 s

    24.5 s

    Your 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 “The above video shows a Ford Bronco driving through a woode…”.

  • Time to Interactive: 48.1 s

    48.1 s

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

  • Speed Index: 15.0 s

    15.0 s

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

  • First Contentful Paint: 5.9 s

    5.9 s

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

  • Cumulative Layout Shift: 0.355

    0.355

    The layout shifts by 0.355 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 861 ms

    861 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • 11 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 182 ms

    182 ms

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

  • Real-user TTFB: 721 ms

    721 ms

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

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

    -43%

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

Images and page weight

3 to fix53
  • Page weight: 18.8 MB in 262 requests

    18.8 MB

    Your homepage downloads 18.8 MB in 262 requests on a phone: media 10.5 MB (2), scripts 4.6 MB (111) and images 2.4 MB (39). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    87 KiB

    1 image is downloaded at several times the size a phone draws it, for example cpo-lineup.png at 1,280 px wide, shown at 360 px. Resized copies would save about 87 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (302 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.3 g of CO₂ per visit

    5.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.32 g of CO₂e: 638.9 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

3 to fixGoogle 9096
  • 2 text elements with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

  • 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 27 images in the HTML carry an alt attribute.

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

SEO

3 to fixGoogle 9288
  • 3 H1 headlines

    There are 3 <h1> headlines (“Ford Dealership in Indiana”, “DealerOn Ford” and “Welcome to Our Ford Dealer”). One clear main headline is easier for people and search engines.

  • Structured data has 3 problems

    Structured data found (AutoDealer, Product and WebSite) but with 3 problems, for example “Product: no offers (price) block”.

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

  • 152 internal links, 25 external

    The homepage links to 152 pages on andymohrford.com and 25 external pages.

5 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Visit Andy Mohr Ford for all of your Ford needs in Plainfield, IN. Shop cars for sale, browse lease deals, or schedule …”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Ford Dealership Plainfield IN | Brownsburg | Indianapolis”.

  • Canonical URL set

    The canonical URL is https://www.andymohrford.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.andymohrford.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,701 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix78
  • 1 linked page hidden from search

    https://www.andymohrford.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.andymohrford.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.andymohrford.com/ford-service.aspx, whose canonical is https://www.andymohrford.com/service-appointment.aspx. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.andymohrford.com/ford-service.aspx, https://www.andymohrford.com/mysavedvehicles, https://www.andymohrford.com/mohr-to-your-door.html and https://www.andymohrford.com/trade.aspx 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 55 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

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    62 of 63 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 1,410 words of copy

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

10 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call 317-707-4180”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact”, “Call 317-707-4180” and “Demo & Loaner Inventory”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Meta Pixel, Hotjar and 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.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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.

  • 21 cookies set on arrival

    21

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 andymohrford.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
Hotjar

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on andymohrford.com, including 20 speed issues and 3 SEO issues. 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