Website review, no card needed

crackedpolish.com logo

crackedpolish.com website review

Visit site (opens in a new tab)Reviewed 4 November 202632 issues · 86 checks

This review found 32 issues worth fixing on crackedpolish.com, 13 of them high impact, across 86 checks. The most urgent: render-blocking 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

Real-visitor load time (LCP)75th percentile, phones
927 ms805 msMay 16Oct 31823 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026874 ms
May 23, 2026832 ms
May 30, 2026823 ms
Jun 6, 2026819 ms
Jun 13, 2026823 ms
Jun 20, 2026860 ms
Jun 27, 2026887 ms
Jul 4, 2026902 ms
Jul 11, 2026893 ms
Jul 18, 2026882 ms
Jul 25, 2026860 ms
Aug 1, 2026858 ms
Aug 8, 2026861 ms
Aug 15, 2026870 ms
Aug 22, 2026905 ms
Aug 29, 2026910 ms
Sep 5, 2026913 ms
Sep 12, 2026912 ms
Sep 19, 2026899 ms
Sep 26, 2026870 ms
Oct 3, 2026856 ms
Oct 10, 2026843 ms
Oct 17, 2026841 ms
Oct 24, 2026836 ms
Oct 31, 2026823 ms
Real-visitor tap response (INP)75th percentile, phones
105 ms86 msMay 16Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202688 ms
May 23, 202688 ms
May 30, 202688 ms
Jun 6, 202689 ms
Jun 13, 202690 ms
Jun 20, 202695 ms
Jun 27, 202696 ms
Jul 4, 202697 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202697 ms
Aug 1, 202697 ms
Aug 8, 202698 ms
Aug 15, 202699 ms
Aug 22, 2026101 ms
Aug 29, 2026102 ms
Sep 5, 2026103 ms
Sep 12, 2026102 ms
Sep 19, 2026103 ms
Sep 26, 202696 ms
Oct 3, 202696 ms
Oct 10, 202695 ms
Oct 17, 202695 ms
Oct 24, 202696 ms
Oct 31, 202696 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 crackedpolish.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crackedpolish.com at 1.0 s1.0 s
  2. crackedpolish.com at 1.9 s1.9 s
  3. crackedpolish.com at 2.9 s2.9 s
  4. crackedpolish.com at 3.8 s3.8 s
  5. crackedpolish.com at 4.8 s4.8 s
  6. crackedpolish.com at 5.8 s5.8 s
  7. crackedpolish.com at 6.7 s6.7 s
  8. crackedpolish.com at 7.7 s7.7 s

Speed

9 to fix71
  • Render-blocking requests

    1.3 s

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

  • Main-thread work: 4.4 s

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

  • 3,188 HTML elements

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

  • Mobile performance score: 71

    71/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and Klarna and others), adding 1.7 MB and 635 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 459 KiB

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

  • Shopify adds 371 ms

    371 ms

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

  • Improve image delivery

    419 KiB

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

  • Klaviyo adds 161 ms

    161 ms

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

    150 ms · 22 KiB

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

  • 9 long tasks on the main thread

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

  • Use efficient cache lifetimes

    64 KiB

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

  • Minify JavaScript

    27 KiB

    27 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    25 KiB

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

  • Duplicated JavaScript

    20 KiB

    20 KiB JavaScript is shipped twice across bundles.

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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 17.7 s

    17.7 s

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

  • Speed Index: 10.1 s

    10.1 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

    1.1 s

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

  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 634 ms

    634 ms

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

  • Total Blocking Time: 107 ms

    107 ms

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

  • Cumulative Layout Shift: 0.043

    0.043

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

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 509 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 509 requests on a phone: images 1.7 MB (75), scripts 1.6 MB (163) and other files 1.5 MB (205). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.44 g

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

6 to fixGoogle 9291
  • 76 text elements with low contrast

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

  • 6 tap targets too small

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

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

  • 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 (4 elements)

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

  • 2 links without text

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

  • Headings skip levels

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

1 checks passed
  • 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 9293
  • 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.

  • One H1 headline

    Your <h1> is empty.

  • 172 internal links, 17 external

    The homepage links to 172 pages on crackedpolish.com and 17 external pages.

7 checks passed
  • Meta description: 105 characters

    Your meta description is 105 characters: “Cracked Polish. Wear it out. No fomo, wearable, indie nail polish that's 10-free, vegan and cruelty free.”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Cracked Polish | No Fomo Indie Nail Polish”.

  • Canonical URL set

    The canonical URL is https://crackedpolish.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://crackedpolish.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://crackedpolish.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.

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.

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

Other pages

4 to fix68
  • 1 page without a title

    https://crackedpolish.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://crackedpolish.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://crackedpolish.com/collections/all, https://crackedpolish.com/customer_authentication/redirect, https://crackedpolish.com/policies/shipping-policy and https://crackedpolish.com/collections/cream have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://crackedpolish.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97073274&Ver=2&mid=81ace085-e6e0-412b-9c3c-e3585f05e59d&bo=1&sid=b40d5300d82711f182d28b370e6e60e5&vid=b40d6e70d82711f1b54b97fb9ea9af2f&vids=1&msclkid=N&pi=918639831&lg.

  • 30 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

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

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

    The homepage carries about 584 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: “And Friends ★ ORDER UP ★” and “Treatments & Nail Care ★ START FRESH ★”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Register” and “And Friends ★ ORDER UP ★”.

  • 39 short forms

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

  • Social proof on the page

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

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 22 cookies set on arrival

    22

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

  • 35 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Bootstrap
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 32 issues on crackedpolish.com, including 14 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