Website review, no card needed

ctzncosmetics.com logo

ctzncosmetics.com website review

Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 76 checks

This review found 33 issues worth fixing on ctzncosmetics.com, 7 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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 ctzncosmetics.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ctzncosmetics.com at 1.1 s1.1 s
  2. ctzncosmetics.com at 2.2 s2.2 s
  3. ctzncosmetics.com at 3.3 s3.3 s
  4. ctzncosmetics.com at 4.3 s4.3 s
  5. ctzncosmetics.com at 5.4 s5.4 s
  6. ctzncosmetics.com at 6.5 s6.5 s
  7. ctzncosmetics.com at 7.6 s7.6 s
  8. ctzncosmetics.com at 8.7 s8.7 s

Speed

9 to fix50
  • Reduce unused JavaScript

    1.2 s · 463 KiB

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

  • Main-thread work: 5.5 s

    A phone's processor spends 5.5 s on main-thread work while loading, 3.3 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 (Google Tag Manager, Yotpo and Clarity and others), adding 1.1 MB and 1.0 s of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • Google Tag Manager adds 413 ms

    413 ms

    Google Tag Manager costs a phone 413 ms of main-thread work and 320 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 · 65 KiB

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

  • Yotpo adds 295 ms

    295 ms

    Yotpo costs a phone 295 ms of main-thread work and 470 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.

  • Use efficient cache lifetimes

    330 KiB

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

  • 2,531 HTML elements

    The page has 2,531 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 193 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    150 ms · 26 KiB

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

  • Minify JavaScript

    150 ms · 21 KiB

    21 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    150 ms

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

  • Improve image delivery

    32 KiB

    2 images could be 32 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.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix54
  • Largest Contentful Paint: 9.2 s

    9.2 s

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

  • Time to Interactive: 13.4 s

    13.4 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Total Blocking Time: 370 ms

    370 ms

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

  • 1 image without width and height

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

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

1 checks passed
  • Cumulative Layout Shift: 0.098

    0.098

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

Images and page weight

1 to fix85
  • Page weight: 2.4 MB in 231 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 231 requests on a phone: scripts 1.1 MB (69), other files 831 KiB (136) and images 169 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.68 g

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

3 checks passed
  • 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

4 to fixGoogle 9095
  • 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 (15 elements)

    All page content should be contained by landmarks: 15 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.

  • 34 links without text

    34 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 7783
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Meet Your Match”). One clear main headline is easier for people and search engines.

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

  • 10 links crawlers can't follow

    10 links have no real href, so search engines can't follow them.

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

  • 128 internal links, 6 external

    The homepage links to 128 pages on ctzncosmetics.com and 6 external pages.

5 checks passed
  • Title: 65 characters

    Your title is a healthy 65 characters: “Find Your Perfect Nude with CTZN Cosmetics' Nudiversal Collection”.

  • Canonical URL set

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

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

3 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 (668 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 10 pages without a meta description

    https://www.ctzncosmetics.com/pages/nude-match-quiz, https://www.ctzncosmetics.com/pages/code-red-match, https://www.ctzncosmetics.com/blogs/all, https://www.ctzncosmetics.com/collections/best-sellers-1, https://www.ctzncosmetics.com/collections/eye-products and https://www.ctzncosmetics.com/collections/shop-sets-bundles and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.ctzncosmetics.com/collections/best-sellers-1, https://www.ctzncosmetics.com/products/nudiversal-lipstick and https://www.ctzncosmetics.com/collections/model-1 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.ctzncosmetics.com/pages/nude-match-quiz, https://www.ctzncosmetics.com/pages/code-red-match and https://www.ctzncosmetics.com/products/nudiversal-lipstick have 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 38 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 48 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 695 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: “Learn More” and “Shop All”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Start shopping”, “Shop” and “SHOP NOW”.

  • 4 short forms

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

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

  • 16 cookies set on arrival

    16

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

  • 29 other companies contacted

    Loading the homepage contacts 29 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 ctzncosmetics.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

Yotpo Product Reviews · Cartbot · Klaviyo Email Marketing Sms · Eu Cookie Bar · Selleasy · elfsight.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

Company

Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on ctzncosmetics.com, including 15 speed issues, 5 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