Website review, no card needed

cleoharper.com logo

cleoharper.com website review

Visit site (opens in a new tab)Reviewed 8 November 202622 issues · 74 checks

This review found 22 issues worth fixing on cleoharper.com, 7 of them high impact, across 74 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
955 ms602 msMay 16Oct 31731 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026798 ms
May 23, 2026794 ms
May 30, 2026831 ms
Jun 6, 2026866 ms
Jun 13, 2026912 ms
Jun 20, 2026783 ms
Jun 27, 2026745 ms
Jul 4, 2026759 ms
Jul 11, 2026734 ms
Jul 18, 2026849 ms
Jul 25, 2026914 ms
Aug 1, 2026754 ms
Aug 8, 2026729 ms
Aug 15, 2026711 ms
Aug 22, 2026696 ms
Aug 29, 2026728 ms
Sep 5, 2026729 ms
Sep 12, 2026742 ms
Sep 19, 2026757 ms
Sep 26, 2026728 ms
Oct 3, 2026713 ms
Oct 10, 2026643 ms
Oct 17, 2026700 ms
Oct 24, 2026720 ms
Oct 31, 2026731 ms
Real-visitor tap response (INP)75th percentile, phones
108 ms76 msMay 16Oct 3195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202687 ms
May 23, 202688 ms
May 30, 202687 ms
Jun 6, 202680 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202689 ms
Jul 4, 202694 ms
Jul 11, 202695 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 202694 ms
Aug 22, 202695 ms
Aug 29, 202692 ms
Sep 5, 202689 ms
Sep 12, 202691 ms
Sep 19, 202692 ms
Sep 26, 202696 ms
Oct 3, 202697 ms
Oct 10, 202696 ms
Oct 17, 202693 ms
Oct 24, 202695 ms
Oct 31, 202695 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 cleoharper.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix100
  • Render-blocking requests

    1.4 s

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

  • 3,049 HTML elements

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

  • Improve image delivery

    3.5 MB

    44 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    150 ms · 35 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, rapidlercdn.com and Klaviyo and others), adding 319 KiB and 48 ms of main-thread time.

  • 4 long tasks on the main thread

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

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 114 ms of it running JavaScript. That is comfortably low.

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

1 to fix100
  • 2 images without width and height

    2 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 87 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

11 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: 0.8 s

    0.8 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 492 ms

    492 ms

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

  • Time to Interactive: 3.1 s

    3.1 s

    The page is fully interactive after 3.1 s.

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Speed Index: 2.4 s

    2.4 s

    Visually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Total Blocking Time: 8 ms

    8 ms

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

Images and page weight

4 to fix52
  • Page weight: 4.6 MB in 137 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 137 requests on a phone: images 4.0 MB (53), scripts 472 KiB (48) and HTML 100 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    4_4e16fa25-55b5-43e6-982c-4722f5191752.png 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).

  • 25 images far larger than shown

    427 KiB

    25 images are downloaded at several times the size a phone draws them, for example 1_d38c35e4-88f5-45e7-875c-3538f8f6570c.jpg at 525 px wide, shown at 161 px. Resized copies would save about 427 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (308 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.32 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8693
  • 1 button without a name

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

  • 4 text elements with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 52 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: 52 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

2 to fixGoogle 9285
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (248 characters)

    Your meta description is 248 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 112 internal links, 5 external

    The homepage links to 112 pages on cleoharper.com and 5 external pages.

6 checks passed
  • Title: 56 characters

    Your title is a healthy 56 characters: “Cleo Harper | Activewear, Leggings, Sports Bras & Shorts”.

  • Canonical URL set

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

AI search readiness

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

  • llms.txt published

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://cleoharper.com/collections/all, https://cleoharper.com/collections/shop-all, https://cleoharper.com/pages/rewards, https://cleoharper.com/collections/bestsellers, https://cleoharper.com/collections/bralets and https://cleoharper.com/collections/leggings and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://cleoharper.com/pages/rewards has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://cleoharper.com/pages/rewards and https://cleoharper.com/collections/casual-shorts 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 62 found) and read each the way a search engine does.

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

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

Best practices

2 to fixGoogle 10087
  • 50 small tap targets

    50 of 117 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: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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.

  • About 1,061 words of copy

    The homepage carries about 1,061 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “SHOP ALL”, “SHOP” and “Shop now”.

  • 36 short forms

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

  • Social proof on the page

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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.

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

  • 31 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Wishlist Hero · Yotpo Product Reviews · Yotpo Loyalty Rewards · Pagefly Ai Page Builder · Chatra Live Chat Chatbot · Geoip Country Redirect · Givy · Loop Returns · Announcement Bar Maker By Apphero · cloudfront.net · nfcube.com · esc-apps-cdn.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

Framework
jQuery
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 22 issues on cleoharper.com, including 4 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