budget.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 2.6 s

  2.6 s

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

• Real-user INP: 270 ms

  270 ms

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

• Real-user CLS: 0.12

  0.12

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

• Tap response (INP) held steady for real visitors

  0%

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

• Largest content (LCP) held steady for real visitors

  +1%

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

• Page weight: 5.5 MB

  5.5 MB

  Your homepage downloads 5.5 MB on a phone, 902 KiB of it images (16%). Under 2 MB keeps phones on slow connections fast.

• 3 images in older formats

  3 images (400 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.

  Elements (3)

• About 1.6 g of CO₂ per visit

  1.56 g

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

• Unlabelled dropdowns

  2 dropdowns have no label.

  Elements (2)

• Malformed lists

  Some lists contain elements other than list items, which screen readers announce wrongly.

  Elements (3)

• 2 text elements with low contrast

  2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (2)

• Positive tabindex

  2 elements have a tabindex above 0, which scrambles the keyboard order.

  Elements (2)

• ARIA dialog and alertdialog nodes should have an accessible name (1 element)

  ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Elements must only use permitted ARIA attributes (1 element)

  Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 2 images without alt text

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

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

  Elements (3)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Zoom is disabled

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

  Elements (1)

• 10 form fields without a label

  10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  View source

• 2 links without text

  2 visible links have no text or label, so screen readers cannot say where they go.

  Elements (2)

• Headings should not be empty (5 elements)

  Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings skip levels

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

  View sourceElements (2)

• Title is long (66 characters)

  Your title is 66 characters, so Google will cut it off around 60: “Discount car rental rates and rental car deals | Budget Car Rental”.

  View source

• 2 H1 headlines

  There are 2 <h1> headlines (“Car Rental from Budget, Book Online Now & Save Ca…” and “Car Rental from Budget, Book Online Now & Save”). One clear main headline is easier for people and search engines.

• 118 internal links, 16 external

  The homepage links to 118 pages on budget.com and 16 external pages.

• No llms.txt

  There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

• 15 internal pages checked

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

• 4 broken images

  4 images failed to load on a phone, for example https://www.budget.com/en/home.

• 16 small tap targets

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

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “ dro-error: [2026-10-12 6:58:38.391] : Cannot read properties of undefined (reading '20')”.

• 2 redirects before the homepage

  Opening https://budget.com goes through 2 redirects before the homepage loads.

• 3 links through redirect chains

  3 links go through two or more redirects, for example https://itunes.apple.com/app/budget-car-rental-reserve-then/id538787758?mt=8.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  budget.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  budget.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• Local business without LocalBusiness data

  Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  View source

• Thin social proof

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

• A 31-field form

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

  View source

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

  The homepage carries about 467 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• Domain receives no email

  budget.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

• Email authentication score: 100/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 8 trackers load before any consent

  8

  Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 27 cookies set on arrival

  27

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

• 51 other companies contacted

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