Website review, no card needed
swsh.com website review
Visit site (opens in a new tab)Reviewed 19 November 202650 issues · 86 checks
This review found 50 issues worth fixing on swsh.com, 19 of them high impact, across 86 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
65DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
31.9 s · 36.8 MB19 images could be 36.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 31.9 s faster on a phone.
Use efficient cache lifetimes
4.0 s · 701 KiB15 files are served with short cache lifetimes, so returning visitors download them again (701 KiB).
Reduce unused JavaScript
3.4 s · 650 KiBAbout 650 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.
Reduce unused CSS
1.0 s · 81 KiBAbout 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 s faster on a phone.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Google Maps and YouTube and others), adding 892 KiB and 1.0 s of main-thread time.
Google Tag Manager adds 949 ms
949 msGoogle Tag Manager costs a phone 949 ms of main-thread work and 714 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.
Render-blocking requests
900 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Minify JavaScript
460 ms · 92 KiB92 KiB could be saved by minifying JavaScript.
Legacy JavaScript
300 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 248 ms. During a long task the page ignores taps.
Minify CSS
180 ms · 21 KiB21 KiB could be saved by minifying CSS.
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: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 65.6 s
65.6 sYour largest element takes 65.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Clean Dose Program An effective, easy-to-use tablet cleanin…”.
Time to Interactive: 66.9 s
66.9 sThe page becomes fully interactive after 66.9 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
2 images without width and height
2 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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 50.2 MB in 55 requests
50.2 MBYour homepage downloads 50.2 MB in 55 requests on a phone: images 48.8 MB (26), scripts 1.2 MB (13) and fonts 171 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (376 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
67 KiB1 image is downloaded at several times the size a phone draws it, for example full.ashx at 1,098 px wide, shown at 332 px. Resized copies would save about 67 KiB.
1 image in older formats
1 image (376 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 14.2 g of CO₂ per visit
14.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 14.24 g of CO₂e: 1708.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
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.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (7 characters)
Your title is only 7 characters: “Swisher”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 H1 headlines
There are 4 <h1> headlines (“Clean Dose Program”, “Rapid Multi Surface Disinfectant Cleaner (Swisher…” and “Liquid Warewashing Program”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://swsh.com/sitemap.xml, so Google discovers your pages only by following links.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
157 internal links, 4 external
The homepage links to 157 pages on swsh.com and 4 external pages.
1 checks passed
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://swsh.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 (637 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://swsh.com/about-us and https://swsh.com/product-categories 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://swsh.com/product-categories/category/swisher-heavy-duty-degreaser-and-floor-cleaner, whose canonical is https://swsh.com/products/swisher-heavy-duty-degreaser-and-floor-cleaner. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://swsh.com/about-us has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
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
5 small tap targets
5 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://www.googleadservices.com/pagead/conversion/797099081/?random=1795108573071&cv=11&fst=17951085730…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 384 words of copy
The homepage carries about 384 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT” and “Learn More”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Learn More” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
9 other companies contacted
Loading the homepage contacts 9 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 swsh.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on swsh.com, including 17 speed issues, 9 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.