Website review, no card needed
forever52.in website review
Visit site (opens in a new tab)Reviewed 24 October 202653 issues · 94 checks
This review found 53 issues worth fixing on forever52.in, 18 of them high impact, across 94 checks. The most urgent: improve image delivery. 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
63D- #114,910 of 120,953 reviewed websitesbeats 4%
- #66,946 of 68,456 online storesbeats 2%
- #61,275 of 62,380 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 256 ms |
| May 9, 2026 | 260 ms |
| May 16, 2026 | 267 ms |
| May 23, 2026 | 304 ms |
| May 30, 2026 | 352 ms |
| Jun 6, 2026 | 383 ms |
| Jun 13, 2026 | 401 ms |
| Jun 20, 2026 | 419 ms |
| Jun 27, 2026 | 420 ms |
| Jul 4, 2026 | 424 ms |
| Jul 11, 2026 | 425 ms |
| Jul 18, 2026 | 429 ms |
| Jul 25, 2026 | 432 ms |
| Aug 1, 2026 | 428 ms |
| Aug 8, 2026 | 436 ms |
| Aug 15, 2026 | 428 ms |
| Aug 22, 2026 | 423 ms |
| Aug 29, 2026 | 419 ms |
| Sep 5, 2026 | 405 ms |
| Sep 12, 2026 | 409 ms |
| Sep 19, 2026 | 418 ms |
| Sep 26, 2026 | 435 ms |
| Oct 3, 2026 | 434 ms |
| Oct 10, 2026 | 436 ms |
| Oct 17, 2026 | 438 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
1.0 s
2.0 s
3.0 s
4.0 s
5.0 s
5.9 s
6.9 s
7.9 s
Speed
Improve image delivery
6.7 s · 1.0 MB28 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.7 s faster on a phone.
Main-thread work: 7.8 s
A phone's processor spends 7.8 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,172 HTML elements
The page has 3,172 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
2.4 MBAbout 2.4 MB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, shopflo.co and Shopify and others), adding 3.7 MB and 1.4 s of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50 (desktop: 57). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Google Tag Manager adds 470 ms
470 msGoogle Tag Manager costs a phone 470 ms of main-thread work and 659 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.
shopflo.co adds 311 ms
311 msshopflo.co costs a phone 311 ms of main-thread work and 1.9 MB 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
293 KiB18 files are served with short cache lifetimes, so returning visitors download them again (293 KiB).
Shopify adds 216 ms
216 msShopify costs a phone 216 ms of main-thread work and 661 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 234 KiBAbout 234 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 28 ms
28 msYour server sent the HTML in 28 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.
Largest Contentful Paint: 12.0 s
12.0 sYour largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 38.9 s
38.9 sThe page becomes fully interactive after 38.9 s. Good is under 3.8 s.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 281 ms
281 msReal visitors wait 281 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.22
0.22For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.
Tap response (INP) got 69% slower for real visitors
+69%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 256 ms to 438 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 889 ms
889 msReal visitors wait 889 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 373 ms
373 msScripts block taps and scrolling for 373 ms in total while the page loads. Good is under 200 ms.
1 checks passed
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 405 requests
7.6 MBYour homepage downloads 7.6 MB in 405 requests on a phone: scripts 3.8 MB (136), images 2.3 MB (63) and other files 939 KiB (141). Under 2 MB keeps phones on slow connections fast.
11 images far larger than shown
640 KiB11 images are downloaded at several times the size a phone draws them, for example FDC001-2_9c55fa30-6423-43d7-b8c8-7a30a113913f.png at 1,000 px wide, shown at 166 px. Resized copies would save about 640 KiB.
An image on the first screen is lazy-loaded
Artist_Kajal_Banner_-_MOBILE_fadfefd1-c4ab-459f-825a-bbacc85 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).
About 2.2 g of CO₂ per visit
2.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.16 g of CO₂e: 259.4 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
Hidden but focusable
10 elements hidden from screen readers can still receive keyboard focus.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Summary elements must have discernible text (2 elements)
Summary elements must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
37 links without text
37 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
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
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 66 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Buy Cosmetic & Beauty Products Online in India – Daily Life Forever52”.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
193 internal links, 17 external
The homepage links to 193 pages on forever52.in and 17 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Buy Cosmetic Products, Skincare & Beauty Products online from Forever52. The most renowned cosmetic brands with a high …”.
Canonical URL set
The canonical URL is https://www.forever52.in/.
Structured data in place
Structured data found: Organization, SocialMediaPosting 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://www.forever52.in/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: 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,178 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.forever52.in/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.forever52.in/collections/all-collection and https://www.forever52.in/collections/best-seller have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.forever52.in/collections/all-collection, https://www.forever52.in/collections/new-arrival, https://www.forever52.in/collections/best-seller, https://www.forever52.in/collections/face, https://www.forever52.in/collections/foundation and https://www.forever52.in/collections/compact-powder 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 86 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
1 broken image
1 image failed to load on a phone, for example https://www.forever52.in/.
23 small tap targets
23 of 105 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
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 765 words of copy
The homepage carries about 765 words of visible text.
4 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Lips Matte, gloss and everyday Shop Now”, “Eyes Kajal, liner, mascara & Shop Now” and “Contact us”.
1 short form
A short form (3 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 24 testimonial or review blocks, a star rating, 2 trust badges and “Trusted by 1.8M+ users”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Hotjar.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
51 other companies contacted
Loading the homepage contacts 51 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 forever52.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Vue.js
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on forever52.in, including 25 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.