spine-3d.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 6.5 s

  6.5 s

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

• Real-user FCP: 5.4 s

  5.4 s

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

• Largest content (LCP) got 18% slower for real visitors

  +18%

  Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 5.7 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 5.7 MB

  5.7 MB

  Your homepage downloads 5.7 MB on a phone, 3.3 MB of it images (58%). Under 2 MB keeps phones on slow connections fast.

• 7 images in older formats

  7 images (1.2 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.

  Elements (5)

• 5 images below the first screen load straight away

  5 images further down the page (755 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• 1 image far larger than shown

  149 KiB

  1 image is downloaded at several times the size a phone draws it, for example id-21815-DM_testata_nopayoff-e1463225645668.png at 700 px wide, shown at 50 px. Resized copies would save about 149 KiB.

  Elements (1)

• About 1.6 g of CO₂ per visit

  1.62 g

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

• [role="img"] and [role="image"] elements must have alternative text (9 elements)

  [role="img"] and [role="image"] elements must have alternative text: 9 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• 5 text elements with low contrast

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

  Elements (3)

• 3 tap targets too small

  3 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

• All page content should be contained by landmarks (39 elements)

  All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• 17 links without text

  17 visible links have no text or label, so screen readers cannot say where they go.

  Elements (3)

• 4 form fields without a label

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

  View source

• Headings skip levels

  Headings skip levels (h2 → h6, h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.

  View sourceElements (3)

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• 45 internal links, 7 external

  The homepage links to 45 pages on spine-3d.com and 7 external pages.

• No llms.txt

  There is no https://spine-3d.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.

• 4 pages without a meta description

  https://spine-3d.com/about, https://spine-3d.com/blog, https://spine-3d.com/press and https://spine-3d.com/category/causes have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (4)

• 1 page without an H1

  https://spine-3d.com/category/causes has no <h1> headline, so visitors and search engines get no clear main topic.

• 4 pages slow to respond

  https://spine-3d.com/about, https://spine-3d.com/blog, https://spine-3d.com/press and https://spine-3d.com/category/causes took over 3 s to send their HTML from our server.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage and read each the way a search engine does.

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'slidesToShow')”.

• 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.

• Thin social proof

  Social proof on the homepage: 1 testimonial or review block. 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.

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

• 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 780 words of copy

  The homepage carries about 780 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• 3 cookies set on arrival

  3

  Opening the homepage sets 3 cookies, 1 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.