Website review, no card needed

uscarcadiahospital.org logo

uscarcadiahospital.org website review

Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 88 checks

This review found 38 issues worth fixing on uscarcadiahospital.org, 16 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
3.5 s2.8 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.3 s
Jul 18, 20263.1 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
103 ms95 msMay 16Oct 31102 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202696 ms
May 23, 202697 ms
May 30, 202697 ms
Jun 6, 202698 ms
Jun 13, 2026100 ms
Jun 20, 2026100 ms
Jun 27, 2026101 ms
Jul 4, 2026102 ms
Jul 11, 2026101 ms
Jul 18, 2026101 ms
Jul 25, 2026101 ms
Aug 1, 2026102 ms
Aug 8, 2026102 ms
Aug 15, 2026101 ms
Aug 22, 202699 ms
Aug 29, 202699 ms
Sep 5, 202699 ms
Sep 12, 2026100 ms
Sep 19, 2026100 ms
Sep 26, 2026100 ms
Oct 3, 202699 ms
Oct 10, 202698 ms
Oct 17, 2026101 ms
Oct 24, 2026102 ms
Oct 31, 2026102 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 uscarcadiahospital.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. uscarcadiahospital.org at 0.5 s0.5 s
  2. uscarcadiahospital.org at 1.0 s1.0 s
  3. uscarcadiahospital.org at 1.4 s1.4 s
  4. uscarcadiahospital.org at 1.9 s1.9 s
  5. uscarcadiahospital.org at 2.4 s2.4 s
  6. uscarcadiahospital.org at 2.9 s2.9 s
  7. uscarcadiahospital.org at 3.4 s3.4 s
  8. uscarcadiahospital.org at 3.8 s3.8 s

Speed

11 to fix34
  • Render-blocking requests

    4.1 s

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

  • YouTube adds 1.6 s

    1.6 s

    YouTube costs a phone 1.6 s of main-thread work and 3.9 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.

  • Reduce unused CSS

    1.4 s · 429 KiB

    About 429 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 6.5 s

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

  • Reduce unused JavaScript

    600 ms · 2.6 MB

    About 2.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Optimizely and others), adding 5.5 MB and 2.6 s of main-thread time.

  • Improve image delivery

    650 ms · 958 KiB

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

  • Google Tag Manager adds 396 ms

    396 ms

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

  • FontAwesome CDN adds 156 ms

    156 ms

    FontAwesome CDN costs a phone 156 ms of main-thread work and 452 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.

  • Google Maps adds 96 ms

    96 ms

    Google Maps costs a phone 96 ms of main-thread work and 320 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.

  • 20 long tasks on the main thread

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

  • Minify CSS

    150 ms · 36 KiB

    36 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    174 KiB

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

  • Legacy JavaScript

    150 ms · 22 KiB

    Polyfills for old browsers add 22 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 JavaScript

    27 KiB

    27 KiB could be saved by minifying JavaScript.

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

    23 ms

    Your server sent the HTML in 23 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 TTFB: 2.2 s

    2.2 s

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

  • Time to Interactive: 43.6 s

    43.6 s

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

  • Speed Index: 15.0 s

    15.0 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • First Contentful Paint: 4.3 s

    4.3 s

    The first text or image appears after 4.3 s on a phone. Good is under 1.8 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.

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.8 s

    2.8 s

    Real visitors see the first content after 2.8 s (75th percentile). 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 96 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -9%

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

3 checks passed
  • Real-user INP: 88 ms

    88 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Cumulative Layout Shift: 0.059

    0.059

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

Images and page weight

4 to fix33
  • Page weight: 8.4 MB in 197 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 197 requests on a phone: scripts 4.9 MB (71), images 1.7 MB (37) and fonts 746 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    581 KiB

    4 images are downloaded at several times the size a phone draws them, for example 2026HEIGoldLeader1-scaled.png.webp at 2,560 px wide, shown at 112 px. Resized copies would save about 581 KiB.

  • 6 images in older formats

    6 images (718 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.

  • 3 images below the first screen load straight away

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

  • About 2.4 g of CO₂ per visit

    2.37 g

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

Accessibility

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

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

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 2 H1 headlines

    There are 2 <h1> headlines (“USC Arcadia Hospital” and “USC Arcadia Hospital”). One clear main headline is easier for people and search engines.

  • 2 links with vague text

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

  • 143 internal links, 33 external

    The homepage links to 143 pages on uscarcadiahospital.org and 33 external pages.

7 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “Explore USC Arcadia Hospital, a leading community hospital offering comprehensive health services in the San Gabriel Va…”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “USC Arcadia Hospital - Keck Medicine of USC”.

  • Canonical URL set

    The canonical URL is https://www.keckmedicine.org/locations/300-w-huntington-drive-arcadia/.

  • Structured data in place

    Structured data found: BreadcrumbList, Hospital, ImageObject, MedicalWebPage and Organization.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.keckmedicine.org/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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.keckmedicine.org/locations/1812-verdugo-blvd-glendale is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.keckmedicine.org/conditions-and-treatments and https://www.keckmedicine.org/find-a-doctor 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 67 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 6 small tap targets

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

  • 6 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'split')”.

  • 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

2 to fix81
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 475 words of visible text.

6 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Request an Appointment”, “Request An Appointment” and “Learn more about USC Arcadia Hospital”.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 15 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

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 34 other companies contacted

    Loading the homepage contacts 34 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 uscarcadiahospital.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Fastly

Company

Headquarters
Arcadia

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on uscarcadiahospital.org, including 21 speed issues, 2 SEO issues 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