accor.com website review

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

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

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

49 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

6 third-party services load with your homepage (Google Tag Manager, Optanon and LinkedIn Ads and others), adding 2.1 MB and 114 ms of main-thread time.

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

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

imgix costs a phone 0 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.

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

About 23 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.

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

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 8.6 s on a phone. Good is under 1.8 s.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.0 MB in 117 requests on a phone: images 1.9 MB (59), scripts 1.5 MB (29) and fonts 241 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Your title is only 11 characters: “Accor Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 212 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 179 pages on accor.com and 16 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

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

Large scripts ship without source maps.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

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

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.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

DMARC is set to p=none, so mail pretending to be accor.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Tag Manager and LinkedIn Insight (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 6 cookies (measured from a US location before any click).

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