enterprise.com website review

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

About 986 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.0 s faster on a phone.

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

Your mobile performance score is 39 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Optanon and others), adding 2.0 MB and 1.2 s of main-thread time.

About 209 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

Google Tag Manager costs a phone 542 ms of main-thread work and 748 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 CDN costs a phone 303 ms of main-thread work and 733 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.

The page has 2,899 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

15 long tasks block the main thread while loading, the longest for 210 ms. During a long task the page ignores taps.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

Desktop scores 65 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 21.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 213 requests on a phone: scripts 3.4 MB (105), other files 494 KiB (37) and images 369 KiB (46). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

2 tap targets are too small or too close together to hit reliably with a finger.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 element has a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (5 elements).

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 219 pages on enterprise.com and 93 external pages.

Your robots.txt lets 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.

/en/car-rental-by-month-subscription.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/en/car-rental-faqs, /content/experience-fragments/ecom/en/header/master.html, /en/car-rental.html, /en/car-rental/deals.html and /en/car-rental/one-way.html have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /en/help/contact, whose canonical is /en/help/contact.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/content/experience-fragments/ecom/en/header/master.html, /en/reserve/view-modify-cancel.html and /en/reserve/receipts.html have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5947341&tm=gtm002&Ver=2&mid=cce410d6-d99a-4ba1-af39-91656f3b213a&bo=2&sid=49435190c5bd11f181a44fad0637bb9a&vid=49438310c5bd11f18c441bf42cf8ef68&vids=1&msclkid=N&pi=918.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “SCHEMA WARNING: value failed schema validator. [object Object]”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

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

2 links go through two or more redirects, for example https://www.enterprise.com/en/help/contact.

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

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

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

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

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 530 words of visible text.

enterprise.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 2 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.

Opening the homepage sets 31 cookies, 3 of them by other companies (measured from a US location before any click).

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