surgalign.com website review

97 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

45 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.6 s.

3 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

About 365 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

Your mobile performance score is 53 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

3 long tasks block the main thread while loading, the longest for 275 ms. During a long task the page ignores taps.

Google Maps costs a phone 192 ms of main-thread work and 384 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.

3 third-party services load with your homepage (Google Maps, cdn-cookieyes.com and Google Fonts), adding 605 KiB and 255 ms of main-thread time.

About 73 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

13 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

The first text or image appears after 7.7 s on a phone. Good is under 1.8 s.

Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “From our roots as a Montana-based tissue bank to a recogniz…”.

The page becomes fully interactive after 23.7 s. Good is under 3.8 s.

Visually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 63 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 225 ms in total while the page loads. Good is under 200 ms.

7 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 5.3 MB in 124 requests on a phone: images 3.6 MB (22), scripts 928 KiB (42) and fonts 332 KiB (5). Under 2 MB keeps phones on slow connections fast.

Xtant-Medical-Blue-Green-Day-Group-Photo-scaled.jpg weighs 1.3 MB. On a phone connection a single image that size takes seconds.

3 images (1.5 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.50 g of CO₂e: 180.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 20 characters: “Home – Xtant Medical”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“Precision.”, “Performance.” and “Progress.”). One clear main headline is easier for people and search engines.

The homepage links to 132 pages on surgalign.com and 12 external pages.

There is no https://xtantmedical.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.

https://xtantmedical.com/biologics, https://xtantmedical.com/product-category/biologics/allogeneic-proteins, https://xtantmedical.com/product-category/biologics/surgical-adjunct, https://xtantmedical.com/product-category/biologics/demineralized-bone-matrix-dbm, https://xtantmedical.com/product-category/biologics/precision-milled-allografts and https://xtantmedical.com/product-category/biologics/sports-medicine-allografts and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://xtantmedical.com/biologics, https://xtantmedical.com/product-category/biologics/allogeneic-proteins, https://xtantmedical.com/product-category/biologics/surgical-adjunct, https://xtantmedical.com/product-category/biologics/demineralized-bone-matrix-dbm, https://xtantmedical.com/product-category/biologics/precision-milled-allografts and https://xtantmedical.com/product-category/biologics/sports-medicine-allografts and 4 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 379 words of visible text.

Opening the homepage sets 8 cookies (measured from a US location before any click).

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.