Website review, no card needed
sellersford.com website review
Visit site (opens in a new tab)Reviewed 22 October 202634 issues · 88 checks
This review found 34 issues worth fixing on sellersford.com, 13 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 146 ms |
| May 9, 2026 | 148 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 160 ms |
| Jun 6, 2026 | 159 ms |
| Jun 13, 2026 | 169 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 166 ms |
| Jul 4, 2026 | 168 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 156 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 169 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 153 ms |
| Sep 26, 2026 | 150 ms |
| Oct 3, 2026 | 158 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 158 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.4 s
5.1 s
Speed
Use efficient cache lifetimes
8.8 s · 2.5 MB24 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).
Improve image delivery
6.5 s · 1.7 MB13 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 6.5 s faster on a phone.
Reduce unused JavaScript
2.9 s · 516 KiBAbout 516 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Render-blocking requests
1.6 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 35
35/100Your mobile performance score is 35 (desktop: 30). 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 (secureoffersites.com, complyauto.com and Google Tag Manager and others), adding 4.8 MB and 1.6 s of main-thread time.
secureoffersites.com adds 519 ms
519 mssecureoffersites.com costs a phone 519 ms of main-thread work and 2.8 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.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 335 ms. During a long task the page ignores taps.
complyauto.com adds 316 ms
316 mscomplyauto.com costs a phone 316 ms of main-thread work and 157 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 247 ms
247 msGoogle Tag Manager costs a phone 247 ms of main-thread work and 844 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 adds 221 ms
221 mspodium.com costs a phone 221 ms of main-thread work and 539 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.
Reduce unused CSS
150 ms · 45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 29 KiB29 KiB could be saved by minifying JavaScript.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
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: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 23.7 s
23.7 sYour largest element takes 23.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “rotational banner”.
Time to Interactive: 23.7 s
23.7 sThe page becomes fully interactive after 23.7 s. Good is under 3.8 s.
First Contentful Paint: 6.2 s
6.2 sThe first text or image appears after 6.2 s on a phone. Good is under 1.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s 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.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 146 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 99 ms
99 msReal visitors wait 99 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 511 ms
511 msReal visitors wait 511 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 92 requests
4.9 MBYour homepage downloads 4.9 MB in 92 requests on a phone: images 2.3 MB (17), scripts 2.0 MB (33) and fonts 371 KiB (8). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.
13 images in older formats
13 images (2.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
2 images below the first screen load straight away
2 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 167.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (AutoBodyShop, AutoDealer, AutoPartsStore and AutoRepair) but with 1 problem, for example “ld+json block 3 is not valid JSON (Bad control character in string literal in JSON at position )”.
10 links crawlers can't follow
10 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 set, so this is minor.
39 internal links, 3 external
The homepage links to 39 pages on sellersford.com and 3 external pages.
7 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Discover top-quality new and used cars, trucks, and SUVs at our Ford dealership in Troy, MI, just north of Detroit. You…”.
One H1 headline
Your main headline reads: “Welcome to the Family: Our Ford Dealership in Troy, MI”.
Title: 64 characters
Your title is a healthy 64 characters: “Ford Dealer in Troy, MI | New and Used Cars North of Detroit, MI”.
Canonical URL set
The canonical URL is https://www.sellersford.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.sellersford.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,960 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.sellersford.com/llms.txt (8 KiB, 45 links), a plain-text guide to the site for AI tools.
Other pages
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.sellersford.com/ford-dealership-detroit-mi, whose canonical is //ford-dealership-detroit-mi. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages with very little text
https://www.sellersford.com/getfinancing, https://www.sellersford.com/scheduleservice and https://www.sellersford.com/shopperwizard/mytradevalue have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,560 words of copy
The homepage carries about 1,560 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”.
16 calls to action
The homepage has 16 calls to action, for example “Schedule Service”, “Schedule” and “Shop Now”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
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.
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
3 trackers load before any consent
3Before 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.
14 cookies set on arrival
14Opening 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.
24 other companies contacted
Loading the homepage contacts 24 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 sellersford.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
- Tailwind CSS
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on sellersford.com, including 18 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.