Website review, no card needed

shopbycomo.com logo

shopbycomo.com website review

Visit site (opens in a new tab)Reviewed 16 November 202632 issues · 79 checks

This review found 32 issues worth fixing on shopbycomo.com, 11 of them high impact, across 79 checks. The most urgent: page weight: 52.6 MB in 197 requests. 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
2.1 s1.3 sMay 30Nov 141.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.5 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20261.6 s
Nov 7, 20261.7 s
Nov 14, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
205 ms64 msMay 30Nov 14110 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202680 ms
Jun 6, 202681 ms
Jun 13, 202683 ms
Jun 20, 202681 ms
Jul 4, 2026103 ms
Jul 11, 2026103 ms
Jul 18, 202695 ms
Jul 25, 2026113 ms
Aug 1, 202684 ms
Aug 8, 202684 ms
Aug 15, 202688 ms
Aug 22, 202690 ms
Aug 29, 2026104 ms
Sep 5, 2026128 ms
Sep 12, 2026172 ms
Sep 19, 2026172 ms
Sep 26, 2026189 ms
Oct 3, 2026174 ms
Oct 17, 2026121 ms
Oct 24, 2026120 ms
Oct 31, 2026104 ms
Nov 7, 2026106 ms
Nov 14, 2026110 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 shopbycomo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shopbycomo.com at 0.8 s0.8 s
  2. shopbycomo.com at 1.7 s1.7 s
  3. shopbycomo.com at 2.5 s2.5 s
  4. shopbycomo.com at 3.4 s3.4 s
  5. shopbycomo.com at 4.2 s4.2 s
  6. shopbycomo.com at 5.1 s5.1 s
  7. shopbycomo.com at 5.9 s5.9 s
  8. shopbycomo.com at 6.7 s6.7 s

Speed

10 to fix48
  • Reduce unused JavaScript

    1.4 s · 323 KiB

    About 323 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48. 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.6 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 (Shopify, Klaviyo and Optanon and others), adding 51.2 MB and 965 ms of main-thread time.

  • Shopify adds 317 ms

    317 ms

    Shopify costs a phone 317 ms of main-thread work and 50.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.

  • Render-blocking requests

    550 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

  • Use efficient cache lifetimes

    300 ms · 80 KiB

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

  • Klaviyo adds 277 ms

    277 ms

    Klaviyo costs a phone 277 ms of main-thread work and 387 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.

  • 15 long tasks on the main thread

    15 long tasks block the main thread while loading, the longest for 288 ms. During a long task the page ignores taps.

  • 1,782 HTML elements

    The page has 1,782 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    250 ms · 39 KiB

    Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 84 KiB

    About 84 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    77 KiB

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

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

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We would like to use cookies to give you the best experienc…”.

  • Time to Interactive: 12.7 s

    12.7 s

    The page becomes fully interactive after 12.7 s. Good is under 3.8 s.

  • Speed Index: 8.2 s

    8.2 s

    Visually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 807 ms

    807 ms

    Scripts block taps and scrolling for 807 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) got 34% slower for real visitors

    +34%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

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

    1.5 s

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

  • Real-user INP: 110 ms

    110 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 465 ms

    465 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.039

    0.039

    The layout barely moves while loading (CLS 0.039, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 52.6 MB in 197 requests

    52.6 MB

    Your homepage downloads 52.6 MB in 197 requests on a phone: media 50.2 MB (3), scripts 1.1 MB (71) and other files 699 KiB (87). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • About 14.9 g of CO₂ per visit

    14.91 g

    By the Sustainable Web Design model, a visit to your homepage emits about 14.91 g of CO₂e: 1789.8 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

3 to fixGoogle 9496
  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

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

  • 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 45 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

5 to fixGoogle 9279
  • Title is short (12 characters)

    Your title is only 12 characters: “Shop By COMO”. 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 (“Shop By COMO”, “The Present Moment” and “Resortwear by COR”). One clear main headline is easier for people and search engines.

  • No social preview image

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

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

  • 158 internal links, 5 external

    The homepage links to 158 pages on shopbycomo.com and 5 external pages.

4 checks passed
  • Meta description: 95 characters

    Your meta description is 95 characters: “Bring the COMO lifestyle home — in fashion, homeware, hotel merchandise, and wellness products.”.

  • Canonical URL set

    The canonical URL is https://shopbycomo.com/en-us.

  • 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://shopbycomo.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://shopbycomo.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 (619 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://shopbycomo.com/en-us/collections/paola-navone-for-serax has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

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

Best practices

2 to fixGoogle 10087
  • 5 small tap targets

    5 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 318 words of copy

    The homepage carries about 318 words of visible text.

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “SHOP BY CATEGORY”, “SHOP BY BRAND” and “Contact Us”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies (measured from a US location before any click).

  • 27 other companies contacted

    Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 shopbycomo.com, 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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Se Wishlist Engine · Giftship · Wyllo Formerly Nofraud · Giftkart · creditsyard.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

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on shopbycomo.com, including 15 speed issues, 5 SEO issues and 3 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

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