Website review, no card needed
todaysgateway.com website review
Visit site (opens in a new tab)Reviewed 31 October 202636 issues · 80 checks
This review found 36 issues worth fixing on todaysgateway.com, 13 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 96 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 97 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 97 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 99 ms |
| Sep 5, 2026 | 100 ms |
| Sep 12, 2026 | 101 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 101 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 101 ms |
| Oct 24, 2026 | 100 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
Use efficient cache lifetimes
6.8 s · 1.4 MB30 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Reduce unused JavaScript
4.5 s · 904 KiBAbout 904 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Improve image delivery
800 ms · 1.1 MB6 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 104 KiBAbout 104 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
500 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
2,691 HTML elements
The page has 2,691 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Vidyard adds 153 ms
153 msVidyard costs a phone 153 ms of main-thread work and 512 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.
6 third-party services on the page
6 third-party services load with your homepage (Vidyard, Adobe Tag Manager and GetSiteControl and others), adding 677 KiB and 236 ms of main-thread time.
Legacy JavaScript
150 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 858 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 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: 14.9 s
14.9 sYour largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 14.9 s
14.9 sThe page becomes fully interactive after 14.9 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 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 TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 400 ms
400 msScripts block taps and scrolling for 400 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 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 96 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 106 ms
106 msReal visitors wait 106 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 88 requests
4.7 MBYour homepage downloads 4.7 MB in 88 requests on a phone: images 2.7 MB (15), scripts 1.6 MB (38) and stylesheets 135 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.32 g of CO₂e: 158.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 buttons without a name
7 buttons have no accessible name, so screen readers announce just “button”.
ARIA dialog and alertdialog nodes should have an accessible name (4 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
Links must have discernible text (2 elements)
Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
2 checks passed
Every image has alt text
All 2 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 5 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Vanderbilt Health” and “Advanced care. Focused on you.”). 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.
No XML sitemap
No XML sitemap at https://www.vanderbilthealth.com/sitemap.xml, so Google discovers your pages only by following links.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
75 internal links, 60 external
The homepage links to 75 pages on todaysgateway.com and 60 external pages.
2 checks passed
Title: 31 characters
Your title is a healthy 31 characters: “Vanderbilt Health Nashville, TN”.
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.vanderbilthealth.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 (997 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.vanderbilthealth.com/information/estimates-and-price-transparency and https://www.vanderbilthealth.com/vanderbilt-health/information/estimates-and-price-transparency all use the title “Estimates and Price Transparency | Vanderbilt Health Nashville, TN”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://www.vanderbilthealth.com/hospital/vanderbilt-bedford-hospital, https://www.vanderbilthealth.com/hospital/vanderbilt-clarksville-hospital, https://www.vanderbilthealth.com/hospital/vanderbilt-tullahoma-harton-hospital, https://www.vanderbilthealth.com/hospital/vanderbilt-wilson-county-hospital, https://www.vanderbilthealth.com/information/estimates-and-price-transparency and https://www.vanderbilthealth.com/doctors and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://www.vanderbilthealth.com/services-we-offer took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 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 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 14 pages that loaded have a <title>.
Best practices
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
74 of 74 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 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 1,660 words of copy
The homepage carries about 1,660 words of visible text.
4 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Learn More” and “Join Our Team”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 8 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
6 cookies set on arrival
6Opening the homepage sets 6 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.
13 other companies contacted
Loading the homepage contacts 13 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 todaysgateway.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
- Next.js
- Hosting
- Vumc
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 todaysgateway.com, including 16 speed issues, 6 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.