Website review, no card needed
chicdecent.com website review
Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 85 checks
This review found 36 issues worth fixing on chicdecent.com, 10 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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
80B- #43,133 of 108,857 reviewed websitesbeats 55%
- #28,689 of 61,765 online storesbeats 47%
- #27,617 of 56,365 Shopify storesbeats 44%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 137 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 144 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 139 ms |
| Jul 11, 2026 | 177 ms |
| Jul 18, 2026 | 220 ms |
| Jul 25, 2026 | 335 ms |
| Aug 1, 2026 | 376 ms |
| Aug 8, 2026 | 352 ms |
| Aug 15, 2026 | 316 ms |
| Aug 22, 2026 | 237 ms |
| Aug 29, 2026 | 230 ms |
| Sep 5, 2026 | 212 ms |
| Sep 12, 2026 | 217 ms |
| Sep 19, 2026 | 248 ms |
| Sep 26, 2026 | 243 ms |
| Oct 3, 2026 | 229 ms |
| Oct 10, 2026 | 232 ms |
| Oct 17, 2026 | 236 ms |
| Oct 24, 2026 | 252 ms |
| Oct 31, 2026 | 245 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
Render-blocking requests
1.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,596 HTML elements
The page has 3,596 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
500 ms · 286 KiB6 images could be 286 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and b-cdn.net and others), adding 1.5 MB and 419 ms of main-thread time.
Reduce unused JavaScript
150 ms · 370 KiBAbout 370 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.
Reduce unused CSS
300 ms · 51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 195 ms
195 msShopify costs a phone 195 ms of main-thread work and 767 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 266 ms. During a long task the page ignores taps.
Google Tag Manager adds 150 ms
150 msGoogle Tag Manager costs a phone 150 ms of main-thread work and 470 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.
Use efficient cache lifetimes
33 KiB8 files are served with short cache lifetimes, so returning visitors download them again (33 KiB).
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 13.8 s
13.8 sThe page becomes fully interactive after 13.8 s. Good is under 3.8 s.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 269 ms
269 msReal visitors wait 269 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 81% slower for real visitors
+81%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 137 ms to 245 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 418 ms
418 msReal visitors wait 418 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 190 ms
190 msScripts block the page for only 190 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.08
0.08The layout barely moves while loading (CLS 0.08, good is under 0.1).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.3 MB in 350 requests
3.3 MBYour homepage downloads 3.3 MB in 350 requests on a phone: scripts 1.4 MB (171), other files 838 KiB (130) and images 710 KiB (17). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Girlcult_-_Loulan_Bohemian_33.webp 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).
2 images in older formats
2 images (321 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 0.9 g of CO₂ per visit
0.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.94 g of CO₂e: 112.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h4 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 105 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//chicdecent.com/cdn/shop/files/chicdecentlogo_1.png?v=…”.
458 internal links, 6 external
The homepage links to 458 pages on chicdecent.com and 6 external pages.
7 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Chic Decent Beauty is a cbeauty store, on young and energtic cosmetic products. To present the known and arising Chines…”.
One H1 headline
Your main headline reads: “MAKEUP CHANGES!”.
Title: 32 characters
Your title is a healthy 32 characters: “Chic Decent, The Makeup Changes.”.
Canonical URL set
The canonical URL is https://chicdecent.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://chicdecent.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,992 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://chicdecent.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without a meta description
https://chicdecent.com/pages/discount-look, https://chicdecent.com/pages/chic-it, https://chicdecent.com/pages/brandslisting, https://chicdecent.com/collections/all, https://chicdecent.com/collections/newcolors and https://chicdecent.com/collections/colorrose and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://chicdecent.com/pages/discount-look, https://chicdecent.com/pages/chic-it, https://chicdecent.com/pages/brandslisting, https://chicdecent.com/collections/all, https://chicdecent.com/collections/newcolors and https://chicdecent.com/collections/colorrose and 9 others have 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 186 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
48 of 57 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 554 words of copy
The homepage carries about 554 words of visible text.
3 checks passed
21 calls to action
The homepage has 21 calls to action, for example “Contact us”, “Shop More” and “SHOP NOW”.
7 short forms
7 short forms (2 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
23 other companies contacted
Loading the homepage contacts 23 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 chicdecent.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
Consentmo Gdpr · Froonze Loyalty Wishlist · Judge Me Reviews · Instafeed · Inbox · Froonze App · Gdpr Backpack · Discount Kit · b-cdn.net
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
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on chicdecent.com, including 17 speed issues, 1 SEO issue and 5 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.