comhs.org website review

38 files are served with short cache lifetimes, so returning visitors download them again (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 5.4 s faster on a phone.

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

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

13 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, powershealth.org and coveo.com and others), adding 7.9 MB and 1.2 s of main-thread time.

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

powershealth.org costs a phone 270 ms of main-thread work and 5.8 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.

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

The page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.

86 KiB could be saved by minifying JavaScript.

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

coveo.com costs a phone 108 ms of main-thread work and 375 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.

site.com costs a phone 11 ms of main-thread work and 702 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.

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

33 KiB could be saved by minifying CSS.

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

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Polyfills for old browsers add 6 KiB JavaScript that modern phones do not need.

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.

Your largest element takes 31.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Caring mother buttoning her daughter's jacket during cold e…”.

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

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

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

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

5 images weigh 37.3 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example northwest-cancer-center.ashx at 5,452 px wide, shown at 308 px. Resized copies would save about 33.7 MB.

Your homepage downloads 8.0 MB in 102 requests on a phone: images 4.2 MB (26), scripts 2.4 MB (36) and fonts 1,005 KiB (9). Under 2 MB keeps phones on slow connections fast.

13 images (38.2 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.

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

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.

Your page has no <title>, so Google has to invent the blue link in search results.

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.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

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

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

A phone browser shows 305 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /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.

No viewport meta tag, so phones render the desktop layout zoomed out.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://communityfoundationnwin.my.site.com/ESWMessagingforInAppan1732237730956/assets/sty…”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

No character set is declared, so some characters can render as gibberish.

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

comhs.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

comhs.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

DMARC is set to p=none, so mail pretending to be comhs.org is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 11 cookies, 2 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.