Website review, no card needed
thewrightcenter.org website review
Visit site (opens in a new tab)Reviewed 29 October 202642 issues · 92 checks
This review found 42 issues worth fixing on thewrightcenter.org, 20 of them high impact, across 92 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 99 ms |
| May 16, 2026 | 98 ms |
| May 23, 2026 | 100 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 108 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 99 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 97 ms |
| Aug 15, 2026 | 100 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 110 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 108 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 99 ms |
| Oct 24, 2026 | 98 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.1 s
3.5 s
Speed
Improve image delivery
7.1 s · 3.6 MB47 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.1 s faster on a phone.
Use efficient cache lifetimes
8.4 s · 1.4 MB7 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Reduce unused JavaScript
5.1 s · 968 KiBAbout 968 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.
Render-blocking requests
2.3 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, smartbot360.com and iubenda and others), adding 1.7 MB and 603 ms of main-thread time.
Reduce unused CSS
300 ms · 99 KiBAbout 99 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
smartbot360.com adds 220 ms
220 mssmartbot360.com costs a phone 220 ms of main-thread work and 1.3 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 259 ms. During a long task the page ignores taps.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 814 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
200 ms · 37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify JavaScript
63 KiB63 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 35.7 s
35.7 sYour largest element takes 35.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Need HELP after hours? Call 570-230-0019 to speak with our …”.
Time to Interactive: 36.7 s
36.7 sThe page becomes fully interactive after 36.7 s. Good is under 3.8 s.
First Contentful Paint: 7.4 s
7.4 sThe first text or image appears after 7.4 s on a phone. Good is under 1.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
44 images without width and height
44 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 458 ms
458 msScripts block taps and scrolling for 458 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 99 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 98 ms
98 msReal visitors wait 98 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 450 ms
450 msReal visitors wait 450 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.2 MB in 111 requests
8.2 MBYour homepage downloads 8.2 MB in 111 requests on a phone: images 6.0 MB (55), scripts 1.8 MB (18) and fonts 184 KiB (7). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.
14 images far larger than shown
1.6 MB14 images are downloaded at several times the size a phone draws them, for example Medical-team-looking-at-camera-while-working-together-at-des at 2,000 px wide, shown at 374 px. Resized copies would save about 1.6 MB.
24 images in older formats
24 images (3.4 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.
26 images below the first screen load straight away
26 images further down the page (3.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.33 g of CO₂e: 279.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Required ARIA attributes must be provided (1 element)
Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
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.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (24 characters)
Your title is only 24 characters: “Home - The Wright Center”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 H1 headlines
There are 3 <h1> headlines (“Need HELP after hours?”, “Psychiatry services” and “The WRIGHT Kind of Medicine”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
14 links with vague text
14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
136 internal links, 57 external
The homepage links to 136 pages on thewrightcenter.org and 57 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://thewrightcenter.org/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://thewrightcenter.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://thewrightcenter.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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,071 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://thewrightcenter.org/locations, https://thewrightcenter.org/services/psychiatry-services, https://thewrightcenter.org/careers, https://thewrightcenter.org/es, https://thewrightcenter.org/ne and https://thewrightcenter.org/ht and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css2?family=OpenDyslexic&display=swap' from origin 'https://t…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,272 words of copy
The homepage carries about 1,272 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more and customize”.
4 calls to action
The homepage has 4 calls to action, for example “Join Our Board of Directors”, “Learn More” and “Sign Up to Our Newsletter”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 37 customer or partner logos and 14 trust badges.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: iubenda
A consent management tool (iubenda) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at thewrightcenter.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- Cloudflare
Company
- Founded
- 1976
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on thewrightcenter.org, including 16 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.