Website review, no card needed

kahalaresort.com logo

kahalaresort.com website review

Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 88 checks

This review found 39 issues worth fixing on kahalaresort.com, 17 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.8 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.4 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
176 ms122 msMay 9Oct 24166 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026128 ms
May 16, 2026129 ms
May 23, 2026129 ms
May 30, 2026130 ms
Jun 6, 2026135 ms
Jun 13, 2026132 ms
Jun 20, 2026135 ms
Jun 27, 2026137 ms
Jul 4, 2026138 ms
Jul 11, 2026145 ms
Jul 18, 2026147 ms
Jul 25, 2026149 ms
Aug 1, 2026147 ms
Aug 8, 2026154 ms
Aug 15, 2026158 ms
Aug 22, 2026162 ms
Aug 29, 2026170 ms
Sep 5, 2026167 ms
Sep 12, 2026168 ms
Sep 19, 2026169 ms
Sep 26, 2026169 ms
Oct 3, 2026170 ms
Oct 10, 2026168 ms
Oct 17, 2026163 ms
Oct 24, 2026166 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of kahalaresort.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kahalaresort.com at 0.6 s0.6 s
  2. kahalaresort.com at 1.3 s1.3 s
  3. kahalaresort.com at 1.9 s1.9 s
  4. kahalaresort.com at 2.6 s2.6 s
  5. kahalaresort.com at 3.2 s3.2 s
  6. kahalaresort.com at 3.9 s3.9 s
  7. kahalaresort.com at 4.5 s4.5 s
  8. kahalaresort.com at 5.2 s5.2 s

Speed

15 to fix33
  • Render-blocking requests

    4.3 s

    36 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.3 s.

  • Reduce unused JavaScript

    3.1 s · 975 KiB

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

  • Improve image delivery

    2.3 s · 1.4 MB

    16 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 610 KiB

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

  • Mobile performance score: 33

    33/100

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

  • Main-thread work: 5.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and rlets.com and others), adding 2.1 MB and 2.0 s of main-thread time.

  • Reduce unused CSS

    900 ms · 161 KiB

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

  • Google Tag Manager adds 749 ms

    749 ms

    Google Tag Manager costs a phone 749 ms of main-thread work and 728 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.

  • Minify JavaScript

    450 ms · 107 KiB

    107 KiB could be saved by minifying JavaScript.

  • Facebook adds 363 ms

    363 ms

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

  • rlets.com adds 255 ms

    255 ms

    rlets.com costs a phone 255 ms of main-thread work and 289 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.

  • 2,793 HTML elements

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

  • 15 long tasks on the main thread

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

  • myma.ai adds 212 ms

    212 ms

    myma.ai costs a phone 212 ms of main-thread work and 316 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.

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • Font display

    50 ms

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

  • Minify CSS

    14 KiB

    14 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 35.6 s

    35.6 s

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

  • Time to Interactive: 38.9 s

    38.9 s

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

  • First Contentful Paint: 7.6 s

    7.6 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Tap response (INP) got 28% slower for real visitors

    +28%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 172 ms

    172 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix43
  • Page weight: 9.2 MB in 348 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 348 requests on a phone: images 5.4 MB (81), scripts 2.9 MB (97) and stylesheets 369 KiB (69). Under 2 MB keeps phones on slow connections fast.

  • 18 images in older formats

    18 images (2.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 6 images below the first screen load straight away

    6 images further down the page (495 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    9 KiB

    1 image is downloaded at several times the size a phone draws it, for example 2026_CONDE-NAST-TRAVELER_READERS-CHOICE-AWARDS_LOGO_RGB_exp- at 390 px wide, shown at 120 px. Resized copies would save about 9 KiB.

  • About 2.6 g of CO₂ per visit

    2.60 g

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

Accessibility

3 to fixGoogle 9094
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 82 images without alt text

    82 images have no alt text, which hurts accessibility and image search.

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 1 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • No XML sitemap

    No XML sitemap at https://www.kahalaresort.com/sitemap_index.xml, so Google discovers your pages only by following links.

  • 193 internal links, 144 external

    The homepage links to 193 pages on kahalaresort.com and 144 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “The Kahala Hotel & Resort is one of the top Hawaii resorts and luxury hotels in Honolulu. Visit our Honolulu Hotel & Re…”.

  • One H1 headline

    Your main headline reads: “Experience the Legacy of Aloha”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Luxury Hotel in Honolulu, Hawaii | The Kahala Hotel & Resort”.

  • Canonical URL set

    The canonical URL is https://www.kahalaresort.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Hotel, ImageObject, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, description and contact details; logo and sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (5,003 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 3 pages without a meta description

    https://www.kahalaresort.com/our-resort/resort-history, https://www.kahalaresort.com/our-resort/awards-accolades and https://www.kahalaresort.com/special-packages/the-kahala-signature-experience have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    8 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5469
  • 4 broken images

    4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5902311&Ver=2&mid=df4951cb-74c6-41cb-960c-a9b14fade058&sid=3bc038907fa211ed86f75f49e7a83353&vid=80d07ab07b4911ed92cadf9215540f14&vids=0&msclkid=N&uach=pv%3D10.0.0&pi=9.

  • 11 third-party cookies

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

  • 4 small tap targets

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

  • Deprecated browser APIs

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • No call to action on the first screen

    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 opening hours

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

  • About 646 words of copy

    The homepage carries about 646 words of visible text.

8 checks passed
  • 26 calls to action

    The homepage has 26 calls to action, for example “RESERVE NOW”, “BOOK NOW” and “Contact Information”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 customer or partner logos and 7 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies (measured from a US location before any click).

  • 57 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at kahalaresort.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
WP Engine

Company

Employees
110

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on kahalaresort.com, including 24 speed issues, 1 SEO issue and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25