Website review, no card needed

mellownoir.com logo

mellownoir.com website review

Visit site (opens in a new tab)Reviewed 4 November 202636 issues · 85 checks

This review found 36 issues worth fixing on mellownoir.com, 12 of them high impact, across 85 checks. The most urgent: main-thread work: 11.1 s. 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.9 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
208 ms173 msMay 16Oct 31203 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026177 ms
May 23, 2026179 ms
May 30, 2026182 ms
Jun 6, 2026185 ms
Jun 13, 2026185 ms
Jun 20, 2026186 ms
Jun 27, 2026187 ms
Jul 4, 2026187 ms
Jul 11, 2026191 ms
Jul 18, 2026194 ms
Jul 25, 2026192 ms
Aug 1, 2026194 ms
Aug 8, 2026194 ms
Aug 15, 2026194 ms
Aug 22, 2026194 ms
Aug 29, 2026192 ms
Sep 5, 2026189 ms
Sep 12, 2026187 ms
Sep 19, 2026188 ms
Sep 26, 2026193 ms
Oct 3, 2026197 ms
Oct 10, 2026202 ms
Oct 17, 2026203 ms
Oct 24, 2026204 ms
Oct 31, 2026203 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 mellownoir.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mellownoir.com at 0.7 s0.7 s
  2. mellownoir.com at 1.3 s1.3 s
  3. mellownoir.com at 2.0 s2.0 s
  4. mellownoir.com at 2.7 s2.7 s
  5. mellownoir.com at 3.4 s3.4 s
  6. mellownoir.com at 4.0 s4.0 s
  7. mellownoir.com at 4.7 s4.7 s
  8. mellownoir.com at 5.4 s5.4 s

Speed

11 to fix45
  • Main-thread work: 11.1 s

    A phone's processor spends 11.1 s on main-thread work while loading, 5.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6,820 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, wgs-static.com and Klaviyo and others), adding 1.0 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 493 KiB

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

  • Use efficient cache lifetimes

    250 ms · 526 KiB

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

  • Shopify adds 486 ms

    486 ms

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

  • wgs-static.com adds 404 ms

    404 ms

    wgs-static.com costs a phone 404 ms of main-thread work and 39 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.

  • Reduce unused CSS

    300 ms · 51 KiB

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

  • 20 long tasks on the main thread

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

  • Klaviyo adds 252 ms

    252 ms

    Klaviyo costs a phone 252 ms of main-thread work and 369 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

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

  • Improve image delivery

    91 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    28 KiB

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

  • Minify JavaScript

    13 KiB

    13 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: 26 ms

    26 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 20.9 s

    20.9 s

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

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 6.1 s

    6.1 s

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

  • Speed Index: 5.7 s

    5.7 s

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

  • 1 image without width and height

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.0 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: 139 ms

    139 ms

    Real visitors wait 139 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: 1.1 s

    1.1 s

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

  • Real-user TTFB: 493 ms

    493 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

2 to fix81
  • Page weight: 3.6 MB in 319 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 319 requests on a phone: scripts 1.7 MB (125), other files 898 KiB (149) and images 468 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    2026-11-02_black-deals-anti-aging-starterset_hero_1000x1250_ 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.0 g of CO₂ per visit

    1.02 g

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

4 to fixGoogle 9494
  • Elements must only use permitted ARIA attributes (6 elements)

    Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (6 elements)

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

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9295
  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 52 internal links, 4 external

    The homepage links to 52 pages on mellownoir.com and 4 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Zertifizierte Naturkosmetik mit der Schönheitsinnovation - aktivem Kaffeeöl aus 100% verbrauchtem Kaffee. Vegan und hoc…”.

  • One H1 headline

    Your main headline reads: “mellow NOIR”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “mellow NOIR - clean & effektiv.”.

  • Canonical URL set

    The canonical URL is https://mellownoir.com/de-de.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://mellownoir.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, 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://mellownoir.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 (924 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix55
  • 1 page without a title

    https://mellownoir.com/dermatest-cb has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://mellownoir.com/products/black-deal-anti-aging-starterset is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://mellownoir.com/de-de/collections/black-deals and https://mellownoir.com/collections/black-deals all use the title “Black Deals”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://mellownoir.com/de-de/collections/black-deals, https://mellownoir.com/de-de/apps/memberr/build-a-box/95e63461-ece1-4c5e-9433-8d2e77d35b3e, https://mellownoir.com/de-de/pages/konzept, https://mellownoir.com/collections/black-deals, https://mellownoir.com/products/black-deal-anti-aging-starterset and https://mellownoir.com/dermatest-cb have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mellownoir.com/collections/black-deals, whose canonical is https://mellownoir.com/de-de/collections/black-deals. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://mellownoir.com/de-de/collections/black-deals, https://mellownoir.com/de-de/collections/produkte, https://mellownoir.com/de-de/apps/memberr/build-a-box/95e63461-ece1-4c5e-9433-8d2e77d35b3e, https://mellownoir.com/de-de/pages/konzept, https://mellownoir.com/collections/black-deals and https://mellownoir.com/dermatest-cb have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://mellownoir.com/de-de/apps/memberr/build-a-box/95e63461-ece1-4c5e-9433-8d2e77d35b3e 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.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Shopify is not defined”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 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 852 words of copy

    The homepage carries about 852 words of visible text.

  • Urgency cues

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

4 checks passed
  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 12 testimonial or review blocks and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 36 cookies set on arrival

    36

    Opening the homepage sets 36 cookies, 1 of them by other companies (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.

  • 54 other companies contacted

    Loading the homepage contacts 54 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 mellownoir.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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Mable · Mellow Noir Custom Integration · Gempages Builder · Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Kaching Bundles · Gdpr Cookie Consent · Rivo Loyalty Rewards Referrals · selecdoo.com · archive-digger.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 Analytics | Google Tag Manager | 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 36 issues on mellownoir.com, including 16 speed issues, 2 SEO issues 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