avis.com website review

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

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

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

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

About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

42 files are served with short cache lifetimes, so returning visitors download them again (976 KiB).

Optanon costs a phone 938 ms of main-thread work and 304 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 block the main thread while loading, the longest for 740 ms. During a long task the page ignores taps.

Facebook costs a phone 615 ms of main-thread work and 307 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.

Quantum Metric costs a phone 520 ms of main-thread work and 119 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.

rokt-api.com costs a phone 491 ms of main-thread work and 379 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.

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

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

38 KiB JavaScript is shipped twice across bundles.

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

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

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.

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

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

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

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “avis-globalweb-firstv2r2-1440x720.jpg”.

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

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

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

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

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

Your homepage downloads 5.6 MB in 248 requests on a phone: scripts 4.8 MB (97), images 270 KiB (40) and other files 187 KiB (89). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

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

The homepage links to 118 pages on avis.com and 5 external pages.

/en/offers/us-offers/low-rates-suvs has no <title>, so Google invents the link text in results.

/en/reservation/precheck is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/en/reservation/view-modify-cancel and /en/reservation/precheck have no meta description, so Google writes the search snippet from whatever text it finds.

/en/reservation/view-modify-cancel, /en/reservation/precheck and /en/reservation/ereceipt have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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

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.

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

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

avis.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 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 865 words of visible text.

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

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 Meta Pixel 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 19 cookies (measured from a US location before any click).

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