Website review, no card needed
discoverpilgrim.com website review
Visit site (opens in a new tab)Reviewed 19 November 202634 issues · 70 checks
This review found 34 issues worth fixing on discoverpilgrim.com, 11 of them high impact, across 70 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Pilgrim
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 324 ms |
| Jun 6, 2026 | 330 ms |
| Jun 13, 2026 | 336 ms |
| Jun 20, 2026 | 339 ms |
| Jun 27, 2026 | 346 ms |
| Jul 4, 2026 | 347 ms |
| Jul 11, 2026 | 347 ms |
| Jul 18, 2026 | 346 ms |
| Jul 25, 2026 | 347 ms |
| Aug 1, 2026 | 346 ms |
| Aug 8, 2026 | 344 ms |
| Aug 15, 2026 | 336 ms |
| Aug 22, 2026 | 337 ms |
| Aug 29, 2026 | 326 ms |
| Sep 5, 2026 | 323 ms |
| Sep 12, 2026 | 323 ms |
| Sep 19, 2026 | 326 ms |
| Sep 26, 2026 | 336 ms |
| Oct 3, 2026 | 340 ms |
| Oct 10, 2026 | 343 ms |
| Oct 17, 2026 | 339 ms |
| Oct 24, 2026 | 346 ms |
| Oct 31, 2026 | 351 ms |
| Nov 7, 2026 | 353 ms |
| Nov 14, 2026 | 350 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 347 ms
347 msReal visitors wait 347 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 324 ms to 350 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-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user TTFB: 750 ms
750 msReal visitors wait 750 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.2 MB
6.2 MBYour homepage downloads 6.2 MB on a phone, 1.2 MB of it images (20%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
rb_82225_2.png 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).
1 image far larger than shown
43 KiB1 image is downloaded at several times the size a phone draws it, for example RosemaryShampoo2.0_PersonalizedBanner_1600x900_2cf60d67-cc04 at 1,600 px wide, shown at 390 px. Resized copies would save about 43 KiB.
1 image in older formats
1 image (42 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.77 g of CO₂e: 212.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
27 text elements with low contrast
27 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Inline text spacing must be adjustable with custom stylesheets (2 elements)
Inline text spacing must be adjustable with custom stylesheets: 2 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
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 (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
50 links without text
50 visible links have no text or label, so screen readers cannot say where they go.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 16 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Pilgrim India - Official Website | Skin • Hair • Makeup • Fragrance”.
Structured data has 1 problem
Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected non-whitespace character after JSON at position 9)”.
509 internal links, 0 external
The homepage links to 509 pages on discoverpilgrim.com and 0 external pages.
6 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “Pilgrim - Premium International Brand | No Animal Testing, No Harmful Chemicals, Natural, Vegan Friendly, FDA Approved.”.
One H1 headline
Your main headline reads: “Pilgrim India”.
Canonical URL set
The canonical URL is https://discoverpilgrim.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://discoverpilgrim.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 (3,699 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://discoverpilgrim.com/llms.txt (42 KiB, 254 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://discoverpilgrim.com/collections/bestsellers, https://discoverpilgrim.com/products/3-redensyl-4-anagain-hair-growth-serum, https://discoverpilgrim.com/products/korean-rice-water-hydra-glow-moisturizer, https://discoverpilgrim.com/products/10-vitamin-c-face-serum-for-daily-brightness, https://discoverpilgrim.com/products/10-niacinamide-face-serum-for-acne-marks and https://discoverpilgrim.com/products/australian-tea-tree-non-drying-anti-dandruff-shampoo 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 185 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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://discoverpilgrim.com/.
17 small tap targets
17 of 83 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'IntersectionObserver': parameter 1 is not of type 'Element'.”.
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 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 1,096 words of copy
The homepage carries about 1,096 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Track Order” and “START SHOPPING”.
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “Track Order” and “Shop By Collection”.
51 short forms
51 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and PostHog.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 3 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.
35 cookies set on arrival
35Opening the homepage sets 35 cookies, 3 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.
38 other companies contacted
Loading the homepage contacts 38 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 discoverpilgrim.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | PostHog | Microsoft Clarity
- Hosting
- Shopify
Company
- Employees
- 810
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on discoverpilgrim.com, including 4 speed issues, 2 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.