Website review, no card needed

choosekeswick.org logo

choosekeswick.org website review

Visit site (opens in a new tab)Reviewed 21 October 202634 issues · 87 checks

This review found 34 issues worth fixing on choosekeswick.org, 12 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.1 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.4 s
Sep 5, 20261.6 s
Sep 12, 20261.2 s
Sep 19, 20261.3 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20262.0 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
128 ms65 msMay 2Oct 17107 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026100 ms
May 9, 2026119 ms
May 23, 2026121 ms
May 30, 202680 ms
Jun 6, 202691 ms
Jun 13, 202678 ms
Jun 20, 202680 ms
Jun 27, 202688 ms
Jul 4, 202680 ms
Jul 11, 202693 ms
Jul 18, 202694 ms
Jul 25, 202697 ms
Aug 1, 202691 ms
Aug 8, 202691 ms
Aug 15, 202691 ms
Aug 22, 202687 ms
Aug 29, 202679 ms
Sep 5, 202680 ms
Sep 12, 202679 ms
Sep 19, 202677 ms
Sep 26, 202685 ms
Oct 3, 202672 ms
Oct 10, 2026103 ms
Oct 17, 2026107 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

Full-page screenshot of choosekeswick.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. choosekeswick.org at 0.4 s0.4 s
  2. choosekeswick.org at 0.8 s0.8 s
  3. choosekeswick.org at 1.1 s1.1 s
  4. choosekeswick.org at 1.5 s1.5 s
  5. choosekeswick.org at 1.9 s1.9 s
  6. choosekeswick.org at 2.3 s2.3 s
  7. choosekeswick.org at 2.7 s2.7 s
  8. choosekeswick.org at 3.0 s3.0 s

Speed

11 to fix46
  • Reduce unused JavaScript

    5.7 s · 1.1 MB

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

  • Render-blocking requests

    5.7 s

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

  • Use efficient cache lifetimes

    2.4 s · 487 KiB

    11 files are served with short cache lifetimes, so returning visitors download them again (487 KiB).

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46 (desktop: 53). 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 (YouTube, website-files.com and Google Tag Manager and others), adding 3.2 MB and 1.5 s of main-thread time.

  • Reduce unused CSS

    450 ms · 158 KiB

    About 158 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.

  • YouTube adds 501 ms

    501 ms

    YouTube costs a phone 501 ms of main-thread work and 990 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.

  • Improve image delivery

    577 KiB

    10 images could be 577 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • website-files.com adds 293 ms

    293 ms

    website-files.com costs a phone 293 ms of main-thread work and 1.2 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 278 ms

    278 ms

    Google Tag Manager costs a phone 278 ms of main-thread work and 482 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.

  • Main-thread work: 3.2 s

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

  • 16 long tasks on the main thread

    16 long tasks block the main thread while loading, the longest for 188 ms. During a long task the page ignores taps.

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

  • 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: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • First Contentful Paint: 12.6 s

    12.6 s

    The first text or image appears after 12.6 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 25.0 s

    25.0 s

    Your largest element takes 25.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 25.2 s

    25.2 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • Total Blocking Time: 396 ms

    396 ms

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 100 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 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.3 s

    2.3 s

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 562 ms

    562 ms

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

  • Cumulative Layout Shift: 0.008

    0.008

    The layout barely moves while loading (CLS 0.008, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 4.2 MB in 91 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 91 requests on a phone: scripts 2.8 MB (32), images 796 KiB (14) and fonts 278 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6aa7eff7b7386979f683ddbf_KES-Flowers_dark-p-500.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images in older formats

    3 images (126 KiB) 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.

  • About 1.2 g of CO₂ per visit

    1.18 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 141.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8990
  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (9 elements)

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

  • Banner landmark should not be contained in another landmark (2 elements)

    Banner landmark should not be contained in another landmark: 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.

  • 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.

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9290
  • 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.

  • 5 links with vague text

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

  • 43 internal links, 11 external

    The homepage links to 43 pages on choosekeswick.org and 11 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Keswick improves the experience of aging in Baltimore, MD, offering Wise & Well membership, Community for Life, short‑t…”.

  • One H1 headline

    Your main headline reads: “Improving the Experience of Aging, Together.”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Keswick - Improving the Experience of Aging, Together”.

  • 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://choosekeswick.org/sitemap.xml.

AI search readiness

1 to fix88
  • 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://choosekeswick.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.

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 (780 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 7791
  • 6 small tap targets

    6 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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.

  • Thin social proof

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

  • No opening hours

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

  • 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 728 words of copy

    The homepage carries about 728 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT” and “CONTACT US”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Contact Us” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 2 email links.

  • 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

    5

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).

  • 33 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 choosekeswick.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
Webflow
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on choosekeswick.org, including 17 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25