Website review, no card needed
sandosurgical.com website review
Visit site (opens in a new tab)Reviewed 21 November 202629 issues · 74 checks
This review found 29 issues worth fixing on sandosurgical.com, 10 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. 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
77C- #69,633 of 125,680 reviewed websitesbeats 39%
- #44,815 of 70,239 online storesbeats 31%
- #1,113 of 2,950 WooCommerce storesbeats 57%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.5 s
2.3 s
3.1 s
3.8 s
4.6 s
5.4 s
6.1 s
Speed
Use efficient cache lifetimes
1.6 s · 543 KiB45 files are served with short cache lifetimes, so returning visitors download them again (543 KiB).
Reduce unused JavaScript
1.5 s · 283 KiBAbout 283 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.1 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Minify JavaScript
600 ms · 126 KiB126 KiB could be saved by minifying JavaScript.
Improve image delivery
226 KiB2 images could be 226 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
170 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 180 KiB and 176 ms of main-thread time.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 496 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.3 s
6.3 sYour largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LASER equipment sales and services”. Most of its time is element render delay (5.4 s).
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.6 s
6.6 sThe page becomes fully interactive after 6.6 s. Good is under 3.8 s.
5 images without width and height
5 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.
3 checks passed
Total Blocking Time: 154 ms
154 msScripts block the page for only 154 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.5 MB in 49 requests
1.5 MBYour homepage downloads 1.5 MB in 49 requests on a phone: images 803 KiB (20), scripts 588 KiB (14) and fonts 86 KiB (4). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
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 (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“LASER equipment sales and services” and “Our clients trust us”). One clear main headline is easier for people and search engines.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
28 internal links, 5 external
The homepage links to 28 pages on sandosurgical.com and 5 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.sandosurgical.com/.
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://www.sandosurgical.com/wp-sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.sandosurgical.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 (672 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a title
https://www.sandosurgical.com/shop, https://www.sandosurgical.com/surgical-laser, https://www.sandosurgical.com/phaco-maintenance, https://www.sandosurgical.com/specialty-biomedical, https://www.sandosurgical.com/career and https://www.sandosurgical.com/%d1%81ontacts and 5 others have no <title>, so Google invents the link text in results.
11 pages without a meta description
https://www.sandosurgical.com/shop, https://www.sandosurgical.com/surgical-laser, https://www.sandosurgical.com/phaco-maintenance, https://www.sandosurgical.com/specialty-biomedical, https://www.sandosurgical.com/career and https://www.sandosurgical.com/%d1%81ontacts and 5 others 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://www.sandosurgical.com/privacy-policy-2, whose canonical is https://www.sandosurgical.com/privacy-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages without an H1
https://www.sandosurgical.com/shop, https://www.sandosurgical.com/career, https://www.sandosurgical.com/product-category/aesthetic-2, https://www.sandosurgical.com/product-category/equipment-sales, https://www.sandosurgical.com/product-category/ophthalmic and https://www.sandosurgical.com/product-category/surgical have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.sandosurgical.com/shop, https://www.sandosurgical.com/surgical-laser, https://www.sandosurgical.com/phaco-maintenance, https://www.sandosurgical.com/specialty-biomedical, https://www.sandosurgical.com/career and https://www.sandosurgical.com/%d1%81ontacts took over 3 s to send their HTML from our server.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
2 checks passed
Linked pages load
All 11 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
9 small tap targets
9 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 13-field form
Your longest form asks for 13 fields (10 required). Every extra field lowers completion.
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 477 words of copy
The homepage carries about 477 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Request a service”.
7 calls to action
The homepage has 7 calls to action, for example “Contact us”, “Request a service” and “Join the team”.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks and 2 customer or partner logos.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
2 other companies contacted
Loading the homepage contacts 2 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 sandosurgical.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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- Sucuri
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on sandosurgical.com, including 9 speed issues, 5 SEO issues and 1 conversion gap. 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.