Website review, no card needed
rareism.com website review
Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 76 checks
This review found 28 issues worth fixing on rareism.com, 5 of them high impact, across 76 checks. The most urgent: 1 tap target too small. 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
87B- #6,768 of 95,115 reviewed websitesbeats 90%
- #3,760 of 51,211 online storesbeats 89%
- #3,646 of 46,327 Shopify storesbeats 88%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 171 ms |
| May 23, 2026 | 172 ms |
| May 30, 2026 | 197 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 209 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 190 ms |
| Jul 18, 2026 | 175 ms |
| Jul 25, 2026 | 160 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 216 ms |
| Aug 22, 2026 | 257 ms |
| Aug 29, 2026 | 275 ms |
| Sep 5, 2026 | 292 ms |
| Sep 12, 2026 | 287 ms |
| Sep 19, 2026 | 247 ms |
| Sep 26, 2026 | 233 ms |
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 192 ms |
| Oct 17, 2026 | 184 ms |
| Oct 24, 2026 | 174 ms |
| Oct 31, 2026 | 185 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
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Use efficient cache lifetimes
300 ms · 21 KiB2 files are served with short cache lifetimes, so returning visitors download them again (21 KiB).
Google Tag Manager adds 0 ms
0 msGoogle Tag Manager costs a phone 0 ms of main-thread work and 345 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 · 32 KiBAbout 32 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.
6 third-party services on the page
6 third-party services load with your homepage (pickrr.com, Google Fonts and Shopify and others), adding 428 KiB and 1 ms of main-thread time.
Improve image delivery
21 KiB1 image could be 21 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 77 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.0 s
9.0 sThe page becomes fully interactive after 9.0 s. Good is under 3.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 171 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 127 ms
127 msReal visitors wait 127 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.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 306 ms
306 msReal visitors wait 306 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
12 images in older formats
12 images (732 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.
13 images below the first screen load straight away
13 images further down the page (693 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 60.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.8 MB in 46 requests
1.8 MBYour homepage downloads 1.8 MB in 46 requests on a phone: images 959 KiB (22), scripts 748 KiB (18) and stylesheets 46 KiB (4). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
28 images without alt text
28 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (71 elements)
All page content should be contained by landmarks: 71 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (OnlineStore and Product) but with 1 problem, for example “Product: missing name”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
190 internal links, 27 external
The homepage links to 190 pages on rareism.com and 27 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Rareism brings to you elegant and fashionable womens clothing online. Choose from a range of dresses, tops, jumpsuits t…”.
One H1 headline
Your main headline reads: “Rareism - Luxury Clothing Brand for Women”.
Title: 58 characters
Your title is a healthy 58 characters: “Rareism - Women's Most Loved Fashion Clothing Store Online”.
Canonical URL set
The canonical URL is https://rareism.com/.
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://rareism.com/sitemap.xml.
AI search readiness
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 description; sameAs (social profiles) and contact details would complete it.
llms.txt published
The site publishes https://rareism.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://rareism.com/collections/rareism-aw-26, https://rareism.com/collections/rareism-guild-casual, https://rareism.com/collections/rareism-walk-7-0, https://rareism.com/collections/rarez-women, https://rareism.com/collections/rareism-bobo and https://rareism.com/collections/outlet and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://rareism.com/pages/help, https://rareism.com/pages/rareism-shibani, https://rareism.com/pages/rareism-blush-bark and https://rareism.com/pages/rareism-mahjong 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 69 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
21 small tap targets
21 of 73 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were 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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 138 words
The homepage has only about 138 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “START SHOPPING” and “TRACK ORDER”.
4 calls to action
The homepage has 4 calls to action, for example “START SHOPPING”, “APPLY Loading...” and “TRACK ORDER”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
53 other companies contacted
Loading the homepage contacts 53 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 rareism.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Clevertap · Customerlabs 1pd Capi Tracking · Wizrocketplugin · xpresslane.in · amazonaws.com · webmarked.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
- The footer still says © 2025.
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 4 open roles
- Job board
- careers page
Company
- Headquarters
- Bengaluru
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on rareism.com, including 9 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.