Website review, no card needed

accrv.org logo

accrv.org website review

Visit site (opens in a new tab)Reviewed 14 November 202645 issues · 89 checks

This review found 45 issues worth fixing on accrv.org, 14 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of accrv.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix47
  • Use efficient cache lifetimes

    4.3 s · 6.8 MB

    55 files are served with short cache lifetimes, so returning visitors download them again (6.8 MB).

  • Reduce unused JavaScript

    6.8 s · 812 KiB

    About 812 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.

  • Improve image delivery

    1.3 s · 4.7 MB

    29 images could be 4.7 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.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Vimeo and Other Google APIs/SDKs and others), adding 2.1 MB and 815 ms of main-thread time.

  • Google CDN adds 655 ms

    655 ms

    Google CDN costs a phone 655 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.

  • Reduce unused CSS

    300 ms · 63 KiB

    About 63 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.3 s

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

  • Vimeo adds 72 ms

    72 ms

    Vimeo costs a phone 72 ms of main-thread work and 391 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.

  • Cloudflare CDN adds 17 ms

    17 ms

    Cloudflare CDN costs a phone 17 ms of main-thread work and 316 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.

  • 9 long tasks on the main thread

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

  • Document request latency

    39 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 86 ms

    86 ms

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

Core Web Vitals

6 to fix57
  • First Contentful Paint: 9.8 s

    9.8 s

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

  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Make a Donation Make an Impact To help with the day-to-day …”.

  • Time to Interactive: 19.3 s

    19.3 s

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

  • Speed Index: 9.8 s

    9.8 s

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

  • 49 images without width and height

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

  • Total Blocking Time: 364 ms

    364 ms

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix43
  • Page weight: 9.3 MB in 98 requests

    9.3 MB

    Your homepage downloads 9.3 MB in 98 requests on a phone: images 6.7 MB (49), scripts 1.5 MB (18) and fonts 456 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 29 images in older formats

    29 images (5.1 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.

  • 24 images below the first screen load straight away

    24 images further down the page (4.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    191 KiB

    2 images are downloaded at several times the size a phone draws them, for example SalemChamber.jpg at 1,080 px wide, shown at 150 px. Resized copies would save about 191 KiB.

  • About 2.6 g of CO₂ per visit

    2.63 g

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

Accessibility

8 to fixGoogle 8089
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • 11 images without alt text

    11 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 20 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.

  • 21 links without text

    21 visible links have no text or label, so screen readers cannot say where they go.

  • 5 form fields without a label

    5 form fields have 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 (h1 → h3, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 43 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: 43 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8380
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 17 H1 headlines

    There are 17 <h1> headlines (“1st Medical Day Care for Adults in Virginia”, “1st Medical Day Care for Adults in Virginia” and “Make a Donation Make an Impact”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (221 characters)

    Your meta description is 221 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 45 internal links, 7 external

    The homepage links to 45 pages on accrv.org and 7 external pages.

4 checks passed
  • Title: 42 characters

    Your title is a healthy 42 characters: “Adult Care Center of Roanoke Valley - Home”.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.accrv.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://www.accrv.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 (791 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 4 pages share a title

    https://www.accrv.org/meet-the-team.php, https://www.accrv.org/valued-partners.php, https://www.accrv.org/adultcare-news-events.php and https://www.accrv.org/services-details.php all use the title “Adult Care Center of Roanoke Valley”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://www.accrv.org/adultcare-about.php and https://www.accrv.org/adultcare-donation.php use the same meta description. A description written for each page earns more clicks.

  • 4 pages with very little text

    https://www.accrv.org/adultcare-news-events.php, https://www.accrv.org/enrollment-forms.php, https://www.accrv.org/services-details.php and https://www.accrv.org/adultcare-gallery.php 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.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    10 pages of 11 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • 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 10 pages that loaded have a <title>.

Best practices

5 to fixGoogle 4681
  • 5 small tap targets

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

  • 2 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

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

    The homepage carries about 395 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us” and “Healthcare Workers Apply”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks and 17 customer or partner logos.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 4 of them by other companies (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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 accrv.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Global2016 Globalhostingsolutions Inc

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on accrv.org, including 17 speed issues, 5 SEO issues 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

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