Website review, no card needed

musso.co logo

musso.co website review

Visit site (opens in a new tab)Reviewed 7 November 202623 issues · 77 checks

This review found 23 issues worth fixing on musso.co, 4 of them high impact, across 77 checks. The most urgent: 1 button without a name. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.2 s624 msMay 16Oct 31690 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026932 ms
May 23, 2026945 ms
May 30, 2026979 ms
Jun 6, 20261.0 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 2026985 ms
Jul 18, 2026955 ms
Jul 25, 2026913 ms
Aug 1, 2026935 ms
Aug 8, 2026932 ms
Aug 15, 2026923 ms
Aug 22, 2026936 ms
Aug 29, 2026908 ms
Sep 5, 2026909 ms
Sep 12, 2026913 ms
Sep 19, 2026871 ms
Sep 26, 2026833 ms
Oct 3, 2026772 ms
Oct 10, 2026714 ms
Oct 17, 2026700 ms
Oct 24, 2026689 ms
Oct 31, 2026690 ms
Real-visitor tap response (INP)75th percentile, phones
277 ms148 msMay 16Oct 31234 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026163 ms
May 23, 2026173 ms
May 30, 2026187 ms
Jun 6, 2026203 ms
Jun 13, 2026196 ms
Jun 20, 2026205 ms
Jun 27, 2026209 ms
Jul 4, 2026214 ms
Jul 11, 2026220 ms
Jul 18, 2026212 ms
Jul 25, 2026212 ms
Aug 1, 2026213 ms
Aug 8, 2026205 ms
Aug 15, 2026215 ms
Aug 22, 2026217 ms
Aug 29, 2026220 ms
Sep 5, 2026236 ms
Sep 12, 2026246 ms
Sep 19, 2026254 ms
Sep 26, 2026256 ms
Oct 3, 2026262 ms
Oct 10, 2026250 ms
Oct 17, 2026245 ms
Oct 24, 2026237 ms
Oct 31, 2026234 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

Full-page screenshot of musso.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. musso.co at 0.4 s0.4 s
  2. musso.co at 0.8 s0.8 s
  3. musso.co at 1.1 s1.1 s
  4. musso.co at 1.5 s1.5 s
  5. musso.co at 1.9 s1.9 s
  6. musso.co at 2.3 s2.3 s
  7. musso.co at 2.6 s2.6 s
  8. musso.co at 3.0 s3.0 s

Speed

2 to fix90
  • Improve image delivery

    361 KiB

    8 images could be 361 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • xcottons.com adds 0 ms

    0 ms

    xcottons.com costs a phone 0 ms of main-thread work and 328 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Unpkg and xcottons.com and others), adding 966 KiB and 0 ms of main-thread time.

  • Reduce unused CSS

    48 KiB

    About 48 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    15 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (15 KiB).

  • Minify CSS

    7 KiB

    7 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.

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 26 ms of it running JavaScript. That is comfortably low.

  • Server response: 16 ms

    16 ms

    Your server sent the HTML in 16 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Tap response (INP) got 40% slower for real visitors

    +40%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 163 ms to 234 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.203

    0.203

    The layout shifts by 0.203 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

12 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: 0.7 s

    0.7 s

    Real visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 115 ms

    115 ms

    Real visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.7 s

    0.7 s

    Real visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 447 ms

    447 ms

    Real visitors wait 447 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 27% faster for real visitors

    -27%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Speed Index: 1.8 s

    1.8 s

    Visually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.4 s

    1.4 s

    The page is fully interactive after 1.4 s.

Images and page weight

2 to fix81
  • Page weight: 2.7 MB in 98 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 98 requests on a phone: images 1.4 MB (34), scripts 984 KiB (38) and fonts 200 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Mobile_Standing_Desk.jpg 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).

  • 1 image in older formats

    1 image (31 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 0.8 g of CO₂ per visit

    0.78 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8490
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 17 text elements with low contrast

    17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (4 elements)

    Links must have discernible text: 4 elements on the page fail 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 (16 elements)

    All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.

  • 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.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9280
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Musso US® Ergonomic Office Chair Official Site | Enjoy Life Seated”.

  • Meta description is long (230 characters)

    Your meta description is 230 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 82 internal links, 13 external

    The homepage links to 82 pages on musso.co and 13 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://musso.co/.

  • Structured data in place

    Structured data found: Organization 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://musso.co/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (703 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://musso.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://musso.co/pages/black-friday-sale-2026, https://musso.co/pages/faq, https://musso.co/pages/mobile-standing-desk, https://musso.co/collections/all, https://musso.co/pages/creators and https://musso.co/pages/about-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://musso.co/pages/faq, https://musso.co/pages/mobile-standing-desk and https://musso.co/pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://musso.co/products/custom-e80-chair-cover-set, https://musso.co/products/pu-silent-universal-wheels-5-pcs, https://musso.co/products/custom-seat-cushion-cover, https://musso.co/collections/all, https://musso.co/pages/creators and https://musso.co/pages/about-us took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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

    16 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 356 words of copy

    The homepage carries about 356 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join Now”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Order Tracking”, “Bulk Order” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 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 musso.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Hulk Form Builder · Inbox · Xcotton Guard · Microsoft Clarity · Judge Me Reviews · Klaviyo Email Marketing Sms · Kaching Bundles · Comparable · Snippets · Easylocation · Discount In Cart · goaffpro.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on musso.co, including 5 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25