Website review, no card needed
chesapeakeregional.com website review
Visit site (opens in a new tab)Reviewed 27 October 202637 issues · 83 checks
This review found 37 issues worth fixing on chesapeakeregional.com, 11 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 999 ms |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 979 ms |
| Aug 29, 2026 | 992 ms |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 111 ms |
| May 16, 2026 | 110 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 110 ms |
| Aug 15, 2026 | 108 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 108 ms |
| Sep 12, 2026 | 108 ms |
| Sep 19, 2026 | 108 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 105 ms |
| Oct 24, 2026 | 106 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.9 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Improve image delivery
1.2 s · 255 KiB7 images could be 255 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
Use efficient cache lifetimes
6.9 MB52 files are served with short cache lifetimes, so returning visitors download them again (6.9 MB).
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 76). Pages that score under 90 lose visitors before the first paint.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 602 ms. During a long task the page ignores taps.
Reduce unused JavaScript
280 ms · 322 KiBAbout 322 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 ms faster on a phone.
Reduce unused CSS
450 ms · 84 KiBAbout 84 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.
Legacy JavaScript
300 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 third-party services on the page
3 third-party services load with your homepage (JSDelivr CDN, Google Fonts and Sentry), adding 243 KiB and 123 ms of main-thread time.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 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.
Largest Contentful Paint: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Updated Best Regional Hospitals logo on a blue background”.
Time to Interactive: 9.8 s
9.8 sThe page becomes fully interactive after 9.8 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.21
0.21For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.197
0.197The layout shifts by 0.197 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 337 ms
337 msScripts block taps and scrolling for 337 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 111 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 512 ms
512 msReal visitors wait 512 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 9.5 MB in 114 requests
9.5 MBYour homepage downloads 9.5 MB in 114 requests on a phone: fonts 8.0 MB (54), scripts 834 KiB (22) and images 494 KiB (19). Under 2 MB keeps phones on slow connections fast.
5 images below the first screen load straight away
5 images further down the page (353 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
25 KiB3 images are downloaded at several times the size a phone draws them, for example DSC_0067.JPG at 1,000 px wide, shown at 318 px. Resized copies would save about 25 KiB.
About 2.7 g of CO₂ per visit
2.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.69 g of CO₂e: 322.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 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.
Title is long (84 characters)
Your title is 84 characters, so Google will cut it off around 60: “Chesapeake Regional Healthcare: Innovative For Life | Chesapeake Regional Healthcare”.
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.
74 internal links, 16 external
The homepage links to 74 pages on chesapeakeregional.com and 16 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Innovative for life”.
Canonical URL set
The canonical URL is https://chesapeakeregional.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://chesapeakeregional.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://chesapeakeregional.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 (738 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://chesapeakeregional.com/find-a-doctor, https://chesapeakeregional.com/imaging and https://chesapeakeregional.com/node/2243 have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://chesapeakeregional.com/about-us/news-media and https://chesapeakeregional.com/blog use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://chesapeakeregional.com/find-a-doctor, https://chesapeakeregional.com/node/798 and https://chesapeakeregional.com/node/2243 have 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 43 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.
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
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
31 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 484 words of copy
The homepage carries about 484 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” and “Schedule same day care”.
4 calls to action
The homepage has 4 calls to action, for example “Contact”, “Schedule same day care” and “Learn more”.
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
3 other companies contacted
Loading the homepage contacts 3 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 chesapeakeregional.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
- Drupal
- Framework
- jQuery
- Hosting
- Fastly
Company
- Founded
- 1976
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on chesapeakeregional.com, including 18 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.