Website review, no card needed
bakernissan.com website review
Visit site (opens in a new tab)Reviewed 25 October 202638 issues · 92 checks
This review found 38 issues worth fixing on bakernissan.com, 15 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.2 s |
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 278 ms |
| May 9, 2026 | 263 ms |
| May 16, 2026 | 253 ms |
| May 23, 2026 | 250 ms |
| May 30, 2026 | 245 ms |
| Jun 6, 2026 | 238 ms |
| Jun 13, 2026 | 235 ms |
| Jun 20, 2026 | 227 ms |
| Jun 27, 2026 | 229 ms |
| Jul 4, 2026 | 246 ms |
| Jul 11, 2026 | 262 ms |
| Jul 18, 2026 | 294 ms |
| Jul 25, 2026 | 319 ms |
| Aug 1, 2026 | 308 ms |
| Aug 8, 2026 | 303 ms |
| Aug 15, 2026 | 296 ms |
| Aug 22, 2026 | 280 ms |
| Aug 29, 2026 | 270 ms |
| Sep 5, 2026 | 263 ms |
| Sep 12, 2026 | 256 ms |
| Sep 19, 2026 | 262 ms |
| Sep 26, 2026 | 260 ms |
| Oct 3, 2026 | 252 ms |
| Oct 10, 2026 | 247 ms |
| Oct 17, 2026 | 238 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
1.3 s
2.5 s
3.8 s
5.1 s
6.3 s
7.6 s
8.9 s
10.1 s
Speed
Reduce unused JavaScript
9.3 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.3 s faster on a phone.
Use efficient cache lifetimes
3.5 s · 1.2 MB29 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Reduce unused CSS
1.1 s · 115 KiBAbout 115 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 11.0 s
A phone's processor spends 11.0 s on main-thread work while loading, 7.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 25
25/100Your mobile performance score is 25 (desktop: 53). 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 (autodriven.com, Google CDN and complyauto.com and others), adding 2.1 MB and 3.0 s of main-thread time.
autodriven.com adds 861 ms
861 msautodriven.com costs a phone 861 ms of main-thread work and 270 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.
Improve image delivery
150 ms · 653 KiB9 images could be 653 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Google CDN adds 572 ms
572 msGoogle CDN costs a phone 572 ms of main-thread work and 734 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 580 ms. During a long task the page ignores taps.
complyauto.com adds 541 ms
541 mscomplyauto.com costs a phone 541 ms of main-thread work and 159 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 316 ms
316 msGoogle Tag Manager costs a phone 316 ms of main-thread work and 461 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.
elfsightcdn.com adds 314 ms
314 mselfsightcdn.com costs a phone 314 ms of main-thread work and 316 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.
Legacy JavaScript
150 ms · 43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 53 but mobile only 25. 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 JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 506 ms
506 msYour server sent the HTML in 506 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 31.0 s
31.0 sYour largest element takes 31.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Get More for Your Trade — Start Your Free Appraisal Today”.
Time to Interactive: 39.5 s
39.5 sThe page becomes fully interactive after 39.5 s. Good is under 3.8 s.
Speed Index: 14.4 s
14.4 sVisually, the page fills in at 14.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.3 s
2.3 sScripts block taps and scrolling for 2.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Real-user INP: 279 ms
279 msReal visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.17
0.17For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 777 ms
777 msReal visitors wait 777 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 278 ms to 238 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.093
0.093The layout barely moves while loading (CLS 0.093, good is under 0.1).
Images and page weight
Page weight: 14.5 MB in 205 requests
14.5 MBYour homepage downloads 14.5 MB in 205 requests on a phone: media 7.1 MB (1), scripts 3.7 MB (103) and images 1.8 MB (25). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
166 KiB1 image is downloaded at several times the size a phone draws it, for example 6ibmwc217drfolo9rlobqqrwiojd at 1,536 px wide, shown at 374 px. Resized copies would save about 166 KiB.
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.1 g of CO₂ per visit
4.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.10 g of CO₂e: 492.1 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
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.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor 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. (3 elements).
2 checks passed
Every image has alt text
All 74 images in the HTML carry an alt attribute.
50 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: 50 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
73 internal links, 3 external
The homepage links to 73 pages on bakernissan.com and 3 external pages.
8 checks passed
Meta description: 106 characters
Your meta description is 106 characters: “Baker Nissan is your Nissan dealer serving Houston, TX, and beyond. Contact us today to take a test drive!”.
One H1 headline
Your main headline reads: “Baker Nissan in Houston, TX”.
Title: 47 characters
Your title is a healthy 47 characters: “Nissan Dealer Serving Houston TX | Baker Nissan”.
Canonical URL set
The canonical URL is https://bakernissan.com/.
Structured data in place
Structured data found: AutoDealer and WebSite.
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://bakernissan.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 3 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
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 (800 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bakernissan.com/llms.txt (45 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://bakernissan.com/hours--directions and https://bakernissan.com/directions all use the title “Baker Nissan Hours & Directions | Nissan Dealer in Houston, TX”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://bakernissan.com/hours--directions and https://bakernissan.com/directions use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://bakernissan.com/hours--directions, whose canonical is https://bakernissan.com/hours-directions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://bakernissan.com/service-schedule, https://bakernissan.com/service-schedule1 and https://bakernissan.com/finance have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://bakernissan.com/service-schedule, https://bakernissan.com/service-schedule1 and https://bakernissan.com/finance 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 21 found) and read each the way a search engine does.
4 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.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
63 of 68 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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,094 words of copy
The homepage carries about 1,094 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” and “Shop New”.
5 calls to action
The homepage has 5 calls to action, for example “Shop New”, “Shop Used” and “Schedule Service”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 8 customer or partner logos and 8 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and 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
2 trackers load before any consent
2Before 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.
19 cookies set on arrival
19Opening 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.
38 other companies contacted
Loading the homepage contacts 38 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 bakernissan.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
- Next.js
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on bakernissan.com, including 23 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.