Website review, no card needed
ad-surgical.com website review
Visit site (opens in a new tab)Reviewed 17 November 202656 issues · 87 checks
This review found 56 issues worth fixing on ad-surgical.com, 23 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
61D- #112,739 of 116,487 reviewed websitesbeats 3%
- #65,961 of 66,776 online storesbeats 1%
- #854 of 882 BigCommerce storesbeats 2%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 117 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 114 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 120 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 121 ms |
| Nov 7, 2026 | 121 ms |
| Nov 14, 2026 | 120 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One 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.0 s
3.8 s
4.5 s
5.3 s
6.1 s
Speed
Improve image delivery
13.5 s · 2.8 MB5 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.5 s faster on a phone.
Reduce unused JavaScript
9.8 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.8 s faster on a phone.
Use efficient cache lifetimes
5.5 s · 1.0 MB23 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Render-blocking requests
1.1 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 17
17/100Your mobile performance score is 17. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Bigcommerce and Google CDN and others), adding 2.9 MB and 2.1 s of main-thread time.
Google Tag Manager adds 771 ms
771 msGoogle Tag Manager costs a phone 771 ms of main-thread work and 1.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.
Reduce unused CSS
660 ms · 154 KiBAbout 154 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 660 ms faster on a phone.
Bigcommerce adds 484 ms
484 msBigcommerce costs a phone 484 ms of main-thread work and 632 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.
Google CDN adds 413 ms
413 msGoogle CDN costs a phone 413 ms of main-thread work and 600 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 359 ms. During a long task the page ignores taps.
1,899 HTML elements
The page has 1,899 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 38.7 s
38.7 sYour largest element takes 38.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 38.7 s
38.7 sThe page becomes fully interactive after 38.7 s. Good is under 3.8 s.
First Contentful Paint: 6.2 s
6.2 sThe first text or image appears after 6.2 s on a phone. Good is under 1.8 s.
Speed Index: 12.1 s
12.1 sVisually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.257
0.257The layout shifts by 0.257 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 959 ms
959 msReal visitors wait 959 ms for your server to start answering (75th percentile). Good is under 800 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 106 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 6.5 MB in 201 requests
6.5 MBYour homepage downloads 6.5 MB in 201 requests on a phone: scripts 3.0 MB (109), images 2.9 MB (19) and fonts 220 KiB (10). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
1.8 MB4 images are downloaded at several times the size a phone draws them, for example Pasted.jpg at 2,453 px wide, shown at 280 px. Resized copies would save about 1.8 MB.
3 images in older formats
3 images (2.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.
2 images below the first screen load straight away
2 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.84 g of CO₂e: 220.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
Orphan list items
Some list items are not inside a list.
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.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
47 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: 47 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
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 XML sitemap
No XML sitemap at https://ad-surgical.com/sitemap.xml, so Google discovers your pages only by following links.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
333 internal links, 5 external
The homepage links to 333 pages on ad-surgical.com and 5 external pages.
3 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “AD SURGICAL - A Trusted Medical Product Supplier Since 2000”.
Canonical URL set
The canonical URL is https://ad-surgical.com/.
robots.txt in place
robots.txt is in place.
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://ad-surgical.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,155 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 187 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5223207&Ver=2&mid=22f72abf-c562-4c37-8257-4a571693d3b7&bo=1&sid=e394e1f0e28111f19cd7f58ffc94a256&vid=e39505c0e28111f1ab718590659c93ca&vids=1&msclkid=N&pi=918639831&lg=.
9 small tap targets
9 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Unexpected end of input”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 249 words
The homepage has only about 249 words of visible text; thin pages give Google and first-time buyers little to go on.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Sign Up” and “Learn More About Us”.
14 calls to action
The homepage has 14 calls to action, for example “Sign Up”, “Contact Us” and “Shop All”.
4 short forms
4 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
36 other companies contacted
Loading the homepage contacts 36 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 ad-surgical.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- BigCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Bigcommerce Inc.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 56 issues on ad-surgical.com, including 25 speed issues, 7 SEO issues and 2 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.