Website review, no card needed
mageerehab.org website review
Visit site (opens in a new tab)Reviewed 22 November 202640 issues · 70 checks
This review found 40 issues worth fixing on mageerehab.org, 15 of them high impact, across 70 checks. The most urgent: reduce unused JavaScript. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.2 s |
| Nov 14, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 254 ms |
| Jun 6, 2026 | 254 ms |
| Jun 13, 2026 | 254 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 254 ms |
| Jul 4, 2026 | 251 ms |
| Jul 11, 2026 | 245 ms |
| Jul 18, 2026 | 238 ms |
| Jul 25, 2026 | 238 ms |
| Aug 1, 2026 | 243 ms |
| Aug 8, 2026 | 247 ms |
| Aug 15, 2026 | 252 ms |
| Aug 22, 2026 | 251 ms |
| Aug 29, 2026 | 250 ms |
| Sep 5, 2026 | 251 ms |
| Sep 12, 2026 | 252 ms |
| Sep 19, 2026 | 253 ms |
| Sep 26, 2026 | 251 ms |
| Oct 3, 2026 | 246 ms |
| Oct 10, 2026 | 232 ms |
| Oct 17, 2026 | 212 ms |
| Oct 24, 2026 | 194 ms |
| Oct 31, 2026 | 180 ms |
| Nov 7, 2026 | 175 ms |
| Nov 14, 2026 | 171 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.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Reduce unused JavaScript
2.4 s · 443 KiBAbout 443 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
2.8 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
900 ms · 271 KiB48 files are served with short cache lifetimes, so returning visitors download them again (271 KiB).
Legacy JavaScript
500 ms · 69 KiBPolyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
Improve image delivery
430 KiB4 images could be 430 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
300 ms · 65 KiBAbout 65 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (Optanon, Google Tag Manager and perfalytics.com and others), adding 634 KiB and 443 ms of main-thread time.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 238 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
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: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Rehabilitation center in Phialdephia for inpatient and outp…”.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.2 s
8.2 sThe page becomes fully interactive after 8.2 s. Good is under 3.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 477 ms
477 msScripts block taps and scrolling for 477 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.157
0.157The layout shifts by 0.157 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 511 ms
511 msReal visitors wait 511 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 32% faster for real visitors
-32%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 254 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 54.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.6 MB in 79 requests
1.6 MBYour homepage downloads 1.6 MB in 79 requests on a phone: scripts 825 KiB (10), images 602 KiB (44) and fonts 88 KiB (4). That is a lean page.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Banner landmark should not be contained in another landmark (1 element)
Banner 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 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Jefferson Moss-Magee Rehabilitation Hospital – Center City | Jefferson Health”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
4 checks passed
Meta description: 128 characters
Your meta description is 128 characters: “Jefferson Moss-Magee Rehabilitation Hospital – Center City is a Greater Philadelphia rehabilitation program in Philadel…”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://www.jeffersonhealth.org/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 893 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.
No Organization structured data
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.
2 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.
llms.txt published
The site publishes https://www.jeffersonhealth.org/llms.txt (17 KiB, 117 links), a plain-text guide to the site for AI tools.
Best practices
13 small tap targets
13 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “this.init is not a function”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 893 words of copy
The homepage carries about 893 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 mageerehab.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- AWS
Company
- Founded
- 1958
- Headquarters
- Philadelphia
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on mageerehab.org, including 19 speed issues, 6 SEO issues and 4 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.