Website review, no card needed

passportbmw.com logo

passportbmw.com website review

Visit site (opens in a new tab)Reviewed 19 October 202638 issues · 90 checks

This review found 38 issues worth fixing on passportbmw.com, 14 of them high impact, across 90 checks. The most urgent: google Tag Manager adds 5.0 s. 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
2.2 s1.4 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
346 ms113 msMay 2Oct 17237 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026203 ms
May 9, 2026204 ms
May 16, 2026196 ms
May 23, 2026191 ms
May 30, 2026201 ms
Jun 6, 2026187 ms
Jun 13, 2026170 ms
Jun 20, 2026155 ms
Jun 27, 2026140 ms
Jul 4, 2026153 ms
Jul 11, 2026170 ms
Jul 18, 2026179 ms
Jul 25, 2026187 ms
Aug 1, 2026194 ms
Aug 8, 2026196 ms
Aug 15, 2026203 ms
Aug 22, 2026205 ms
Aug 29, 2026212 ms
Sep 5, 2026242 ms
Sep 12, 2026303 ms
Sep 19, 2026316 ms
Sep 26, 2026319 ms
Oct 3, 2026296 ms
Oct 10, 2026247 ms
Oct 17, 2026237 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 passportbmw.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. passportbmw.com at 1.8 s1.8 s
  2. passportbmw.com at 3.5 s3.5 s
  3. passportbmw.com at 5.2 s5.2 s
  4. passportbmw.com at 7.0 s7.0 s
  5. passportbmw.com at 8.7 s8.7 s
  6. passportbmw.com at 10.5 s10.5 s
  7. passportbmw.com at 12.2 s12.2 s
  8. passportbmw.com at 14.0 s14.0 s

Speed

12 to fix26
  • Google Tag Manager adds 5.0 s

    5.0 s

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

  • Reduce unused JavaScript

    2.1 s · 3.3 MB

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

  • Use efficient cache lifetimes

    2.2 s · 1.3 MB

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

  • Main-thread work: 16.7 s

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

  • Mobile performance score: 26

    26/100

    Your mobile performance score is 26 (desktop: 60). 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 (Google Tag Manager, dealeron.com and complyauto.com and others), adding 6.1 MB and 7.9 s of main-thread time.

  • dealeron.com adds 974 ms

    974 ms

    dealeron.com costs a phone 974 ms of main-thread work and 108 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 722 ms

    722 ms

    complyauto.com costs a phone 722 ms of main-thread work and 158 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 692 ms. During a long task the page ignores taps.

  • Google Maps adds 396 ms

    396 ms

    Google Maps costs a phone 396 ms of main-thread work and 476 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.

  • ftlaunchpad.ai adds 399 ms

    399 ms

    ftlaunchpad.ai costs a phone 399 ms of main-thread work and 2 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

    388 KiB

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

  • Legacy JavaScript

    150 ms · 24 KiB

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

  • Reduce unused CSS

    97 KiB

    About 97 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 60 but mobile only 26. 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 CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 23 ms

    23 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.1 s

    14.1 s

    Your largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Inventory Search Vehicle Keyword Type New Used Certified Ma…”.

  • Speed Index: 17.0 s

    17.0 s

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

  • Total Blocking Time: 6.1 s

    6.1 s

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

  • Time to Interactive: 57.6 s

    57.6 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • 18 images without width and height

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

  • Tap response (INP) got 19% slower for real visitors

    +19%

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

7 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.2 s

    1.2 s

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

  • Real-user INP: 178 ms

    178 ms

    Real visitors wait 178 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 396 ms

    396 ms

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

2 to fix60
  • Page weight: 10.0 MB in 254 requests

    10.0 MB

    Your homepage downloads 10.0 MB in 254 requests on a phone: scripts 6.4 MB (111), images 2.4 MB (39) and other files 905 KiB (84). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    1 KiB

    3 images are downloaded at several times the size a phone draws them, for example PassportBMW-BA-Homepage04.jpeg at 1,081 px wide, shown at 360 px. Resized copies would save about 1 KiB.

  • 5 images below the first screen load straight away

    5 images further down the page (239 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.8 g of CO₂ per visit

    2.82 g

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

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9695
  • 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.

  • Frames without titles

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  • Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption.

    Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (1 element).

1 checks passed
  • 54 automated accessibility rules passed

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

SEO

3 to fixGoogle 10088
  • 3 H1 headlines

    There are 3 <h1> headlines (“Passport BMW”, “Passport BMW” and “Welcome to Passport BMW”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (AutoDealer and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, 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.

  • 122 internal links, 27 external

    The homepage links to 122 pages on passportbmw.com and 27 external pages.

5 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Visit Passport BMW for all of your BMW needs near Upper Marlboro, MD. Shop cars for sale, browse lease deals, or schedu…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “BMW Dealership Upper Marlboro MD | Waldorf | Alexandria”.

  • Canonical URL set

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

  • 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.passportbmw.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix65
  • 1 page points its canonical at the homepage

    https://www.passportbmw.com/bmwevcharging declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 linked pages hidden from search

    https://www.passportbmw.com/mysavedvehicles and https://www.passportbmw.com/Certified-Pre-Owned.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://www.passportbmw.com/bmwevcharging all use the title “BMW Dealership Upper Marlboro MD | Waldorf | Alexandria”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.passportbmw.com/mysavedvehicles has no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.passportbmw.com/mysavedvehicles, https://www.passportbmw.com/build-your-own, https://www.passportbmw.com/bmw-military-offer, https://www.passportbmw.com/bmw-m-models.html, https://www.passportbmw.com/bmw-electric-vehicles--ev-service.html and https://www.passportbmw.com/bmwi3 and 1 other have 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 47 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “DealerOnTrack is not defined”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    30 of 33 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
  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 759 words of copy

    The homepage carries about 759 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 Appointment” and “Reserve Now”.

  • 27 calls to action

    The homepage has 27 calls to action, for example “Schedule Service Appointment”, “Shop New” and “Shop Electric”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel and Umami.

  • Direct contact links

    Visitors can reach you directly: 4 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
  • 3 trackers load before any consent

    3

    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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 2 of them by other companies (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.

  • 40 other companies contacted

    Loading the homepage contacts 40 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 passportbmw.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

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 passportbmw.com, including 18 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