waldeneatingdisorders.com website review

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

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

787 KiB could be saved by minifying JavaScript.

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

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

The page has 3,144 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (jotform.com, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 3.2 MB and 1.0 s of main-thread time.

jotform.com costs a phone 347 ms of main-thread work and 1.9 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.

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

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

Google Tag Manager costs a phone 301 ms of main-thread work and 323 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 310 ms. During a long task the page ignores taps.

jotfor.ms costs a phone 0 ms of main-thread work and 539 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.

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

1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your largest element takes 25.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Everyone is Welcome at Walden All Genders, All Diagnoses Le…”.

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

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

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

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 107 ms to 95 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 3.0 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.3 MB in 107 requests on a phone: scripts 2.7 MB (62), fonts 726 KiB (9) and stylesheets 423 KiB (12). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 144.7 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”.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 177 pages on waldeneatingdisorders.com and 14 external pages.

There is no https://www.waldeneatingdisorders.com/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.waldeneatingdisorders.com/what-we-treat/anorexia, https://www.waldeneatingdisorders.com/what-we-treat/anorexia/anorexia-symptoms-and-signs, https://www.waldeneatingdisorders.com/what-we-treat/anorexia/potential-causes-and-risk-factors-of-anorexia, https://www.waldeneatingdisorders.com/what-we-treat/anorexia/anorexia-health-risks, https://www.waldeneatingdisorders.com/what-we-treat/anorexia/anorexia-treatment and https://www.waldeneatingdisorders.com/what-we-treat/anorexia/anorexia-online-assessment all use the title “What is Anorexia? Symptoms, Signs, and Treatment | Monte Nido”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.waldeneatingdisorders.com/what-we-treat/anorexia, https://www.waldeneatingdisorders.com/what-we-treat/anorexia/anorexia-symptoms-and-signs, https://www.waldeneatingdisorders.com/what-we-treat/anorexia/potential-causes-and-risk-factors-of-anorexia, https://www.waldeneatingdisorders.com/what-we-treat/anorexia/anorexia-health-risks, https://www.waldeneatingdisorders.com/what-we-treat/anorexia/anorexia-treatment and https://www.waldeneatingdisorders.com/what-we-treat/anorexia/anorexia-online-assessment use the same meta description. A description written for each page earns more clicks.

https://www.waldeneatingdisorders.com/contact-us, https://www.waldeneatingdisorders.com/who-we-serve, https://www.waldeneatingdisorders.com/who-we-serve/all-ages, https://www.waldeneatingdisorders.com/who-we-serve/all-genders, https://www.waldeneatingdisorders.com/who-we-serve/families and https://www.waldeneatingdisorders.com/virtual-eating-disorder-treatment-for-lgbtq and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.waldeneatingdisorders.com/who-we-serve, https://www.waldeneatingdisorders.com/who-we-serve/all-ages and https://www.waldeneatingdisorders.com/who-we-serve/families took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://montenido.jotform.com/events/form/243175314677158/?ref=&res=390x844&eventID=1793096552549_243175314677158_dqKzlZf&loc=https%253A%252F%252Fwww.waldeneatingdisorders.com%252F.

5 of 16 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 “Failed to load resource: the server responded with a status of 404 ()”.

A form field blocks pasting, which frustrates password managers and people on phones.

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.

Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 53 fields (8 required). Every extra field lowers completion.

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

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 1,018 words of visible text.

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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