Website review, no card needed
teddynissan.com website review
Visit site (opens in a new tab)Reviewed 3 November 202635 issues · 86 checks
This review found 35 issues worth fixing on teddynissan.com, 10 of them high impact, across 86 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 188 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 223 ms |
| Jul 25, 2026 | 222 ms |
| Aug 1, 2026 | 221 ms |
| Aug 8, 2026 | 208 ms |
| Aug 15, 2026 | 196 ms |
| Aug 22, 2026 | 204 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 213 ms |
| Sep 19, 2026 | 218 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 263 ms |
| Oct 10, 2026 | 283 ms |
| Oct 17, 2026 | 292 ms |
| Oct 24, 2026 | 300 ms |
| Oct 31, 2026 | 271 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
4.4 s
8.7 s
13.1 s
17.5 s
21.9 s
26.2 s
30.6 s
35.0 s
Speed
Reduce unused JavaScript
1.2 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, edmunds.com and secureoffersites.com and others), adding 4.2 MB and 2.2 s of main-thread time.
Use efficient cache lifetimes
700 ms · 1.4 MB28 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Improve image delivery
100 ms · 979 KiB12 images could be 979 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Google Tag Manager adds 866 ms
866 msGoogle Tag Manager costs a phone 866 ms of main-thread work and 1.7 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
850 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 587 ms. During a long task the page ignores taps.
secureoffersites.com adds 374 ms
374 mssecureoffersites.com costs a phone 374 ms of main-thread work and 1.9 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.
edmunds.com adds 433 ms
433 msedmunds.com costs a phone 433 ms of main-thread work and 11 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 252 ms
252 mscomplyauto.com costs a phone 252 ms of main-thread work and 156 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.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 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.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 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.
Time to Interactive: 26.5 s
26.5 sThe page becomes fully interactive after 26.5 s. Good is under 3.8 s.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s.
Total Blocking Time: 681 ms
681 msScripts block taps and scrolling for 681 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 63% slower for real visitors
+63%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 162 ms to 271 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 89% slower for real visitors
+89%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
5 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (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: 518 ms
518 msReal visitors wait 518 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.024
0.024The layout barely moves while loading (CLS 0.024, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 118 requests
4.5 MBYour homepage downloads 4.5 MB in 118 requests on a phone: scripts 3.0 MB (61), images 1.2 MB (19) and fonts 182 KiB (3). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (548 KiB) 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.
About 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 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.
5 links without text
5 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.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
42 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: 42 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
71 links crawlers can't follow
71 links have no real href, so search engines can't follow them.
Structured data has 1 problem
Structured data found (AutoDealer, GeoCoordinates, ImageObject and Offer) but with 1 problem, for example “ld+json block 3 is not valid JSON (Bad control character in string literal in JSON at position )”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
19 internal links, 0 external
The homepage links to 19 pages on teddynissan.com and 0 external pages.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Visit Teddy Nissan in the Bronx, NY, and explore new Nissan models, quality pre-owned vehicles, expert service, and fle…”.
One H1 headline
Your main headline reads: “A Trusted Nissan Dealership in the Bronx, NY”.
Title: 65 characters
Your title is a healthy 65 characters: “Nissan Dealership in Bronx, NY | New and Used Cars | Teddy Nissan”.
Canonical URL set
The canonical URL is https://www.teddynissan.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.teddynissan.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,943 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.teddynissan.com/llms.txt (7 KiB, 34 links), a plain-text guide to the site for AI tools.
Other pages
5 pages with very little text
https://www.teddynissan.com/scheduleservice, https://www.teddynissan.com/shopperwizard/mytradevalue, https://www.teddynissan.com/scheduletestdrive, https://www.teddynissan.com/getfinancing and https://www.teddynissan.com/contactus 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.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 11 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 11 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 11 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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,481 words of copy
The homepage carries about 1,481 words of visible text.
7 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 “Apply for Financing”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 3 mores (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
32 other companies contacted
Loading the homepage contacts 32 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 teddynissan.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 | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on teddynissan.com, including 22 speed issues, 2 SEO issues and 2 conversion gaps. 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.