Website review, no card needed

mccombsfordwest.com logo

mccombsfordwest.com website review

Visit site (opens in a new tab)Reviewed 23 October 202652 issues · 95 checks

This review found 52 issues worth fixing on mccombsfordwest.com, 18 of them high impact, across 95 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.4 sMay 2Oct 172.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.7 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
332 ms226 msMay 2Oct 17310 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026244 ms
May 9, 2026238 ms
May 16, 2026238 ms
May 23, 2026240 ms
May 30, 2026251 ms
Jun 6, 2026258 ms
Jun 13, 2026263 ms
Jun 20, 2026270 ms
Jun 27, 2026269 ms
Jul 4, 2026270 ms
Jul 11, 2026266 ms
Jul 18, 2026262 ms
Jul 25, 2026255 ms
Aug 1, 2026255 ms
Aug 8, 2026271 ms
Aug 15, 2026280 ms
Aug 22, 2026301 ms
Aug 29, 2026311 ms
Sep 5, 2026295 ms
Sep 12, 2026299 ms
Sep 19, 2026306 ms
Sep 26, 2026304 ms
Oct 3, 2026315 ms
Oct 10, 2026320 ms
Oct 17, 2026310 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 mccombsfordwest.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mccombsfordwest.com at 0.6 s0.6 s
  2. mccombsfordwest.com at 1.1 s1.1 s
  3. mccombsfordwest.com at 1.7 s1.7 s
  4. mccombsfordwest.com at 2.3 s2.3 s
  5. mccombsfordwest.com at 2.9 s2.9 s
  6. mccombsfordwest.com at 3.4 s3.4 s
  7. mccombsfordwest.com at 4.0 s4.0 s
  8. mccombsfordwest.com at 4.6 s4.6 s

Speed

15 to fix18
  • Reduce unused JavaScript

    9.0 s · 1.7 MB

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

  • Use efficient cache lifetimes

    7.5 s · 2.0 MB

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

  • Mobile performance score: 18

    18/100

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

  • Main-thread work: 8.6 s

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

  • 3,364 HTML elements

    The page has 3,364 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 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 3.4 MB and 3.1 s of main-thread time.

  • Improve image delivery

    850 ms · 1.7 MB

    25 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

  • dealeron.com adds 898 ms

    898 ms

    dealeron.com costs a phone 898 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 Tag Manager adds 748 ms

    748 ms

    Google Tag Manager costs a phone 748 ms of main-thread work and 1.2 MB 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.

  • Render-blocking requests

    600 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • Reduce unused CSS

    300 ms · 210 KiB

    About 210 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • complyauto.com adds 460 ms

    460 ms

    complyauto.com costs a phone 460 ms of main-thread work and 158 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.

  • dealerteamwork.com adds 302 ms

    302 ms

    dealerteamwork.com costs a phone 302 ms of main-thread work and 737 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.

  • Stripe adds 297 ms

    297 ms

    Stripe costs a phone 297 ms of main-thread work and 269 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 274 ms. During a long task the page ignores taps.

  • Minify JavaScript

    90 ms · 23 KiB

    23 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    50 ms · 15 KiB

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

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

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

Core Web Vitals

13 to fix0
  • 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.

  • Largest Contentful Paint: 85.4 s

    85.4 s

    Your largest element takes 85.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “McCombs Ford West 2025 Ford Bronco Standard: 2 Offers”.

  • Time to Interactive: 85.8 s

    85.8 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Cumulative Layout Shift: 0.453

    0.453

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 277 ms

    277 ms

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

  • Real-user CLS: 0.20

    0.20

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

  • Tap response (INP) got 31% slower for real visitors

    +31%

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

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

    +28%

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 26 images without width and height

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

2 checks passed
  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 644 ms

    644 ms

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

Images and page weight

2 to fix60
  • Page weight: 17.2 MB in 293 requests

    17.2 MB

    Your homepage downloads 17.2 MB in 293 requests on a phone: fonts 9.0 MB (13), scripts 3.8 MB (120) and images 2.9 MB (38). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    61 KiB

    1 image is downloaded at several times the size a phone draws it, for example mustangbonusblock.png at 500 px wide, shown at 100 px. Resized copies would save about 61 KiB.

  • 1 image below the first screen load straight away

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

  • About 4.9 g of CO₂ per visit

    4.88 g

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

8 to fixGoogle 7989
  • Links look like plain text

    7 links inside paragraphs rely on colour alone to stand out.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Invalid ARIA attributes

    6 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

1 checks passed
  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 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

4 to fixGoogle 8386
  • Meta description is long (179 characters)

    Your meta description is 179 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (AutoDealer and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • 13 links crawlers can't follow

    13 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 incomplete here.

  • 193 internal links, 13 external

    The homepage links to 193 pages on mccombsfordwest.com and 13 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “McCombs Ford West”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Ford Dealership in San Antonio, TX | McCombs Ford West”.

  • Canonical URL set

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

  • llms.txt published

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

Other pages

4 to fix78
  • 1 linked page hidden from search

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

  • 1 page without an H1

    https://www.mccombsfordwest.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 77 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 6976
  • 1 broken image

    1 image failed to load on a phone, for example https://iq.webtrackiq.com/12346/00173_mccombsfordwest.com_SMART.GIF.

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “DealerOnTrack is not defined”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix95
  • Thin social proof

    Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • About 1,376 words of copy

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

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call 833-711-9378” and “P.R.O. Shop”.

  • 29 calls to action

    The homepage has 29 calls to action, for example “Contact”, “Call 833-711-9378” and “Pro Shop Custom Vehicles”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Meta Pixel, TikTok Pixel 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
  • 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.

  • 19 cookies set on arrival

    19

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 mccombsfordwest.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on mccombsfordwest.com, including 28 speed issues, 4 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