northsidecenter.org website review

15 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 23.8 s faster on a phone.

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

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

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

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

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

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

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

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

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

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

6 KiB could be saved by minifying CSS.

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

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

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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 12.0 MB in 212 requests on a phone: images 5.3 MB (24), scripts 4.8 MB (93) and fonts 1.1 MB (13). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

11 images are downloaded at several times the size a phone draws them, for example Community-Day-Post-Mobile.png at 1,254 px wide, shown at 390 px. Resized copies would save about 1.0 MB.

8 images (4.5 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.

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

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

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

The skip-link target should exist and be focusable: 2 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.

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

5 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

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

The homepage links to 33 pages on northsidecenter.org and 19 external pages.

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

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

https://www.northsidecenter.org/growing-up-seen/growing-up-seen-registration is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.northsidecenter.org/donate and https://www.northsidecenter.org/give-now all use the title “Support Northside”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.northsidecenter.org/programs, https://www.northsidecenter.org/careers, https://www.northsidecenter.org/volunteer, https://www.northsidecenter.org/news-announcements, https://www.northsidecenter.org/growing-up-seen/growing-up-seen-registration and https://www.northsidecenter.org/tech-workshops and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.northsidecenter.org/donate and https://www.northsidecenter.org/give-now use the same meta description. A description written for each page earns more clicks.

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

https://www.northsidecenter.org/about, https://www.northsidecenter.org/careers, https://www.northsidecenter.org/volunteer, https://www.northsidecenter.org/news-announcements, https://www.northsidecenter.org/growing-up-seen/growing-up-seen-registration and https://www.northsidecenter.org/tech-workshops and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.northsidecenter.org/donate, https://www.northsidecenter.org/2026-gala-gallery, https://www.northsidecenter.org/give-now and https://www.northsidecenter.org/2025-impact-report have 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.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

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

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

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 391 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 10 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.