Website review, no card needed

asbhawaii.com logo

asbhawaii.com website review

Visit site (opens in a new tab)Reviewed 18 November 202643 issues · 87 checks

This review found 43 issues worth fixing on asbhawaii.com, 17 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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.9 s2.6 sMay 30Nov 142.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.7 s
Nov 7, 20262.7 s
Nov 14, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
467 ms396 msMay 30Nov 14437 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026428 ms
Jun 6, 2026432 ms
Jun 13, 2026424 ms
Jun 20, 2026418 ms
Jun 27, 2026412 ms
Jul 4, 2026405 ms
Jul 11, 2026404 ms
Jul 18, 2026405 ms
Jul 25, 2026410 ms
Aug 1, 2026414 ms
Aug 8, 2026425 ms
Aug 15, 2026437 ms
Aug 22, 2026448 ms
Aug 29, 2026454 ms
Sep 5, 2026459 ms
Sep 12, 2026455 ms
Sep 19, 2026447 ms
Sep 26, 2026438 ms
Oct 3, 2026433 ms
Oct 10, 2026431 ms
Oct 17, 2026435 ms
Oct 24, 2026437 ms
Oct 31, 2026435 ms
Nov 7, 2026444 ms
Nov 14, 2026437 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 asbhawaii.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. asbhawaii.com at 0.6 s0.6 s
  2. asbhawaii.com at 1.1 s1.1 s
  3. asbhawaii.com at 1.6 s1.6 s
  4. asbhawaii.com at 2.2 s2.2 s
  5. asbhawaii.com at 2.7 s2.7 s
  6. asbhawaii.com at 3.3 s3.3 s
  7. asbhawaii.com at 3.8 s3.8 s
  8. asbhawaii.com at 4.4 s4.4 s

Speed

11 to fix39
  • Reduce unused JavaScript

    3.6 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

  • Render-blocking requests

    3.7 s

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

  • Use efficient cache lifetimes

    1.6 s · 799 KiB

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

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 1.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 2.7 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, onlineaccess1.com and Google CDN and others), adding 2.9 MB and 2.4 s of main-thread time.

  • Improve image delivery

    900 ms · 584 KiB

    13 images could be 584 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • onlineaccess1.com adds 698 ms

    698 ms

    onlineaccess1.com costs a phone 698 ms of main-thread work and 186 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.

  • Reduce unused CSS

    300 ms · 77 KiB

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

  • Google CDN adds 138 ms

    138 ms

    Google CDN costs a phone 138 ms of main-thread work and 383 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 · 53 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 22 KiB

    22 KiB could be saved by minifying JavaScript.

  • Font display

    100 ms

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

  • Minify CSS

    15 KiB

    15 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: 14 ms

    14 ms

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

Core Web Vitals

10 to fix33
  • 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: 17.9 s

    17.9 s

    Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NO SERVICE FEE. See all the ways we waive the Monthly Servi…”.

  • Time to Interactive: 28.3 s

    28.3 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Total Blocking Time: 766 ms

    766 ms

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 451 ms

    451 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 776 ms

    776 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 7.4 MB in 197 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 197 requests on a phone: scripts 3.1 MB (66), media 2.1 MB (1) and images 1.9 MB (46). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (942 KiB) 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.

  • 7 images below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.10 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9291
  • 1 text element with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • ARIA role should be appropriate for the element (1 element)

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

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

5 to fixGoogle 8581
  • Title is long (90 characters)

    Your title is 90 characters, so Google will cut it off around 60: “Hawaii Banking, Checking, Savings, Mortgages, Loans & Lines | American Savings Bank Hawaii”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“NO SERVICE FEE.” and “Get a great Certificate of Deposit rate!”). One clear main headline is easier for people and search engines.

  • 23 links crawlers can't follow

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 179 internal links, 45 external

    The homepage links to 179 pages on asbhawaii.com and 45 external pages.

5 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “American Savings Bank Hawaii offers consumer and business banking services including checking, savings, CDs, mortgages,…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.asbhawaii.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

4 to fixGoogle 6970
  • 2 broken images

    2 images failed to load on a phone, for example https://www.asbhawaii.com/.

  • 7 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “fbq is not defined”.

  • 10 distorted images

    10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 539 words of copy

    The homepage carries about 539 words of visible text.

5 checks passed
  • 31 calls to action

    The homepage has 31 calls to action, for example “Get Started”, “Skip Get Started” and “Apply for a Mortgage”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (measured from a US location before any click).

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

  • 32 other companies contacted

    Loading the homepage contacts 32 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 asbhawaii.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
Drupal
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Azure

Hiring

Hiring
26 open roles
Job board
adp

Company

Employees
991

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on asbhawaii.com, including 21 speed issues, 5 SEO issues and 3 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