Website review, no card needed
romehealth.org website review
Visit site (opens in a new tab)Reviewed 28 October 202636 issues · 86 checks
This review found 36 issues worth fixing on romehealth.org, 12 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 763 ms |
| May 16, 2026 | 733 ms |
| May 23, 2026 | 752 ms |
| May 30, 2026 | 767 ms |
| Jun 6, 2026 | 775 ms |
| Jun 13, 2026 | 799 ms |
| Jun 20, 2026 | 807 ms |
| Jun 27, 2026 | 820 ms |
| Jul 4, 2026 | 822 ms |
| Jul 11, 2026 | 809 ms |
| Jul 18, 2026 | 767 ms |
| Jul 25, 2026 | 756 ms |
| Aug 1, 2026 | 749 ms |
| Aug 8, 2026 | 754 ms |
| Aug 15, 2026 | 763 ms |
| Aug 22, 2026 | 761 ms |
| Aug 29, 2026 | 787 ms |
| Sep 5, 2026 | 798 ms |
| Sep 12, 2026 | 798 ms |
| Sep 19, 2026 | 802 ms |
| Sep 26, 2026 | 791 ms |
| Oct 3, 2026 | 744 ms |
| Oct 10, 2026 | 739 ms |
| Oct 17, 2026 | 714 ms |
| Oct 24, 2026 | 699 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 70 ms |
| May 16, 2026 | 70 ms |
| May 23, 2026 | 71 ms |
| May 30, 2026 | 72 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 74 ms |
| Jun 27, 2026 | 74 ms |
| Jul 4, 2026 | 76 ms |
| Jul 11, 2026 | 76 ms |
| Jul 18, 2026 | 73 ms |
| Jul 25, 2026 | 72 ms |
| Aug 1, 2026 | 71 ms |
| Aug 8, 2026 | 72 ms |
| Aug 15, 2026 | 73 ms |
| Aug 22, 2026 | 71 ms |
| Aug 29, 2026 | 73 ms |
| Sep 5, 2026 | 72 ms |
| Sep 12, 2026 | 72 ms |
| Sep 19, 2026 | 75 ms |
| Sep 26, 2026 | 75 ms |
| Oct 3, 2026 | 74 ms |
| Oct 10, 2026 | 75 ms |
| Oct 17, 2026 | 72 ms |
| Oct 24, 2026 | 70 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
Improve image delivery
8.2 s · 2.4 MB8 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.2 s faster on a phone.
Reduce unused JavaScript
1.1 s · 203 KiBAbout 203 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.1 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 73 KiBAbout 73 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.
Google Tag Manager adds 263 ms
263 msGoogle Tag Manager costs a phone 263 ms of main-thread work and 318 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Cloudflare and activehosted.com and others), adding 340 KiB and 279 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 15 KiB2 files are served with short cache lifetimes, so returning visitors download them again (15 KiB).
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 253 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.2 s
17.2 sYour largest element takes 17.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 17.4 s
17.4 sThe page becomes fully interactive after 17.4 s. Good is under 3.8 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 70 ms to 70 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 59 ms
59 msReal visitors wait 59 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 463 ms
463 msReal visitors wait 463 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 13 ms
13 msScripts block the page for only 13 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
the-best-care-out-there-here-at-rome-health-hospital-near-ro weighs 810 KiB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
631 KiB2 images are downloaded at several times the size a phone draws them, for example the-best-care-out-there-here-at-rome-health-hospital-near-ro at 1,920 px wide, shown at 390 px. Resized copies would save about 631 KiB.
Page weight: 3.5 MB in 34 requests
3.5 MBYour homepage downloads 3.5 MB in 34 requests on a phone: images 2.8 MB (18), scripts 419 KiB (5) and fonts 218 KiB (5). Under 2 MB keeps phones on slow connections fast.
7 images in older formats
7 images (2.8 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.
5 images below the first screen load straight away
5 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 119.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Rome Health Hospital”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (33 characters)
Your meta description is only 33 characters: “Learn more about Rome Health here”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.romehealth.org/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
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.
155 internal links, 8 external
The homepage links to 155 pages on romehealth.org and 8 external pages.
3 checks passed
One H1 headline
Your main headline reads: “Rome Health”.
Canonical URL set
The canonical URL is https://www.romehealth.org/.
robots.txt in place
robots.txt is in place.
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://www.romehealth.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 (806 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages point its canonical at the homepage
https://www.romehealth.org/contact, https://www.romehealth.org/patient-portal-landing, https://www.romehealth.org/foundation, https://www.romehealth.org/hospital-jobs-near-rome-ny, https://www.romehealth.org/news and https://www.romehealth.org/about-us-hospitals-near-rome-ny and 9 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 110 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.”.
2 checks passed
Tap targets are thumb-sized
9 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 500 words of copy
The homepage carries about 500 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “Contact” and “Twigs Gift Shop”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 romehealth.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
- Tailwind CSS
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Company
- Employees
- 799
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 romehealth.org, including 11 speed issues, 7 SEO issues and 4 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.