westbridge.org website review

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

Your mobile performance score is 70 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

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

7 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.5 MB and 502 ms of main-thread time.

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

YouTube costs a phone 358 ms of main-thread work and 1.1 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.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.

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

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

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

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

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

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.

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

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Westbridge-Hero-Image”.

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

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

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

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

Your homepage downloads 2.1 MB in 56 requests on a phone: scripts 1.2 MB (15), images 502 KiB (11) and fonts 216 KiB (7). Under 2 MB keeps phones on slow connections fast.

Homequote-480x30.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example New-Logo_01.jpg at 926 px wide, shown at 100 px. Resized copies would save about 169 KiB.

1 image (189 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.

1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 17 characters: “Home - WestBridge”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 539 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 49 pages on westbridge.org and 6 external pages.

https://www.westbridge.org/all-groups-and-programming and https://www.westbridge.org/westbridges-continuum-of-care-for-adults have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.westbridge.org/intensive-outpatient-program, https://www.westbridge.org/programs, https://www.westbridge.org/residential-treatment, https://www.westbridge.org/choosing-a-residential-treatment-program, https://www.westbridge.org/a-day-in-the-life-at-the-commons and https://www.westbridge.org/partial-hospitalization-program-php and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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

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

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

The homepage carries about 549 words of visible text.

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

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

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.

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