Website review, no card needed

soleiz.com logo

soleiz.com website review

Visit site (opens in a new tab)Reviewed 10 November 202629 issues · 74 checks

This review found 29 issues worth fixing on soleiz.com, 8 of them high impact, across 74 checks. The most urgent: page weight: 5.6 MB in 529 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

Full-page screenshot of soleiz.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. soleiz.com at 1.1 s1.1 s
  2. soleiz.com at 2.1 s2.1 s
  3. soleiz.com at 3.2 s3.2 s
  4. soleiz.com at 4.2 s4.2 s
  5. soleiz.com at 5.3 s5.3 s
  6. soleiz.com at 6.3 s6.3 s
  7. soleiz.com at 7.4 s7.4 s
  8. soleiz.com at 8.4 s8.4 s

Speed

9 to fix77
  • Main-thread work: 5.1 s

    A phone's processor spends 5.1 s on main-thread work while loading, 1.9 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 JSDelivr CDN and others), adding 2.0 MB and 978 ms of main-thread time.

  • Mobile performance score: 77

    77/100

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

  • Shopify adds 640 ms

    640 ms

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

    750 ms

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

  • Reduce unused JavaScript

    130 ms · 375 KiB

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

  • Improve image delivery

    470 KiB

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

  • Klaviyo adds 169 ms

    169 ms

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

  • 1,660 HTML elements

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    63 KiB

    Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need.

  • Use efficient cache lifetimes

    42 KiB

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

  • Reduce unused CSS

    34 KiB

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

  • 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: 9 ms

    9 ms

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

Core Web Vitals

3 to fix76
  • Time to Interactive: 19.9 s

    19.9 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 5.5 s

    5.5 s

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

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

3 checks passed
  • Total Blocking Time: 191 ms

    191 ms

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

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix36
  • Page weight: 5.6 MB in 529 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 529 requests on a phone: images 2.4 MB (19), scripts 1.6 MB (281) and other files 1,019 KiB (162). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    737dd226-3a2c-4275-a6c9-4f9a1ca4f95c.png weighs 1.7 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (1.7 MB) 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.

  • An image on the first screen is lazy-loaded

    Untitled_Design_14_0f01b097-2685-40c2-872d-75868bfd7b6f.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.6 g of CO₂ per visit

    1.58 g

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

4 to fixGoogle 8794
  • 26 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail 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.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • One H1 headline

    Your <h1> is empty.

  • 33 internal links, 7 external

    The homepage links to 33 pages on soleiz.com and 7 external pages.

7 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Small moments that are just for you. Self-warming eye masks and Love, Me., a six-month guided journal. From Soleiz, New…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Soleiz | Self-Warming Eye Masks & Love, Me. Journal”.

  • Canonical URL set

    The canonical URL is https://soleiz.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://soleiz.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 (1,033 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix81
  • 4 pages share 2 titles

    https://soleiz.com/collections/self-warming-eyemasks-without-bundles and https://soleiz.com/collections/5-packs all use the title “Self-Warming Eyemasks – Soleiz”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://soleiz.com/pages/wholesale, https://soleiz.com/policies/terms-of-service, https://soleiz.com/policies/privacy-policy, https://soleiz.com/policies/refund-policy and https://soleiz.com/policies/contact-information have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://soleiz.com/collections/self-warming-eyemasks-without-bundles and https://soleiz.com/collections/5-packs use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://soleiz.com/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://soleiz.com/policies/contact-information has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 3 pages slow to respond

    https://soleiz.com/pages/about-us, https://soleiz.com/collections/5-packs and https://soleiz.com/collections/love-me took over 3 s to send their HTML from our server.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • 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
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://cdn.judge.me/reviews/reviews_for_carousel?reviews_selection=all&carousel_type=cards&star_ra…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 1,650 words of copy

    The homepage carries about 1,650 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: “Shop Eye Masks”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop All”, “Shop Eye Masks” and “Shop Love, Me.”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks and a star rating.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 14 cookies set on arrival

    14

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

  • 32 other companies contacted

    Loading the homepage contacts 32 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 soleiz.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 · Judge Me Reviews · Bundler Bundles App · Section Factory · Koala Upsell Gift · nfcube.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on soleiz.com, including 12 speed issues, 1 SEO issue 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

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