Website review, no card needed

gunnauto.com logo

gunnauto.com website review

Visit site (opens in a new tab)Reviewed 21 October 202631 issues · 85 checks

This review found 31 issues worth fixing on gunnauto.com, 9 of them high impact, across 85 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
6.2 s2.5 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.6 s
May 9, 20264.8 s
May 16, 20264.8 s
May 23, 20264.8 s
May 30, 20264.8 s
Jun 6, 20264.8 s
Jun 13, 20264.9 s
Jun 20, 20264.9 s
Jun 27, 20265.1 s
Jul 4, 20265.2 s
Jul 11, 20265.4 s
Jul 18, 20265.7 s
Jul 25, 20265.8 s
Aug 1, 20265.7 s
Aug 8, 20265.6 s
Aug 15, 20265.1 s
Aug 22, 20264.4 s
Aug 29, 20264.0 s
Sep 5, 20263.6 s
Sep 12, 20263.2 s
Sep 19, 20263.3 s
Sep 26, 20263.1 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
247 ms151 msMay 2Oct 17164 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026190 ms
May 9, 2026192 ms
May 16, 2026188 ms
May 23, 2026195 ms
May 30, 2026179 ms
Jun 6, 2026188 ms
Jun 13, 2026192 ms
Jun 20, 2026186 ms
Jun 27, 2026188 ms
Jul 4, 2026187 ms
Jul 11, 2026209 ms
Jul 18, 2026236 ms
Jul 25, 2026229 ms
Aug 1, 2026212 ms
Aug 8, 2026205 ms
Aug 15, 2026197 ms
Aug 22, 2026197 ms
Aug 29, 2026196 ms
Sep 5, 2026196 ms
Sep 12, 2026193 ms
Sep 19, 2026187 ms
Sep 26, 2026181 ms
Oct 3, 2026170 ms
Oct 10, 2026162 ms
Oct 17, 2026164 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 gunnauto.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gunnauto.com at 0.6 s0.6 s
  2. gunnauto.com at 1.3 s1.3 s
  3. gunnauto.com at 1.9 s1.9 s
  4. gunnauto.com at 2.5 s2.5 s
  5. gunnauto.com at 3.2 s3.2 s
  6. gunnauto.com at 3.8 s3.8 s
  7. gunnauto.com at 4.4 s4.4 s
  8. gunnauto.com at 5.1 s5.1 s

Speed

9 to fix58
  • Reduce unused JavaScript

    3.6 s · 727 KiB

    About 727 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, complyauto.com and dealereprocess.org and others), adding 1.6 MB and 1.3 s of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 205 KiB

    37 files are served with short cache lifetimes, so returning visitors download them again (205 KiB).

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58 (desktop: 96). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 144 KiB

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

  • YouTube adds 492 ms

    492 ms

    YouTube costs a phone 492 ms of main-thread work and 960 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 288 ms

    288 ms

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

  • Main-thread work: 2.7 s

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

  • 9 long tasks on the main thread

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

  • Improve image delivery

    178 KiB

    3 images could be 178 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 96 but mobile only 58. 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.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

8 to fix100
  • 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: 15.4 s

    15.4 s

    Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We respect consumer privacy rights by letting visitors opt …”.

  • Time to Interactive: 15.6 s

    15.6 s

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

  • Real-user TTFB: 881 ms

    881 ms

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

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Total Blocking Time: 391 ms

    391 ms

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

  • 15 images without width and height

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

7 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 INP: 113 ms

    113 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

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

    -15%

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

  • Largest content (LCP) got 34% faster for real visitors

    -34%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 2.5 MB in 103 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 103 requests on a phone: scripts 1.4 MB (39), images 833 KiB (39) and stylesheets 114 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    38 KiB

    1 image is downloaded at several times the size a phone draws it, for example dealership-video.jpg at 1,100 px wide, shown at 315 px. Resized copies would save about 38 KiB.

  • 1 image below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.72 g

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

3 to fixGoogle 9394
  • 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.

  • autocomplete attribute must be used correctly (1 element)

    autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10085
  • Title is long (145 characters)

    Your title is 145 characters, so Google will cut it off around 60: “Acura, Buick, Chevrolet, Chrysler, Dodge, GMC, Honda, Jeep, Nissan and Ram Dealer San Ant…”.

  • Meta description is long (227 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), 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.

  • 138 internal links, 33 external

    The homepage links to 138 pages on gunnauto.com and 33 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Welcome to Gunn Automotive Group located in San Antonio, TX”.

  • Canonical URL set

    The canonical URL is https://www.gunnauto.com/.

  • Structured data in place

    Structured data found: AutoDealer, GeoCoordinates, PostalAddress and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://www.gunnauto.com/resrc/xmlsitemap/xml-sitemaps/.

AI search readiness

100
4 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 contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 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.gunnauto.com/finance-application, whose canonical is https://www.gunnauto.com/finance-departments. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.gunnauto.com/finance-application 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 25 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8878
  • 1 broken image

    1 image failed to load on a phone, for example https://www.gunnauto.com/assets/d3303/img/search_lbl.jpg.

  • 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 low-resolution images

    2 images are 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

    26 of 27 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
  • A 9-field form

    Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

  • 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 1,738 words of copy

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

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule Service”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “Shop New Cars”, “Shop New SUVs” and “Shop New Trucks”.

  • Social proof on the page

    Social proof on the homepage: 26 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 3 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.

  • 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
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 14 cookies set on arrival

    14

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 gunnauto.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
Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on gunnauto.com, including 17 speed issues, 3 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