Website review, no card needed
cheekyplum.com website review
Visit site (opens in a new tab)Reviewed 9 November 202629 issues · 78 checks
This review found 29 issues worth fixing on cheekyplum.com, 9 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
86B- #12,083 of 124,581 reviewed websitesbeats 87%
- #7,305 of 69,967 online storesbeats 85%
- #7,074 of 63,604 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 886 ms |
| May 30, 2026 | 871 ms |
| Jun 6, 2026 | 849 ms |
| Jun 13, 2026 | 817 ms |
| Jun 20, 2026 | 820 ms |
| Jun 27, 2026 | 825 ms |
| Jul 4, 2026 | 808 ms |
| Jul 11, 2026 | 800 ms |
| Jul 18, 2026 | 785 ms |
| Jul 25, 2026 | 773 ms |
| Aug 1, 2026 | 773 ms |
| Aug 8, 2026 | 785 ms |
| Aug 15, 2026 | 793 ms |
| Aug 22, 2026 | 808 ms |
| Aug 29, 2026 | 831 ms |
| Sep 5, 2026 | 833 ms |
| Sep 12, 2026 | 838 ms |
| Sep 19, 2026 | 846 ms |
| Sep 26, 2026 | 841 ms |
| Oct 3, 2026 | 839 ms |
| Oct 10, 2026 | 850 ms |
| Oct 17, 2026 | 850 ms |
| Oct 24, 2026 | 892 ms |
| Oct 31, 2026 | 913 ms |
| Nov 7, 2026 | 944 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 94 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 98 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 111 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 127 ms |
| Oct 31, 2026 | 128 ms |
| Nov 7, 2026 | 130 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
Speed
Reduce unused JavaScript
2.4 s · 512 KiBAbout 512 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Improve image delivery
1.5 s · 760 KiB14 images could be 760 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.1 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 (Shopify, Google CDN and Clarity and others), adding 1.6 MB and 849 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 305 KiB27 files are served with short cache lifetimes, so returning visitors download them again (305 KiB).
Render-blocking requests
450 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Shopify adds 310 ms
310 msShopify costs a phone 310 ms of main-thread work and 880 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.
2,664 HTML elements
The page has 2,664 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 169 ms
169 msGoogle CDN costs a phone 169 ms of main-thread work and 299 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.
Attentive adds 142 ms
142 msAttentive costs a phone 142 ms of main-thread work and 378 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
280 ms · 32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 152 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.5 s
14.5 sYour largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “New Arrivals - Satin Loungewear Set Sugar Cookie Santa”.
Time to Interactive: 16.5 s
16.5 sThe page becomes fully interactive after 16.5 s. Good is under 3.8 s.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 94 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 226 ms
226 msScripts block taps and scrolling for 226 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 108 ms
108 msReal visitors wait 108 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 520 ms
520 msReal visitors wait 520 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 4.8 MB in 450 requests
4.8 MBYour homepage downloads 4.8 MB in 450 requests on a phone: images 1.6 MB (29), scripts 1.4 MB (125) and other files 1.3 MB (268). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (77 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 162.7 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 checks passed
Every image has alt text
All 112 images in the HTML carry an alt attribute.
17 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
447 internal links, 6 external
The homepage links to 447 pages on cheekyplum.com and 6 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Welcome to Cheeky Plum girls boutique clothing where we specialize in little girls dresses and outfits for every occasi…”.
One H1 headline
Your main headline reads: “Cheeky Plum”.
Title: 55 characters
Your title is a healthy 55 characters: “Cheeky Plum | Girls Boutique Clothing, Dresses, Outfits”.
Canonical URL set
The canonical URL is https://cheekyplum.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://cheekyplum.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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 (1,221 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://cheekyplum.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages share 2 titles
https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-CLOTHING, https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-LOUNGEWEAR, https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-LEOTARDS, https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-TOPS, https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-BOTTOMS and https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-ACCESSORIES and 1 other all use the title “Christmas Dresses for Baby, Toddler & Girls – Cheeky Plum”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://cheekyplum.com/collections/featured and https://cheekyplum.com/collections/football have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages share a meta description
https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-CLOTHING, https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-LOUNGEWEAR, https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-LEOTARDS, https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-TOPS, https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-BOTTOMS and https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-ACCESSORIES and 1 other use the same meta description. A description written for each page earns more clicks.
11 links to non-canonical URLs
Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://cheekyplum.com/collections/girls-christmas-dresses/XMAS-CLOTHING, whose canonical is https://cheekyplum.com/collections/girls-christmas-dresses. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
21 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 639 words of copy
The homepage carries about 639 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: “New Arrivals SHOP NEW” and “SHOP NEW”.
27 calls to action
The homepage has 27 calls to action, for example “SHOP ALL”, “SHOP ALL SALE” and “New Arrivals Shop new”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 2 of them by other companies (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.
40 other companies contacted
Loading the homepage contacts 40 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 cheekyplum.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Microsoft Clarity · Attentive · Wrapped · Globo Product Options · Essential Post Purchase Upsell · Upcart · chimpstatic.com · attn.tv
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
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Houston
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on cheekyplum.com, including 18 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.