Website review, no card needed

surgeonsolution.io logo

surgeonsolution.io website review

Visit site (opens in a new tab)Reviewed 21 November 202632 issues · 83 checks

This review found 32 issues worth fixing on surgeonsolution.io, 12 of them high impact, across 83 checks. The most urgent: main-thread work: 19.2 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of surgeonsolution.io (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. surgeonsolution.io at 1.2 s1.2 s
  2. surgeonsolution.io at 2.4 s2.4 s
  3. surgeonsolution.io at 3.6 s3.6 s
  4. surgeonsolution.io at 4.8 s4.8 s
  5. surgeonsolution.io at 6.0 s6.0 s
  6. surgeonsolution.io at 7.1 s7.1 s
  7. surgeonsolution.io at 8.3 s8.3 s
  8. surgeonsolution.io at 9.5 s9.5 s

Speed

7 to fix67
  • Main-thread work: 19.2 s

    A phone's processor spends 19.2 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,307 HTML elements

    The page has 3,307 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    450 ms · 620 KiB

    12 images could be 620 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    423 KiB

    About 423 KiB of JavaScript is downloaded but never used on this page.

  • Google CDN adds 148 ms

    148 ms

    Google CDN costs a phone 148 ms of main-thread work and 298 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.

  • Shopify adds 28 ms

    28 ms

    Shopify costs a phone 28 ms of main-thread work and 379 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and surgeonsolutions.org and others), adding 944 KiB and 313 ms of main-thread time.

  • Font display

    200 ms

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

  • 5 long tasks on the main thread

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

  • Render-blocking requests

    100 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

  • Use efficient cache lifetimes

    58 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (58 KiB).

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

1 checks passed
  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix66
  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Surgeons Logo in gold: Animation”.

  • Speed Index: 7.4 s

    7.4 s

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

  • Time to Interactive: 8.6 s

    8.6 s

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

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

3 checks passed
  • Total Blocking Time: 188 ms

    188 ms

    Scripts block the page for only 188 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.079

    0.079

    The layout barely moves while loading (CLS 0.079, good is under 0.1).

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

Images and page weight

4 to fix38
  • Page weight: 5.2 MB in 231 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 231 requests on a phone: images 2.9 MB (35), other files 1,007 KiB (137) and scripts 908 KiB (41). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Untitled_design_6.svg weighs 731 KiB. On a phone connection a single image that size takes seconds.

  • 4 images below the first screen load straight away

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

  • 1 image far larger than shown

    378 KiB

    1 image is downloaded at several times the size a phone draws it, for example Untitled_design_6.svg at 1,080 px wide, shown at 250 px. Resized copies would save about 378 KiB.

  • About 1.5 g of CO₂ per visit

    1.48 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

10 to fixGoogle 9089
  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • Meta description is long (199 characters)

    Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 9 links with vague text

    9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 109 internal links, 22 external

    The homepage links to 109 pages on surgeonsolution.io and 22 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Premium Full Spectrum CBD Gummies & Cannabinoid Oils |Michigan USA”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Michigan's Best Full Spectrum CBD Gummies, Oils & More | Shop Now”.

  • Canonical URL set

    The canonical URL is https://www.surgeonsolution.io/.

  • Structured data in place

    Structured data found: FAQPage, LocalBusiness, Organization, WebPage and WebSite.

  • 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://surgeonsolution.io/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,232 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://surgeonsolution.io/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://surgeonsolution.io/customer_authentication/redirect, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages without a meta description

    https://surgeonsolution.io/collections/all, https://surgeonsolution.io/policies/privacy-policy, https://surgeonsolution.io/policies/terms-of-service and https://surgeonsolution.io/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://surgeonsolution.io/pages/collab, whose canonical is https://surgeonsolution.io/pages/partnerships-opportunities-collaborations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 6991
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    55 of 57 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 2,017 words of copy

    The homepage carries about 2,017 words of visible text.

10 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start selling with us” and “Call Now”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop Now & Save 15%”, “Start selling with us” and “Login/signup”.

  • 8 short forms

    8 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 surgeonsolution.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Forms · trustpilot.com · Swym Wishlist Plus

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on surgeonsolution.io, including 10 speed issues and 2 SEO issues. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25