Website review, no card needed

brickyardhc.com logo

brickyardhc.com website review

Visit site (opens in a new tab)Reviewed 31 October 202636 issues · 85 checks

This review found 36 issues worth fixing on brickyardhc.com, 10 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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
3.0 s2.5 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.6 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
166 ms122 msMay 9Oct 24146 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026137 ms
May 16, 2026137 ms
May 23, 2026129 ms
May 30, 2026127 ms
Jun 6, 2026143 ms
Jun 13, 2026143 ms
Jun 20, 2026145 ms
Jun 27, 2026139 ms
Jul 4, 2026139 ms
Jul 11, 2026139 ms
Jul 18, 2026144 ms
Jul 25, 2026147 ms
Aug 1, 2026146 ms
Aug 8, 2026160 ms
Aug 15, 2026161 ms
Aug 22, 2026160 ms
Aug 29, 2026157 ms
Sep 5, 2026146 ms
Sep 12, 2026142 ms
Sep 19, 2026150 ms
Sep 26, 2026150 ms
Oct 3, 2026153 ms
Oct 10, 2026151 ms
Oct 17, 2026146 ms
Oct 24, 2026146 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 brickyardhc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix61
  • Render-blocking requests

    1.9 s

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

  • Reduce unused JavaScript

    1.2 s · 367 KiB

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

  • Improve image delivery

    300 ms · 1.2 MB

    7 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, tidio.co and Clarity and others), adding 1.1 MB and 535 ms of main-thread time.

  • Google Tag Manager adds 327 ms

    327 ms

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

  • tidio.co adds 110 ms

    110 ms

    tidio.co costs a phone 110 ms of main-thread work and 515 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

    150 ms · 33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 24 KiB

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

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 745 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

8 to fix67
  • 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: 14.0 s

    14.0 s

    Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Brickyard Healthcare provides short- and long-term care to …”.

  • Time to Interactive: 15.4 s

    15.4 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • 21 images without width and height

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

  • Total Blocking Time: 283 ms

    283 ms

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

5 checks passed
  • Real-user INP: 148 ms

    148 ms

    Real visitors wait 148 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    1.1 s

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

  • Real-user TTFB: 439 ms

    439 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    skilled-nursing-facilities-1.jpg weighs 678 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    515 KiB

    1 image is downloaded at several times the size a phone draws it, for example skilled-nursing-facilities-1.jpg at 2,080 px wide, shown at 340 px. Resized copies would save about 515 KiB.

  • Page weight: 3.3 MB in 115 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 115 requests on a phone: images 1.7 MB (33), scripts 1.2 MB (34) and fonts 180 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 13 images below the first screen load straight away

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

  • 6 images in older formats

    6 images (1.4 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.

  • About 0.9 g of CO₂ per visit

    0.93 g

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

Accessibility

5 to fixGoogle 8293
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Input buttons must have discernible text (1 element)

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

  • 5 text elements with low contrast

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

  • 8 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 87 internal links, 14 external

    The homepage links to 87 pages on brickyardhc.com and 14 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Brickyard Healthcare is a provider of short-term rehabilitation and long-term care services with care center locations …”.

  • One H1 headline

    Your main headline reads: “In the Care of Community”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Welcome to Brickyard Healthcare | In the Care of Community”.

  • Canonical URL set

    The canonical URL is https://www.brickyardhc.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.brickyardhc.com/payment-portal is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.brickyardhc.com/payment-portal and https://www.brickyardhc.com/health-services/dialysis have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.brickyardhc.com/payment-portal has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 26 found) 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

2 checks passed
  • Tap targets are thumb-sized

    18 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix69
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • A 9-field form

    Your longest form asks for 9 fields (6 required). Every extra field lowers completion.

  • 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 opening hours

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

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

    The homepage carries about 637 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 3 calls to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Cloudflare Web Analytics.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 21 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 brickyardhc.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
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on brickyardhc.com, including 15 speed issues, 1 SEO issue and 5 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