Website review, no card needed

lotusblind.com logo

lotusblind.com website review

Visit site (opens in a new tab)Reviewed 11 November 202619 issues · 71 checks

This review found 19 issues worth fixing on lotusblind.com, 4 of them high impact, across 71 checks. The most urgent: 5 text elements with low contrast. 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.1 s769 msMay 23Nov 7918 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 2026963 ms
Jun 27, 2026884 ms
Jul 4, 2026894 ms
Jul 11, 2026863 ms
Jul 18, 2026853 ms
Jul 25, 2026863 ms
Aug 1, 2026931 ms
Aug 8, 2026969 ms
Aug 15, 20261.1 s
Aug 22, 2026958 ms
Aug 29, 2026881 ms
Sep 5, 2026856 ms
Sep 12, 2026865 ms
Sep 19, 2026813 ms
Sep 26, 2026870 ms
Oct 3, 2026852 ms
Oct 10, 2026884 ms
Oct 17, 2026967 ms
Oct 24, 2026965 ms
Oct 31, 2026973 ms
Nov 7, 2026918 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms65 msMay 23Nov 786 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202682 ms
May 30, 202677 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202676 ms
Jun 27, 202674 ms
Jul 4, 202671 ms
Jul 11, 202668 ms
Jul 18, 202672 ms
Jul 25, 202675 ms
Aug 1, 202679 ms
Aug 8, 202679 ms
Aug 22, 202685 ms
Aug 29, 202682 ms
Sep 5, 202681 ms
Sep 12, 202681 ms
Oct 3, 202678 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202683 ms
Oct 31, 202685 ms
Nov 7, 202686 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 lotusblind.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lotusblind.com at 0.4 s0.4 s
  2. lotusblind.com at 0.8 s0.8 s
  3. lotusblind.com at 1.2 s1.2 s
  4. lotusblind.com at 1.6 s1.6 s
  5. lotusblind.com at 1.9 s1.9 s
  6. lotusblind.com at 2.3 s2.3 s
  7. lotusblind.com at 2.7 s2.7 s
  8. lotusblind.com at 3.1 s3.1 s

Speed

4 to fix67
  • Reduce unused JavaScript

    960 ms · 146 KiB

    About 146 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 960 ms faster on a phone.

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Font display

    450 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).

  • Shopify adds 98 ms

    98 ms

    Shopify costs a phone 98 ms of main-thread work and 355 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

    250 ms

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

  • Reduce unused CSS

    150 ms · 46 KiB

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

  • Use efficient cache lifetimes

    150 ms · 22 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, Bugsnag and shop.app and others), adding 425 KiB and 98 ms of main-thread time.

  • Improve image delivery

    12 KiB

    1 image could be 12 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.

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 6.2 s

    6.2 s

    Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • First Contentful Paint: 3.2 s

    3.2 s

    The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

  • Speed Index: 5.6 s

    5.6 s

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

  • Time to Interactive: 6.2 s

    6.2 s

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

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 82 ms to 86 ms 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: 0.8 s

    0.8 s

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

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

    0.8 s

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

  • Real-user TTFB: 347 ms

    347 ms

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

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

    -10%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.44 g

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

4 checks passed
  • Page weight: 1.5 MB in 177 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 177 requests on a phone: other files 774 KiB (96), scripts 436 KiB (43) and fonts 129 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9797
  • 5 text elements with low contrast

    5 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 10 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9288
  • Meta description is long (239 characters)

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

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 90 internal links, 7 external

    The homepage links to 90 pages on lotusblind.com and 7 external pages.

6 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “www.lotusblind.com – Lotus & Windoware, Inc.”.

  • Canonical URL set

    The canonical URL is https://www.lotusblind.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.lotusblind.com/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 (640 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://www.lotusblind.com/collections/ftx-2-inch-smooth-snow-white-light-gray, https://www.lotusblind.com/collections/flx-2-inch-smooth-embossed-bright-white, https://www.lotusblind.com/collections/fcx-2-inch-smooth-soft-white, https://www.lotusblind.com/collections/ftx-2-inch-smooth-sott-white, https://www.lotusblind.com/collections/mlx-1-inch-smooth-white-alabaster and https://www.lotusblind.com/collections/rlx-1-inch-smooth-white-alabaster and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.lotusblind.com/collections 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 39 found) and read each the way a search engine does.

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

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 326 words of copy

    The homepage carries about 326 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop By Size”, “Contact” and “Shop All”.

  • 2 short forms

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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 lotusblind.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Advanced Wishlist · Hulk Form Builder · My Wishlist Share Remind · Al Bulk Discount Manager

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on lotusblind.com, including 8 speed issues, 3 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