Six response headers every browser and security scanner checks for. They are set once at the server and cost nothing to add. Anyone can verify this list in about ten seconds with curl.
This site could not be reached when we ran the check, so its headers were not measured. It is not recorded as failing.
Performance, SEO and accessibility
Measured with Google Lighthouse on a mobile connection. These four are Google's own categories and anyone can reproduce them.
Performance
43/100
How quickly the page becomes usable on a phone, which is where most local searches happen.
SEO
100/100
Whether search engines can read what this business does and where it does it.
Accessibility
88/100
Whether someone using a screen reader or a keyboard can get through the site.
Best Practices
77/100
Errors and insecure requests a modern browser flags behind the scenes.
The specific shortfalls
Performance Total Blocking Time 2,420 ms
Performance First Contentful Paint 3.9 s
Performance Speed Index 6.6 s
Performance Largest Contentful Paint 4.4 s
Best Practices Uses deprecated APIs 1 warning found
Best Practices Browser errors were logged to the console
Accessibility Buttons do not have an accessible name
Accessibility Links do not have a discernible name
Accessibility Touch targets do not have sufficient size or spacing.
Accessibility Heading elements are not in a sequentially-descending order
Want these fixed, not just flagged?
We rebuild sites clean, and we do not stop until every category comes back green, including all six security headers, or your money back. You own everything, no lock-in.
We measure a public website only. This says nothing about how Expedia handles data internally, and nothing here is a statement about any incident. Headers were read with a single request following redirects on September 1, 2026.