Website review, no card needed
surgicallycleanair.com website review
Visit site (opens in a new tab)Reviewed 21 October 202629 issues · 83 checks
This review found 29 issues worth fixing on surgicallycleanair.com, 8 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 956 ms |
| Aug 8, 2026 | 880 ms |
| Aug 15, 2026 | 909 ms |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 71 ms |
| May 9, 2026 | 71 ms |
| May 16, 2026 | 79 ms |
| May 23, 2026 | 102 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 98 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 94 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 88 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 91 ms |
| Sep 12, 2026 | 86 ms |
| Sep 19, 2026 | 89 ms |
| Sep 26, 2026 | 100 ms |
| Oct 3, 2026 | 108 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 103 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
7.8 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.8 s faster on a phone.
Use efficient cache lifetimes
3.1 s · 416 KiB10 files are served with short cache lifetimes, so returning visitors download them again (416 KiB).
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 62). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Hubspot and others), adding 2.5 MB and 1.4 s of main-thread time.
Improve image delivery
850 ms · 357 KiB12 images could be 357 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
Google CDN adds 683 ms
683 msGoogle CDN costs a phone 683 ms of main-thread work and 1.5 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
450 ms · 77 KiBAbout 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
450 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Google Tag Manager adds 360 ms
360 msGoogle Tag Manager costs a phone 360 ms of main-thread work and 483 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Hubspot adds 220 ms
220 msHubspot costs a phone 220 ms of main-thread work and 401 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 11.1 s
11.1 sThe first text or image appears after 11.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.0 s
17.0 sYour largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Medical-Grade Air Purifiers for Clinics, Classrooms, and th…”.
Time to Interactive: 17.7 s
17.7 sThe page becomes fully interactive after 17.7 s. Good is under 3.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 51% slower for real visitors
+51%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 71 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 367 ms
367 msScripts block taps and scrolling for 367 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 101 ms
101 msReal visitors wait 101 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 687 ms
687 msReal visitors wait 687 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 59% faster for real visitors
-59%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 66 requests
3.9 MBYour homepage downloads 3.9 MB in 66 requests on a phone: scripts 2.3 MB (19), other files 715 KiB (11) and images 524 KiB (24). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
138 KiB3 images are downloaded at several times the size a phone draws them, for example jade-2-video-opener.webp at 3,468 px wide, shown at 342 px. Resized copies would save about 138 KiB.
3 images below the first screen load straight away
3 images further down the page (219 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (93 KiB) is 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.
About 1.1 g of CO₂ per visit
1.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 131.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
25 text elements with low contrast
25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
118 internal links, 3 external
The homepage links to 118 pages on surgicallycleanair.com and 3 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Medical air purifiers with 5-stage HEPA-Rx filtration and UV-C, trusted by 55,000+ healthcare facilities. UL, ETL and C…”.
One H1 headline
Your main headline reads: “Medical-Grade Air Purifiers for Clinics, Classrooms, and the Spaces You Call Home”.
Title: 56 characters
Your title is a healthy 56 characters: “Medical-Grade Air Purifiers for Clinics, Schools & Homes”.
Canonical URL set
The canonical URL is https://surgicallycleanair.com/.
Structured data in place
Structured data found: FAQPage, Organization, Product, WebPage and WebSite.
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://surgicallycleanair.com/wp-sitemap.xml.
AI search readiness
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 (1,266 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://surgicallycleanair.com/llms.txt (4 KiB, 34 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 59 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
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 ()”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,143 words of copy
The homepage carries about 1,143 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Air Purifiers” and “Talk to Sales”.
12 calls to action
The homepage has 12 calls to action, for example “Contact”, “Shop Air Purifiers” and “Talk to Sales”.
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 31 testimonial or review blocks, 17 customer or partner logos, a star rating and 9 trust badges.
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
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.
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 surgicallycleanair.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
- Analytics
- Google Analytics
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 surgicallycleanair.com, including 18 speed issues, 3 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.