Brazil · Sao Paulo Completed: Apr 7, 2026 20:08 UTCMobile 375 × 812
Score: 69 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Cookie 'bm_sz' is missing the Secure flag
No Content-Security-Policy header found
No favicon or icon links detected
232 HTTP requests — consider bundling or reducing
[](https://beavercheck.com/results/94009c4a-430f-5933-591c-94550f6f1ea1)<a href="https://beavercheck.com/results/94009c4a-430f-5933-591c-94550f6f1ea1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.hilton.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.hilton.comThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
3.05 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.89 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
5.60 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.05 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
33.74 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
| URL | Transfer Size | Duration |
|---|---|---|
| js-cdn.dynatrace.com/jstag/157944990f8/ruxitagent_ICASVfhu_10181191119154660.js | 67.1 KiB | 1.1 s |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| URL | Time Spent |
|---|---|
| www.hilton.com/ | 776 ms |
| www.hilton.com/en/ | 3.6 s |
| www.hilton.com/en/ | 0.0 ms |
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
| Category | Time Spent |
|---|---|
| Script Evaluation | 8.5 s |
| Script Parsing & Compilation | 1.3 s |
| Other | 1.3 s |
| Style & Layout | 293 ms |
| Garbage Collection | 105 ms |
| Parse HTML & CSS | 91 ms |
| Rendering | 59 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
| Failure reason | Failure type |
|---|---|
| Only pages with a status code of 2XX can be cached. | Not actionable |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
| URL | Transfer Size | Est Savings |
|---|---|---|
| @font-face { font-family: 'Brand-Bar-Color'; src: url('https://s3.amazonaws.com/icomoon.io/6720… | 39.5 KiB | 4.7 KiB |
| html { color: #222; font-size: 1em; line-height: 1.4 } … | 8.5 KiB | 3.5 KiB |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
| URL | Transfer Size | Est Savings |
|---|---|---|
| @font-face { font-family: 'Brand-Bar-Color'; src: url('https://s3.amazonaws.com/icomoon.io/6720… | 29.5 KiB | 20.8 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
SOMETHING WENT WRONG body > section.cp-content > div.cp-content__top > h1 |
Hilton.com section.cp-content > div.cp-content__bottom > p > a |
Customer Service section.cp-content > div.cp-content__bottom > p > a |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
| Failing Elements |
|---|
html.no-js html.no-js |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
| Failing Elements |
|---|
body > header > div.inner-width-2 > img body > header > div.inner-width-2 > img |
ul > li.liadchoices > a > img ul > li.liadchoices > a > img |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
| Failing Elements |
|---|
footer.inner-width > div.brand-block > div.brand-block__hilton-logo > a footer.inner-width > div.brand-block > div.brand-block__hilton-logo > a |
div.secondary-footer-links > ul > li.liadchoices > a div.secondary-footer-links > ul > li.liadchoices > a |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
| Failing Elements |
|---|
العربية div.primary-footer-links > ul > li > a |
Български div.primary-footer-links > ul > li > a |
繁體中文 div.primary-footer-links > ul > li > a |
Česky div.primary-footer-links > ul > li > a |
Dansk div.primary-footer-links > ul > li > a |
Nederlands div.primary-footer-links > ul > li > a |
Suomi div.primary-footer-links > ul > li > a |
Français div.primary-footer-links > ul > li > a |
Italiano div.primary-footer-links > ul > li > a |
日本語 div.primary-footer-links > ul > li > a |
한국어 div.primary-footer-links > ul > li > a |
Norsk div.primary-footer-links > ul > li > a |
Polski div.primary-footer-links > ul > li > a |
Español div.primary-footer-links > ul > li > a |
ไทย div.primary-footer-links > ul > li > a |
Türkçe div.primary-footer-links > ul > li > a |
Svenska div.primary-footer-links > ul > li.last > a |
Hilton div.secondary-footer-links > ul > li > a |
Careers div.secondary-footer-links > ul > li > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
| Failing Elements |
|---|
html.no-js html.no-js |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | www.googletagmanager.com/gtag/js?id=AW-971189347&cx=c>m=4e6460 line 593, col 244 |
| Topics | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
| Source | Description |
|---|---|
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 451 () |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
| Failing Elements |
|---|
body > header > div.inner-width-2 > img body > header > div.inner-width-2 > img |
ul > li.liadchoices > a > img ul > li.liadchoices > a > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
To appear in search results, crawlers need access to your app.
Desktop audit not available for this result.
Send Feedback