Website review, no card needed
cswo.com website review
Visit site (opens in a new tab)Reviewed 25 October 202639 issues · 75 checks
This review found 39 issues worth fixing on cswo.com, 13 of them high impact, across 75 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
70CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
3.0 s · 539 KiBAbout 539 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 364 KiB31 files are served with short cache lifetimes, so returning visitors download them again (364 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 6.0 MB and 1.3 s of main-thread time.
Google Tag Manager adds 940 ms
940 msGoogle Tag Manager costs a phone 940 ms of main-thread work and 866 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.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 72). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
739 KiB9 images could be 739 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
450 ms · 83 KiBAbout 83 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.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 4.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.
Legacy JavaScript
300 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 297 ms. During a long task the page ignores taps.
Facebook adds 260 ms
260 msFacebook costs a phone 260 ms of main-thread work and 266 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: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
furnituredealer.net adds 0 ms
0 msfurnituredealer.net costs a phone 0 ms of main-thread work and 930 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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: 25 ms
25 msYour server sent the HTML in 25 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 23.6 s
23.6 sThe first text or image appears after 23.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 34.8 s
34.8 sYour largest element takes 34.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “C.S. Wo & Sons”.
Speed Index: 23.6 s
23.6 sVisually, the page fills in at 23.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 35.0 s
35.0 sThe page becomes fully interactive after 35.0 s. Good is under 3.8 s.
20 images without width and height
20 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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.3 MB in 78 requests
6.3 MBYour homepage downloads 6.3 MB in 78 requests on a phone: fonts 4.0 MB (4), scripts 1.3 MB (39) and images 910 KiB (17). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
545f79cd-bf73-46b7-8d8b-c0b83aaf885c.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.8 g of CO₂ per visit
1.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (80 characters)
Your title is 80 characters, so Google will cut it off around 60: “C. S. Wo & Sons, LLC | Hawaii, Oahu, Hilo, Kona, Maui Furniture & Mattress Store”.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.
No social preview image
No Open Graph image, 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.
31 internal links, 32 external
The homepage links to 31 pages on cswo.com and 32 external pages.
4 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Shop C. S. Wo & Sons, Ltd. for an amazing selection of Furniture & Mattress in the Hawaii, Oahu, Hilo, Kona, Ma…”.
One H1 headline
Your main headline reads: “Discover and elevate your lifestylewith the C. S. WO & Sons family of local brands—A legacy of quality, style, and inno…”.
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.cswo.com/sitemap.xml.
AI search readiness
robots.txt blocks 1 AI answer engine crawler
1 of 6Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.cswo.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (383 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.cswo.com/privacy-policy, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without an H1
https://www.cswo.com/furniturepackages has no <h1> headline, so visitors and search engines get no clear main topic.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 8 pages that loaded have a meta description.
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 8 pages that loaded have a <title>.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://images.furnituredealer.net/rodeo/prod/fc91217e639dedf8bd06d6ea2e77dcfa/f32b89bca1f…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
20 of 20 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 299 words of copy
The homepage carries about 299 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
18 other companies contacted
Loading the homepage contacts 18 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 cswo.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
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on cswo.com, including 19 speed issues, 4 SEO issues and 4 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.