Website review, no card needed

hawaii-guide.com logo

hawaii-guide.com website review

Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 84 checks

This review found 33 issues worth fixing on hawaii-guide.com, 11 of them high impact, across 84 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
1.7 s1.6 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
141 ms115 msMay 16Oct 31118 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026124 ms
May 23, 2026128 ms
May 30, 2026132 ms
Jun 6, 2026130 ms
Jun 13, 2026137 ms
Jun 20, 2026137 ms
Jun 27, 2026137 ms
Jul 4, 2026138 ms
Jul 11, 2026131 ms
Jul 18, 2026129 ms
Jul 25, 2026127 ms
Aug 1, 2026129 ms
Aug 8, 2026129 ms
Aug 15, 2026130 ms
Aug 22, 2026129 ms
Aug 29, 2026124 ms
Sep 5, 2026121 ms
Sep 12, 2026123 ms
Sep 19, 2026122 ms
Sep 26, 2026124 ms
Oct 3, 2026124 ms
Oct 10, 2026121 ms
Oct 17, 2026121 ms
Oct 24, 2026120 ms
Oct 31, 2026118 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 hawaii-guide.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hawaii-guide.com at 0.6 s0.6 s
  2. hawaii-guide.com at 1.2 s1.2 s
  3. hawaii-guide.com at 1.9 s1.9 s
  4. hawaii-guide.com at 2.5 s2.5 s
  5. hawaii-guide.com at 3.1 s3.1 s
  6. hawaii-guide.com at 3.7 s3.7 s
  7. hawaii-guide.com at 4.3 s4.3 s
  8. hawaii-guide.com at 5.0 s5.0 s

Speed

11 to fix60
  • Render-blocking requests

    1.9 s

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

  • Improve image delivery

    1.3 s · 414 KiB

    10 images could be 414 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cloudflare and hawaiiguide.io and others), adding 9.3 MB and 238 ms of main-thread time.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • hawaiiguide.io adds 10 ms

    10 ms

    hawaiiguide.io costs a phone 10 ms of main-thread work and 8.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.

  • Reduce unused JavaScript

    620 ms · 138 KiB

    About 138 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 620 ms faster on a phone.

  • Reduce unused CSS

    310 ms · 69 KiB

    About 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • 2,471 HTML elements

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

  • Google Tag Manager adds 207 ms

    207 ms

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

  • Main-thread work: 2.4 s

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

  • Adobe TypeKit adds 0 ms

    0 ms

    Adobe TypeKit costs a phone 0 ms of main-thread work and 306 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

    160 ms · 44 KiB

    44 KiB could be saved by minifying JavaScript.

  • Minify CSS

    160 ms · 32 KiB

    32 KiB could be saved by minifying CSS.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    50 ms · 21 KiB

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

  • Use efficient cache lifetimes

    50 ms · 8 KiB

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

  • Font display

    50 ms

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

  • 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: 29 ms

    29 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 49.4 s

    49.4 s

    Your largest element takes 49.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aloha KAUAʻI OʻAHU MAUI HAWAIʻI”.

  • Time to Interactive: 49.9 s

    49.9 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Total Blocking Time: 104 ms

    104 ms

    Scripts block the page for only 104 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 10.2 MB in 156 requests

    10.2 MB

    Your homepage downloads 10.2 MB in 156 requests on a phone: media 6.1 MB (2), images 2.6 MB (33) and scripts 608 KiB (55). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    76 KiB

    2 images are downloaded at several times the size a phone draws them, for example hawaii-guide-intro-sound-20260702-v2-poster.jpg at 1,280 px wide, shown at 358 px. Resized copies would save about 76 KiB.

  • 1 image in older formats

    1 image (141 KiB) is 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.

  • About 2.9 g of CO₂ per visit

    2.88 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 9491
  • 30 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    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 (17 elements)

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → 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. (21 elements).

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 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 9298
  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • 374 internal links, 19 external

    The homepage links to 374 pages on hawaii-guide.com and 19 external pages.

8 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Plan your Hawaii vacation with our complete travel guide. Beaches, hiking, tours, hotels, and local tips for Oahu, Maui…”.

  • One H1 headline

    Your main headline reads: “Hawaii Travel Guide”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Hawaii Travel Guide 2026 — Best Islands, Things to Do & Tips”.

  • Canonical URL set

    The canonical URL is https://www.hawaii-guide.com/.

  • Structured data in place

    Structured data found: Article, AudioObject, CreativeWork, FAQPage and ItemList.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.hawaii-guide.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.hawaii-guide.com/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.

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 page without an H1

    https://www.hawaii-guide.com/today has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    37 of 39 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,314 words of copy

    The homepage carries about 1,314 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Best Time to Book”, “Book stays, tours, cars” and “Start planning →”.

  • 5 short forms

    5 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Plausible and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 11 other companies contacted

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

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 hawaii-guide.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager | Plausible
Hosting
Cloudflare

Company

Headquarters
Honolulu

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on hawaii-guide.com, including 16 speed issues, 1 SEO issue and 2 conversion gaps. 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