Website review, no card needed
friedwaldcenter.com website review
Visit site (opens in a new tab)Reviewed 18 October 202641 issues · 88 checks
This review found 41 issues worth fixing on friedwaldcenter.com, 16 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
77CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.3 s
2.0 s
2.7 s
3.3 s
4.0 s
4.7 s
5.3 s
Speed
Use efficient cache lifetimes
21.5 s · 6.6 MB102 files are served with short cache lifetimes, so returning visitors download them again (6.6 MB).
Render-blocking requests
11.1 s26 files block the first paint until they finish downloading. Deferring or inlining them could save about 11.1 s.
Reduce unused CSS
8.7 s · 1.4 MBAbout 1.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.7 s faster on a phone.
Reduce unused JavaScript
6.6 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.6 s faster on a phone.
Minify JavaScript
1.6 s · 269 KiB269 KiB could be saved by minifying JavaScript.
Minify CSS
1.3 s · 186 KiB186 KiB could be saved by minifying CSS.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 58). Pages that score under 90 lose visitors before the first paint.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 643 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
openstreetmap.org adds 0 ms
0 msopenstreetmap.org costs a phone 0 ms of main-thread work and 556 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.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 320 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.
Legacy JavaScript
200 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Improve image delivery
131 KiB8 images could be 131 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Document request latency
109 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
4 third-party services on the page
4 third-party services load with your homepage (Google Fonts, Gravatar and cleantalk.org and others), adding 878 KiB and 0 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.
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: 87 ms
87 msYour server sent the HTML in 87 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 12.8 s
12.8 sThe first text or image appears after 12.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 31.7 s
31.7 sYour largest element takes 31.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 32.1 s
32.1 sThe page becomes fully interactive after 32.1 s. Good is under 3.8 s.
Speed Index: 13.8 s
13.8 sVisually, the page fills in at 13.8 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
2 checks passed
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 8 ms
8 msScripts block the page for only 8 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.4 MB in 120 requests
7.4 MBYour homepage downloads 7.4 MB in 120 requests on a phone: images 3.0 MB (41), scripts 2.1 MB (37) and stylesheets 1.7 MB (26). Under 2 MB keeps phones on slow connections fast.
22 images in older formats
22 images (1.5 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.
15 images below the first screen load straight away
15 images further down the page (553 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
9 KiB1 image is downloaded at several times the size a phone draws it, for example 1.building.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 9 KiB.
About 2.1 g of CO₂ per visit
2.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.10 g of CO₂e: 252.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
5 elements use ARIA attributes their role does not allow, which confuses screen readers.
Images must have alternative text (1 element)
Images must have alternative text: 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.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (47 elements)
All page content should be contained by landmarks: 47 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 10 failed. 2 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
45 internal links, 1 external
The homepage links to 45 pages on friedwaldcenter.com and 1 external page.
5 checks passed
One H1 headline
Your main headline reads: “Learn about the programs & services we offer!”.
Title: 47 characters
Your title is a healthy 47 characters: “Friedwald Center – https://friedwaldcenter.com/”.
Canonical URL set
The canonical URL is https://friedwaldcenter.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://friedwaldcenter.com/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://friedwaldcenter.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,190 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://friedwaldcenter.com/category/updates and https://friedwaldcenter.com/updates all use the title “Updates – Friedwald Center”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://friedwaldcenter.com/about, https://friedwaldcenter.com/contact, https://friedwaldcenter.com/gallery, https://friedwaldcenter.com/new-york-man-is-home-for-christmas-after-269-day-battle-with-covid, https://friedwaldcenter.com/category/updates and https://friedwaldcenter.com/author/admin_mm and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://friedwaldcenter.com/about, https://friedwaldcenter.com/contact, https://friedwaldcenter.com/gallery, https://friedwaldcenter.com/updates, https://friedwaldcenter.com/visitation-policy-covid-19 and https://friedwaldcenter.com/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://friedwaldcenter.com/contact, https://friedwaldcenter.com/gallery, https://friedwaldcenter.com/category/updates, https://friedwaldcenter.com/author/admin_mm, https://friedwaldcenter.com/rehab-recommendation and https://friedwaldcenter.com/privacy-policy have 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.
9 pages slow to respond
https://friedwaldcenter.com/about, https://friedwaldcenter.com/contact, https://friedwaldcenter.com/gallery, https://friedwaldcenter.com/new-york-man-is-home-for-christmas-after-269-day-battle-with-covid, https://friedwaldcenter.com/category/updates and https://friedwaldcenter.com/author/admin_mm and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage and read each the way a search engine does.
4 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.
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
5 small tap targets
5 of 21 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 “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
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,104 words of copy
The homepage carries about 1,104 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: “Contact”.
4 calls to action
The homepage has 4 calls to action, for example “Learn more about our mission”, “Learn more about Friedwald” and “SCHEDULE A TOUR”.
2 short forms
2 short forms (6 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 13 testimonial or review blocks, a star rating and 3 trust badges.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
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.
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
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 friedwaldcenter.com, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on friedwaldcenter.com, including 15 speed issues, 4 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.