Website review, no card needed
surgicaltheater.com website review
Visit site (opens in a new tab)Reviewed 25 October 202642 issues · 80 checks
This review found 42 issues worth fixing on surgicaltheater.com, 13 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
63DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.6 s
3.9 s
5.3 s
6.6 s
7.9 s
9.2 s
10.5 s
Speed
Reduce unused JavaScript
7.2 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.
Render-blocking requests
3.3 s45 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Mobile performance score: 25
25/100Your mobile performance score is 25 (desktop: 34). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (nitrocdn.com, Vimeo and Google Tag Manager and others), adding 40.3 MB and 1.6 s of main-thread time.
Vimeo adds 539 ms
539 msVimeo costs a phone 539 ms of main-thread work and 37.0 MB 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.
nitrocdn.com adds 849 ms
849 msnitrocdn.com costs a phone 849 ms of main-thread work and 3.0 MB 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.
Improve image delivery
1.1 MB17 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
750 ms · 210 KiB19 files are served with short cache lifetimes, so returning visitors download them again (210 KiB).
Reduce unused CSS
610 ms · 149 KiBAbout 149 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 378 ms. During a long task the page ignores taps.
1,570 HTML elements
The page has 1,570 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
21 KiB21 KiB could be saved by minifying CSS.
Legacy JavaScript
10 KiBPolyfills 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 15.0 s
15.0 sThe first text or image appears after 15.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 23.5 s
23.5 sYour largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “XR That Powers Surgical Visualization”.
Speed Index: 17.9 s
17.9 sVisually, the page fills in at 17.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 31.2 s
31.2 sThe page becomes fully interactive after 31.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.726
0.726The layout shifts by 0.726 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 299 ms
299 msScripts block taps and scrolling for 299 ms in total while the page loads. Good is under 200 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
Images and page weight
Page weight: 43.2 MB in 256 requests
43.2 MBYour homepage downloads 43.2 MB in 256 requests on a phone: other files 35.0 MB (78), media 2.8 MB (1) and scripts 2.4 MB (61). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.1 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.
10 images below the first screen load straight away
10 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
338 KiB4 images are downloaded at several times the size a phone draws them, for example burak-ozgur-testimonial.jpg at 1,529 px wide, shown at 343 px. Resized copies would save about 338 KiB.
About 12.2 g of CO₂ per visit
12.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 12.24 g of CO₂e: 1468.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Surgical Theater: Pioneering XR in Healthcare for Enhanced Surgical Precision”.
Meta description is long (227 characters)
Your meta description is 227 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 3 problems
Structured data found (Article, ImageObject, MedicalBusiness and Organization) but with 3 problems, for example “ImageObject: url is not an absolute URL ("https://surgicaltheater.com/wp-content/uploads/2024/01/Sc…”.
78 internal links, 19 external
The homepage links to 78 pages on surgicaltheater.com and 19 external pages.
5 checks passed
One H1 headline
Your main headline reads: “XR That Powers Surgical Visualization”.
Canonical URL set
The canonical URL is https://surgicaltheater.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://surgicaltheater.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://surgicaltheater.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 (1,092 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://surgicaltheater.com/unsubscribe is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
7 pages slow to respond
https://surgicaltheater.com/planxr, https://surgicaltheater.com/brainstorm, https://surgicaltheater.com/surgical-planning, https://surgicaltheater.com/patient-engagement, https://surgicaltheater.com/about and https://surgicaltheater.com/media and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
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: 128 testimonial or review blocks. 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 852 words of copy
The homepage carries about 852 words of visible text.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Request A Demo Today”, “Contact” and “Contact Us”.
Analytics in place
Analytics detected: Google Analytics and LinkedIn Insight.
Opening hours shown
Your opening hours are on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and LinkedIn Insight (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 2 of them by other companies (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.
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 surgicaltheater.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 Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on surgicaltheater.com, including 19 speed issues, 3 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.