mossyford.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, complyauto.com and Google CDN and others), adding 5.0 MB and 2.2 s of main-thread time.

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

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

Google CDN costs a phone 233 ms of main-thread work and 2.0 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.

About 121 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 costs a phone 349 ms of main-thread work and 128 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.

podium.com costs a phone 189 ms of main-thread work and 641 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.

Amplitude Mobile Analytics costs a phone 71 ms of main-thread work and 435 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 29.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site deploys cookies and similar tracking technologies…”.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 16.0 MB in 128 requests on a phone: media 11.9 MB (3), scripts 3.0 MB (49) and other files 388 KiB (37). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example dfe7dd984cc0aaed6d42a6406bb81de0.svg at 765 px wide, shown at 51 px. Resized copies would save about 70 KiB.

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

2 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Structured data found ((untyped), AutoDealer, LocalBusiness and WebSite) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 63 pages on mossyford.com and 7 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.mossyford.com/about-us has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mossyford.com/sell-us-your-car, https://www.mossyford.com/inventory/used and https://www.mossyford.com/specials/new-vehicles took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.

10 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 265 words of visible text.

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.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.