Website review, no card needed
ageways.org website review
Visit site (opens in a new tab)Reviewed 29 October 202648 issues · 95 checks
This review found 48 issues worth fixing on ageways.org, 22 of them high impact, across 95 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 118 ms |
| May 16, 2026 | 122 ms |
| May 23, 2026 | 117 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 143 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 142 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 132 ms |
| Aug 15, 2026 | 131 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 147 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 155 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 152 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 152 ms |
| Oct 24, 2026 | 145 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.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.7 s
6.6 s
7.5 s
Speed
Improve image delivery
1.3 s · 2.5 MB27 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Reduce unused JavaScript
2.7 s · 972 KiBAbout 972 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
3.0 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
audioeye.com adds 2.0 s
2.0 saudioeye.com costs a phone 2.0 s of main-thread work and 297 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Font display
1.7 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.7 s).
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.5 s
A phone's processor spends 7.5 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Google CDN and others), adding 2.0 MB and 3.5 s of main-thread time.
Google CDN adds 551 ms
551 msGoogle CDN costs a phone 551 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.
Google Tag Manager adds 599 ms
599 msGoogle Tag Manager costs a phone 599 ms of main-thread work and 516 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.
Reduce unused CSS
450 ms · 85 KiBAbout 85 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify JavaScript
300 ms · 21 KiB21 KiB could be saved by minifying JavaScript.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 246 ms. During a long task the page ignores taps.
Legacy JavaScript
200 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify CSS
150 ms · 5 KiB5 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
28 KiB6 files are served with short cache lifetimes, so returning visitors download them again (28 KiB).
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: 51 ms
51 msYour server sent the HTML in 51 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.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 18.1 s
18.1 sYour largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ageways Icon”.
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 30.1 s
30.1 sThe page becomes fully interactive after 30.1 s. Good is under 3.8 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 118 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 571 ms
571 msScripts block taps and scrolling for 571 ms in total while the page loads. Good is under 200 ms.
44 images without width and height
44 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.041
0.041The layout barely moves while loading (CLS 0.041, good is under 0.1).
Images and page weight
Page weight: 17.8 MB in 152 requests
17.8 MBYour homepage downloads 17.8 MB in 152 requests on a phone: media 10.9 MB (2), images 3.8 MB (51) and scripts 2.2 MB (52). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
2026-Hermes-Creative-Awards-bug.png weighs 582 KiB. On a phone connection a single image that size takes seconds.
6 images far larger than shown
994 KiB6 images are downloaded at several times the size a phone draws them, for example 2026-Hermes-Creative-Awards-bug.png at 775 px wide, shown at 112 px. Resized copies would save about 994 KiB.
21 images in older formats
21 images (3.3 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.
20 images below the first screen load straight away
20 images further down the page (2.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.0 g of CO₂ per visit
5.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.03 g of CO₂e: 604.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (35 elements)
All page content should be contained by landmarks: 35 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
48 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: 48 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
83 internal links, 7 external
The homepage links to 83 pages on ageways.org and 7 external pages.
8 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “AgeWays - Area Agency on Aging 1-B: Access government programs and elderly assistance in Livingston, Macomb, Monroe, Oa…”.
One H1 headline
Your main headline reads: “AgeWays Nonprofit Senior Services”.
Title: 54 characters
Your title is a healthy 54 characters: “Senior Support Services | Southeast Michigan | AgeWays”.
Canonical URL set
The canonical URL is https://www.ageways.org/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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 https://www.ageways.org/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,193 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ageways.org/llms.txt (195 KiB, 422 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.ageways.org/category/senior-programs-services is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.ageways.org/category/senior-programs-services has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.ageways.org/senior-services/mioptions, https://www.ageways.org/senior-services/adaptive-wellness and https://www.ageways.org/senior-services/veterans use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
5 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343253629&Ver=2&mid=bc567678-cad8-49e4-9597-999eff361472&bo=1&sid=ac31dd80d3ce11f19d2555893faf9d08&vid=ac31dfa0d3ce11f1962415a8ab2da95b&vids=1&msclkid=N&pi=918639831&l.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
19 of 21 tappable elements near the top are at least 24 px.
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.
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.
A 10-field form
Your longest form asks for 10 fields (4 required). Every extra field lowers completion.
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,607 words of copy
The homepage carries about 1,607 words of visible text.
6 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Contact”, “Download Connect Guide” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 19 testimonial or review blocks, 20 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
No consent tool detected
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.
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 ageways.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
- Analytics
- Google Tag Manager
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on ageways.org, including 24 speed issues, 1 SEO issue and 3 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.