Website review, no card needed

hbhospital.org logo

hbhospital.org website review

Visit site (opens in a new tab)Reviewed 29 October 202632 issues · 82 checks

This review found 32 issues worth fixing on hbhospital.org, 18 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
5.1 s3.0 sMay 9Oct 243.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.6 s
May 16, 20263.3 s
May 23, 20263.2 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.8 s
Jun 20, 20264.4 s
Jun 27, 20264.8 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20264.4 s
Jul 25, 20264.2 s
Aug 1, 20264.5 s
Aug 8, 20264.5 s
Aug 15, 20264.5 s
Aug 22, 20264.3 s
Aug 29, 20264.3 s
Sep 5, 20264.2 s
Sep 12, 20264.3 s
Sep 19, 20264.6 s
Sep 26, 20264.6 s
Oct 3, 20264.3 s
Oct 10, 20263.8 s
Oct 17, 20263.7 s
Oct 24, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
109 ms66 msMay 9Oct 2478 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202671 ms
May 16, 202679 ms
May 23, 202676 ms
May 30, 202675 ms
Jun 20, 202671 ms
Jun 27, 202677 ms
Jul 4, 202677 ms
Jul 11, 202682 ms
Jul 18, 202691 ms
Jul 25, 202693 ms
Aug 1, 2026104 ms
Aug 8, 202687 ms
Aug 15, 202684 ms
Aug 22, 202680 ms
Aug 29, 202677 ms
Sep 5, 202675 ms
Sep 12, 202675 ms
Sep 19, 202681 ms
Sep 26, 202680 ms
Oct 3, 202680 ms
Oct 10, 202679 ms
Oct 17, 202677 ms
Oct 24, 202678 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 hbhospital.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hbhospital.org at 0.4 s0.4 s
  2. hbhospital.org at 0.9 s0.9 s
  3. hbhospital.org at 1.3 s1.3 s
  4. hbhospital.org at 1.7 s1.7 s
  5. hbhospital.org at 2.1 s2.1 s
  6. hbhospital.org at 2.6 s2.6 s
  7. hbhospital.org at 3.0 s3.0 s
  8. hbhospital.org at 3.4 s3.4 s

Speed

6 to fix35
  • Use efficient cache lifetimes

    3.9 s · 2.1 MB

    95 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

  • Improve image delivery

    2.4 s · 3.4 MB

    19 images could be 3.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.4 s faster on a phone.

  • Render-blocking requests

    3.3 s

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

  • Reduce unused JavaScript

    1.1 s · 161 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Reduce unused CSS

    300 ms · 102 KiB

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

  • Font display

    250 ms

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

  • Legacy JavaScript

    150 ms · 18 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (steerhealth.io, trustindex.io and userway.org and others), adding 832 KiB and 80 ms of main-thread time.

  • 2 long tasks on the main thread

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

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 454 ms of it running JavaScript. That is comfortably low.

  • Server response: 61 ms

    61 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 23.9 s

    23.9 s

    Your largest element takes 23.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FastTrackCareReserve Your ER Arrival…”.

  • Time to Interactive: 24.9 s

    24.9 s

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

  • Cumulative Layout Shift: 0.978

    0.978

    The layout shifts by 0.978 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

  • Speed Index: 7.6 s

    7.6 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • 15 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

3 checks passed
  • Real-user INP: 78 ms

    78 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 9 ms

    9 ms

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

Images and page weight

5 to fix18
  • Page weight: 5.7 MB in 118 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 118 requests on a phone: images 4.6 MB (52), fonts 524 KiB (9) and scripts 414 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 10 images far larger than shown

    2.6 MB

    10 images are downloaded at several times the size a phone draws them, for example HF5STAR.png at 7,017 px wide, shown at 242 px. Resized copies would save about 2.6 MB.

  • 2 images over 500 KB

    2 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

  • 17 images in older formats

    17 images (3.6 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.

  • 14 images below the first screen load straight away

    14 images further down the page (3.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.63 g

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

Accessibility

2 to fixGoogle 9797
  • 3 text elements with low contrast

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 83 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9289
  • 12 H1 headlines

    There are 12 <h1> headlines (“FastTrackCare”, “Emergency Department Accreditation” and “MyChart Patient Portal”). One clear main headline is easier for people and search engines.

  • 30 links with vague text

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

  • Structured data has 8 problems

    Structured data found (AboutPage, ContactPage, Hospital and ImageObject) but with 8 problems, for example “WebSite: missing name”.

  • 112 internal links, 13 external

    The homepage links to 112 pages on hbhospital.org and 13 external pages.

6 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Huntington Beach Hospital offers emergency, surgical, and specialty care services. Serving Huntington Beach and surroun…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Huntington Beach Hospital | Trusted Care in Orange County”.

  • Canonical URL set

    The canonical URL is https://hbhospital.org/.

  • 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://hbhospital.org/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (1,345 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://hbhospital.org/carecredit, whose canonical is https://hbhospital.org/patients-visitors/carecredit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    https://hbhospital.org/find-a-provider has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 6 pages slow to respond

    https://hbhospital.org/find-a-provider, https://hbhospital.org/careers, https://hbhospital.org/about-us, https://hbhospital.org/carecredit, https://hbhospital.org/medical-records and https://hbhospital.org/why-prime-healthcare took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9697
  • 9 distorted images

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    17 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 955 words of visible text.

6 checks passed
  • 29 calls to action

    The homepage has 29 calls to action, for example “Learn More”, “Contact Us” and “Call Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks, a star rating and 42 trust badges.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (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.

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 hbhospital.org, 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
Hosting
Sucuri

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on hbhospital.org, including 16 speed issues, 3 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