Website review, no card needed
surgerypartners.com website review
Visit site (opens in a new tab)Reviewed 27 October 202620 issues · 74 checks
This review found 20 issues worth fixing on surgerypartners.com, 5 of them high impact, across 74 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Surgery Partners
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 625 ms |
| May 16, 2026 | 601 ms |
| May 23, 2026 | 580 ms |
| May 30, 2026 | 573 ms |
| Jun 6, 2026 | 544 ms |
| Jun 13, 2026 | 565 ms |
| Jun 20, 2026 | 573 ms |
| Jun 27, 2026 | 629 ms |
| Jul 4, 2026 | 624 ms |
| Jul 11, 2026 | 605 ms |
| Jul 18, 2026 | 584 ms |
| Jul 25, 2026 | 573 ms |
| Aug 1, 2026 | 576 ms |
| Aug 8, 2026 | 548 ms |
| Aug 15, 2026 | 594 ms |
| Aug 22, 2026 | 594 ms |
| Aug 29, 2026 | 583 ms |
| Sep 5, 2026 | 598 ms |
| Sep 12, 2026 | 580 ms |
| Sep 19, 2026 | 564 ms |
| Sep 26, 2026 | 575 ms |
| Oct 3, 2026 | 599 ms |
| Oct 10, 2026 | 612 ms |
| Oct 17, 2026 | 612 ms |
| Oct 24, 2026 | 636 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 63 ms |
| May 16, 2026 | 63 ms |
| May 23, 2026 | 63 ms |
| May 30, 2026 | 62 ms |
| Jun 6, 2026 | 62 ms |
| Jun 13, 2026 | 62 ms |
| Jun 20, 2026 | 62 ms |
| Jun 27, 2026 | 63 ms |
| Jul 4, 2026 | 64 ms |
| Jul 11, 2026 | 63 ms |
| Jul 18, 2026 | 64 ms |
| Jul 25, 2026 | 63 ms |
| Aug 1, 2026 | 67 ms |
| Aug 8, 2026 | 66 ms |
| Aug 15, 2026 | 63 ms |
| Aug 22, 2026 | 63 ms |
| Aug 29, 2026 | 62 ms |
| Sep 5, 2026 | 61 ms |
| Sep 12, 2026 | 62 ms |
| Sep 19, 2026 | 62 ms |
| Sep 26, 2026 | 62 ms |
| Oct 3, 2026 | 66 ms |
| Oct 10, 2026 | 69 ms |
| Oct 17, 2026 | 70 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
2.3 s · 392 KiB4 images could be 392 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
1.0 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 89
89/100Your mobile performance score is 89 (desktop: 79). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 98 KiBAbout 98 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 61 KiB61 KiB could be saved by minifying JavaScript.
Reduce unused CSS
150 ms · 27 KiBAbout 27 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.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 0.2 s
A phone's processor spends 0.2 s on main-thread work while loading, 48 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: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Surgery Partners is a leading operator of surgical faciliti…”.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 63 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
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.6 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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: 0.6 s
0.6 sReal visitors wait 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 63 ms
63 msReal visitors wait 63 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: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 315 ms
315 msReal visitors wait 315 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 3.8 s
3.8 sThe page is fully interactive after 3.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Speed Index: 1.6 s
1.6 sVisually, the page fills in at 1.6 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
3 images far larger than shown
11 KiB3 images are downloaded at several times the size a phone draws them, for example [email protected] at 1,040 px wide, shown at 342 px. Resized copies would save about 11 KiB.
4 images in older formats
4 images (442 KiB) 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.
3 images below the first screen load straight away
3 images further down the page (250 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.2 g of CO₂ per visit
0.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.21 g of CO₂e: 24.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 747 KiB in 43 requests
747 KiBYour homepage downloads 747 KiB in 43 requests on a phone: images 450 KiB (6), scripts 234 KiB (24) and stylesheets 50 KiB (12). That is a lean page.
Accessibility
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (23 characters)
Your title is only 23 characters: “Home | Surgery Partners”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (MedicalOrganization) but with 1 problem, for example “MedicalOrganization: logo is not an absolute URL ("../../assets/images/logo.png")”.
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.
No XML sitemap
No XML sitemap at https://surgerypartners.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
19 internal links, 4 external
The homepage links to 19 pages on surgerypartners.com and 4 external pages.
3 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Surgery Partners, a leading operator of surgical facilities and ancillary services, provides healthcare experiences bet…”.
Canonical URL set
The canonical URL is https://surgerypartners.com/.
robots.txt in place
robots.txt is in place.
AI search readiness
No llms.txt
There is no https://surgerypartners.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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (397 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://surgerypartners.com/resources and https://surgerypartners.com/facilities have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://surgerypartners.com/about-us, https://surgerypartners.com/careers, https://surgerypartners.com/partnerships, https://surgerypartners.com/physician-careers, https://surgerypartners.com/node/276 and https://surgerypartners.com/vendorproof use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://surgerypartners.com/careers, whose canonical is https://surgerypartners.com/spcareers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://surgerypartners.com/node/276 and https://surgerypartners.com/vendorproof have no <h1> headline, so visitors and search engines get no clear main topic.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
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 8 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
10 of 12 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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 303 words of copy
The homepage carries about 303 words of visible text.
4 checks passed
1 short form
A short form (4 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 5 customer or partner logos and “more than 670,000 patients”.
Direct contact links
Visitors can reach you directly: 1 phone link 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
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.
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 surgerypartners.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
- Pantheon
Hiring
- Hiring
- 104 open roles
- Teams
- Nursing (32), Technicians (30), Administrative-Clerical (11), Administration (5)
- Job board
- greenhouse
Company
- Employees
- 8,509
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on surgerypartners.com, including 5 speed issues, 5 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.