Website review, no card needed

kandikoated.com logo

kandikoated.com website review

Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 79 checks

This review found 37 issues worth fixing on kandikoated.com, 15 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
3.5 s3.4 sMay 30Aug 293.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s

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 kandikoated.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kandikoated.com at 0.4 s0.4 s
  2. kandikoated.com at 0.8 s0.8 s
  3. kandikoated.com at 1.1 s1.1 s
  4. kandikoated.com at 1.5 s1.5 s
  5. kandikoated.com at 1.9 s1.9 s
  6. kandikoated.com at 2.3 s2.3 s
  7. kandikoated.com at 2.6 s2.6 s
  8. kandikoated.com at 3.0 s3.0 s

Speed

11 to fix14
  • Use efficient cache lifetimes

    4.5 s · 754 KiB

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

  • Reduce unused JavaScript

    4.1 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

  • Render-blocking requests

    4.7 s

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.

  • Mobile performance score: 14

    14/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Accessibe Accessibility Overlay, Google Tag Manager and Facebook and others), adding 917 KiB and 1.1 s of main-thread time.

  • Improve image delivery

    950 ms · 177 KiB

    6 images could be 177 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

  • Reduce unused CSS

    600 ms · 117 KiB

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

  • Accessibe Accessibility Overlay adds 476 ms

    476 ms

    Accessibe Accessibility Overlay costs a phone 476 ms of main-thread work and 250 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.

  • Google Tag Manager adds 416 ms

    416 ms

    Google Tag Manager costs a phone 416 ms of main-thread work and 363 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.

  • 14 long tasks on the main thread

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

  • Main-thread work: 2.6 s

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    13 KiB

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

  • Minify JavaScript

    12 KiB

    12 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: 1 ms

    1 ms

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

Core Web Vitals

7 to fix11
  • Largest Contentful Paint: 15.8 s

    15.8 s

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

  • Cumulative Layout Shift: 0.733

    0.733

    The layout shifts by 0.733 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 15.8 s

    15.8 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • Total Blocking Time: 987 ms

    987 ms

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

  • 8 images without width and height

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

  • 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 3.5 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 75 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 75 requests on a phone: images 1.7 MB (36), scripts 1.3 MB (17) and stylesheets 136 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.98 g

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

8 to fixGoogle 7087
  • Images must have alternative text (2 elements)

    Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • 2 text elements with low contrast

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 6 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 8 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 9289
  • Title is short (22 characters)

    Your title is only 22 characters: “Kandi Koated Cosmetics”. 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.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 76 internal links, 5 external

    The homepage links to 76 pages on kandikoated.com and 5 external pages.

5 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “Shop luxurious cruelty-free cosmetics by Kandi Burruss! Host a Kandi Koated home party or shop online for fantastic mak…”.

  • One H1 headline

    Your main headline reads: “ARE YOU WORKING WITH A Kandi Koated CONSULTANT OR Kandi Koated AFFILIATE?”.

  • Canonical URL set

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

  • 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.kandikoated.com/sitemap_www.kandikoated.com_Index.xml.

AI search readiness

1 to fix83
  • 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://www.kandikoated.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.

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

Other pages

2 to fix90
  • 16 pages share a title

    /, https://www.kandikoated.com/privacy, https://www.kandikoated.com/shop, https://www.kandikoated.com/shop/All-Items, https://www.kandikoated.com/shop/Giftsets and https://www.kandikoated.com/shop/lips and 10 others all use the title “Kandi Koated Cosmetics”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.kandikoated.com/privacy, https://www.kandikoated.com/shop, https://www.kandikoated.com/shop/All-Items, https://www.kandikoated.com/shop/Giftsets, https://www.kandikoated.com/shop/lips and https://www.kandikoated.com/shop/eyes and 9 others use the same meta description. A description written for each page earns more clicks.

  • 2 pages slow to respond

    https://www.kandikoated.com/shop/All-Items and https://www.kandikoated.com/shop/bath-and-body took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

Google 96100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Only about 128 words

    The homepage has only about 128 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN” and “JOIN AS A CONSULTANT”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop”, “Join” and “Buy Now”.

  • 2 short forms

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 kandikoated.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on kandikoated.com, including 18 speed issues, 2 SEO issues and 4 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