Website review, no card needed

hardcandy.com logo

hardcandy.com website review

Visit site (opens in a new tab)Reviewed 10 November 202632 issues · 84 checks

This review found 32 issues worth fixing on hardcandy.com, 8 of them high impact, across 84 checks. The most urgent: certain ARIA roles must be contained by particular parents (13 elements). 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 s761 msMay 23Nov 7999 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 2026903 ms
Jun 13, 2026872 ms
Jun 20, 2026851 ms
Jun 27, 2026842 ms
Jul 4, 2026850 ms
Jul 11, 2026844 ms
Jul 18, 2026820 ms
Jul 25, 2026799 ms
Aug 1, 2026797 ms
Aug 8, 2026800 ms
Aug 15, 2026825 ms
Aug 22, 2026852 ms
Aug 29, 2026874 ms
Sep 5, 2026894 ms
Sep 12, 2026895 ms
Sep 19, 2026900 ms
Sep 26, 2026885 ms
Oct 3, 2026861 ms
Oct 10, 2026864 ms
Oct 17, 2026895 ms
Oct 24, 2026918 ms
Oct 31, 2026949 ms
Nov 7, 2026999 ms
Real-visitor tap response (INP)75th percentile, phones
136 ms82 msMay 23Nov 7130 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202688 ms
May 30, 202691 ms
Jun 6, 202691 ms
Jun 13, 202694 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202694 ms
Jul 11, 202693 ms
Jul 18, 202693 ms
Jul 25, 202694 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202696 ms
Aug 22, 202699 ms
Aug 29, 202696 ms
Sep 5, 202698 ms
Sep 12, 202696 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 202697 ms
Oct 10, 2026102 ms
Oct 17, 2026109 ms
Oct 24, 2026113 ms
Oct 31, 2026121 ms
Nov 7, 2026130 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 hardcandy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix70
  • Mobile performance score: 70

    70/100

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

  • Render-blocking requests

    750 ms

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

  • Improve image delivery

    100 ms · 393 KiB

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

  • Use efficient cache lifetimes

    300 ms · 65 KiB

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

  • 1,627 HTML elements

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Klaviyo, Yotpo and Shopify and others), adding 422 KiB and 178 ms of main-thread time.

  • Duplicated JavaScript

    50 ms · 3 KiB

    3 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    50 ms

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

  • Reduce unused CSS

    41 KiB

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

  • Legacy JavaScript

    19 KiB

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 436 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

5 to fix100
  • Largest Contentful Paint: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hard Candy Glass On Lock Setting Spray on model”.

  • Time to Interactive: 10.5 s

    10.5 s

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

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

    +40%

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Speed Index: 4.1 s

    4.1 s

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

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.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.3 s

    1.3 s

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

  • Real-user INP: 121 ms

    121 ms

    Real visitors wait 121 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.2 s

    1.2 s

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

  • Real-user TTFB: 525 ms

    525 ms

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

  • 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

2 to fix75
  • Page weight: 2.5 MB in 220 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 220 requests on a phone: images 1.2 MB (39), other files 733 KiB (81) and scripts 464 KiB (70). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    99 KiB

    1 image is downloaded at several times the size a phone draws it, for example hero-glaze-model.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 99 KiB.

  • About 0.7 g of CO₂ per visit

    0.72 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.72 g of CO₂e: 86.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 load when needed

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

Accessibility

9 to fixGoogle 8288
  • Certain ARIA roles must be contained by particular parents (13 elements)

    Certain ARIA roles must be contained by particular parents: 13 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 3 text elements with low contrast

    3 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 (15 elements)

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

  • ARIA role should be appropriate for the element (10 elements)

    ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.

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

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 9289
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Hard Candy Cosmetics: Affordable Makeup and Skincare - Cruelty Free”.

  • 5 links crawlers can't follow

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 143 internal links, 9 external

    The homepage links to 143 pages on hardcandy.com and 9 external pages.

7 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Elevate your look with Hard Candy. Explore affordable, cruelty-free makeup that delivers professional results. Shop the…”.

  • One H1 headline

    Your main headline reads: “Best-in-glass skin”.

  • Canonical URL set

    The canonical URL is https://hardcandy.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://hardcandy.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.

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

  • llms.txt published

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

Other pages

1 to fix95
  • 10 pages without a meta description

    https://hardcandy.com/collections/new-1, https://hardcandy.com/collections/eye, https://hardcandy.com/collections/eyeshadow, https://hardcandy.com/collections/mascara, https://hardcandy.com/collections/eyeliner and https://hardcandy.com/collections/lip and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

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

Best practices

2 to fixGoogle 9687
  • 20 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • 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 264 words of copy

    The homepage carries about 264 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 GLASS ON LOCK →”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop Glass On Lock →”, “Shop all setting sprays” and “Shop”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 17 cookies set on arrival

    17

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

  • 24 other companies contacted

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

Apps your storefront loads

Yotpo Product Reviews · Klaviyo Email Marketing Sms · Accessibly App

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

Company

Founded
1995

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on hardcandy.com, including 10 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