Website review, no card needed
camillekids.com website review
Visit site (opens in a new tab)Reviewed 19 November 202638 issues · 84 checks
This review found 38 issues worth fixing on camillekids.com, 18 of them high impact, across 84 checks. The most urgent: hcaptcha.com adds 1.4 s. 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
75C- #78,853 of 119,996 reviewed websitesbeats 30%
- #50,320 of 68,004 online storesbeats 22%
- #47,551 of 61,979 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 906 ms |
| Sep 5, 2026 | 675 ms |
| Sep 12, 2026 | 625 ms |
| Sep 19, 2026 | 615 ms |
| Sep 26, 2026 | 614 ms |
| Oct 3, 2026 | 648 ms |
| Oct 10, 2026 | 687 ms |
| Oct 17, 2026 | 673 ms |
| Oct 24, 2026 | 662 ms |
| Oct 31, 2026 | 624 ms |
| Nov 14, 2026 | 617 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 71 ms |
| Sep 19, 2026 | 71 ms |
| Sep 26, 2026 | 72 ms |
| Oct 3, 2026 | 78 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 79 ms |
| Oct 31, 2026 | 77 ms |
| Nov 14, 2026 | 72 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
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
hcaptcha.com adds 1.4 s
1.4 shcaptcha.com costs a phone 1.4 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 third-party services on the page
4 third-party services load with your homepage (hcaptcha.com, Shopify and nfcube.com and others), adding 2.4 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
750 ms · 443 KiBAbout 443 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
800 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 383 ms. During a long task the page ignores taps.
Shopify adds 193 ms
193 msShopify costs a phone 193 ms of main-thread work and 872 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
150 ms · 173 KiB6 images could be 173 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
225 KiB6 files are served with short cache lifetimes, so returning visitors download them again (225 KiB).
Reduce unused CSS
150 ms · 36 KiBAbout 36 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.
Legacy JavaScript
60 KiBPolyfills for old browsers add 60 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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 658 ms
658 msScripts block taps and scrolling for 658 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.159
0.159The layout shifts by 0.159 while loading, so content jumps under the reader's thumb. Good is under 0.1.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 79 ms to 72 ms 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: 0.6 s
0.6 sReal visitors wait 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 70 ms
70 msReal visitors wait 70 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: 0.5 s
0.5 sReal visitors see the first content after 0.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 359 ms
359 msReal visitors wait 359 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 41% faster for real visitors
-41%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.2 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 4.0 MB in 280 requests
4.0 MBYour homepage downloads 4.0 MB in 280 requests on a phone: scripts 1.8 MB (153), HTML 710 KiB (5) and other files 684 KiB (86). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 136.8 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
Certain ARIA roles must be contained by particular parents (3 elements)
Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
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.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (11 characters)
Your title is only 11 characters: “camillekids”. 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.
51 internal links, 1 external
The homepage links to 51 pages on camillekids.com and 1 external page.
5 checks passed
One H1 headline
Your main headline reads: “camillekids”.
Canonical URL set
The canonical URL is https://camillekids.com/.
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://camillekids.com/sitemap.xml.
AI search readiness
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.
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 (501 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://camillekids.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share a title
https://camillekids.com/products/ecolier-burgundy-leather, https://camillekids.com/products/ecolier-cacoa-leather, https://camillekids.com/products/ecolier-navy-plaid-leather, https://camillekids.com/products/ecolier-burgundy-patent and https://camillekids.com/products/ecolier-black-patent all use the title “Ecolier – camillekids”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://camillekids.com/collections, https://camillekids.com/collections/boys, https://camillekids.com/collections/sale and https://camillekids.com/collections/camille-collection have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://camillekids.com/collections/baby, https://camillekids.com/collections/teen, https://camillekids.com/collections/kids, https://camillekids.com/collections/boys, https://camillekids.com/collections/girls and https://camillekids.com/collections/sale and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://camillekids.com/collections and https://camillekids.com/pages/contact-us 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 23 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
3 broken images
3 images failed to load on a phone, for example https://camillekids.com/.
13 small tap targets
13 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were 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
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 256 words of copy
The homepage carries about 256 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 NOW”.
11 calls to action
The homepage has 11 calls to action, for example “Shop”, “Contact Us” and “SHOP NOW”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies, 1 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.
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 camillekids.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
Instafeed · Forms · nfcube.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
- 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 38 issues on camillekids.com, including 14 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.