changewellproject.com website review

Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

5 third-party services load with your homepage (Wix, Google Tag Manager and Sentry and others), adding 1.4 MB and 677 ms of main-thread time.

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

Wix costs a phone 472 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.

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

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

28 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

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

Polyfills for old browsers add 12 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.

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

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

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

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 2.2 MB in 201 requests on a phone: scripts 1.1 MB (95), other files 695 KiB (85) and HTML 175 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

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

The homepage links to 45 pages on changewellproject.com and 15 external pages.

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.

/ournews, /terms-and-conditions, /accessibility-statement and /drewsharesite are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/team has no meta description, so Google writes the search snippet from whatever text it finds.

/strengthening-rehousing-across-ca, /strengthening-rehousing-across-ca-tribal, /housingdisabilityadvocacyprograms and /srapimplementation use the same meta description. A description written for each page earns more clicks.

/partner-with-us, /subscribe-to-change-well-project, /drewsharesite and /team have no <h1> headline, so visitors and search engines get no clear main topic.

/team 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.

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

1 error was logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

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.

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.

changewellproject.com 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.

changewellproject.com'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.

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

DMARC is set to p=none, so mail pretending to be changewellproject.com 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 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 7 cookies (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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.