Website review, no card needed

beardo.in logo

beardo.in website review

Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 87 checks

This review found 35 issues worth fixing on beardo.in, 11 of them high impact, across 87 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.4 s2.2 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
242 ms175 msMay 16Oct 31234 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026207 ms
May 23, 2026210 ms
May 30, 2026205 ms
Jun 6, 2026203 ms
Jun 13, 2026192 ms
Jun 20, 2026183 ms
Jun 27, 2026188 ms
Jul 4, 2026190 ms
Jul 11, 2026191 ms
Jul 18, 2026190 ms
Jul 25, 2026189 ms
Aug 1, 2026191 ms
Aug 8, 2026196 ms
Aug 15, 2026200 ms
Aug 22, 2026206 ms
Aug 29, 2026213 ms
Sep 5, 2026218 ms
Sep 12, 2026223 ms
Sep 19, 2026227 ms
Sep 26, 2026230 ms
Oct 3, 2026231 ms
Oct 10, 2026233 ms
Oct 17, 2026234 ms
Oct 24, 2026233 ms
Oct 31, 2026234 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

Full-page screenshot of beardo.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beardo.in at 0.4 s0.4 s
  2. beardo.in at 0.8 s0.8 s
  3. beardo.in at 1.1 s1.1 s
  4. beardo.in at 1.5 s1.5 s
  5. beardo.in at 1.9 s1.9 s
  6. beardo.in at 2.3 s2.3 s
  7. beardo.in at 2.6 s2.6 s
  8. beardo.in at 3.0 s3.0 s

Speed

13 to fix59
  • Main-thread work: 8.4 s

    A phone's processor spends 8.4 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 6,351 HTML elements

    The page has 6,351 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and gokwik.co and others), adding 1.9 MB and 1.5 s of main-thread time.

  • Improve image delivery

    350 ms · 1.3 MB

    46 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Reduce unused JavaScript

    704 KiB

    About 704 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 563 ms

    563 ms

    Google Tag Manager costs a phone 563 ms of main-thread work and 514 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

    574 KiB

    21 files are served with short cache lifetimes, so returning visitors download them again (574 KiB).

  • Clarity adds 330 ms

    330 ms

    Clarity costs a phone 330 ms of main-thread work and 32 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.

  • gokwik.co adds 233 ms

    233 ms

    gokwik.co costs a phone 233 ms of main-thread work and 532 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.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 267 ms. During a long task the page ignores taps.

  • Shopify adds 76 ms

    76 ms

    Shopify costs a phone 76 ms of main-thread work and 510 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

    57 KiB

    About 57 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    46 KiB

    Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    24 KiB

    24 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

  • 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 CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 12 ms

    12 ms

    Your server sent the HTML in 12 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix67
  • 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: 19.0 s

    19.0 s

    The page becomes fully interactive after 19.0 s. Good is under 3.8 s.

  • Speed Index: 11.8 s

    11.8 s

    Visually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Total Blocking Time: 620 ms

    620 ms

    Scripts block taps and scrolling for 620 ms in total while the page loads. Good is under 200 ms.

  • Real-user INP: 244 ms

    244 ms

    Real visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 12% slower for real visitors

    +12%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 207 ms to 234 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 651 ms

    651 ms

    Real visitors wait 651 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.043

    0.043

    The layout barely moves while loading (CLS 0.043, good is under 0.1).

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix53
  • Page weight: 6.1 MB in 502 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 502 requests on a phone: images 2.6 MB (93), scripts 1.6 MB (81) and other files 1.6 MB (295). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    image_21.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).

  • 6 images far larger than shown

    139 KiB

    6 images are downloaded at several times the size a phone draws them, for example image_24_4f77982d-2352-49e6-bf21-3b03e006b28a.jpg at 600 px wide, shown at 162 px. Resized copies would save about 139 KiB.

  • 7 images in older formats

    7 images (463 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 1.7 g of CO₂ per visit

    1.73 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.73 g of CO₂e: 207.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 8991
  • 10 tap targets too small

    10 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 117 form fields without a label

    117 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9296
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//beardo.in/cdn/shop/t/211/assets/beardo_logo_white_png…”.

  • 388 internal links, 4 external

    The homepage links to 388 pages on beardo.in and 4 external pages.

7 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “India's #1 men's grooming brand. Shop beard oils, growth serums, face washes, fragrances & more. Free shipping on order…”.

  • One H1 headline

    Your main headline reads: “Men's Grooming Products — Beard, Hair & Fragrance | Beardo India”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Men's Grooming Products - Beard, Hair & Fragrance – Beardo India”.

  • Canonical URL set

    The canonical URL is https://beardo.in/.

  • 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://beardo.in/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 2 AI crawlers

    Your robots.txt lets ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://beardo.in/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,577 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 191 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 4 third-party cookies

    4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) ReferenceError: oaiq is not defined”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    108 of 122 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 133 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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,304 words of copy

    The homepage carries about 1,304 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: “☀️ Beardo Buy 2 Get 3 Free Sale Is Live” and “SHOP NOW”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “☀️ Beardo Buy 2 Get 3 Free Sale Is Live”, “Look Book” and “Contact us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 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.

  • 39 other companies contacted

    Loading the homepage contacts 39 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 beardo.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Employees
280
Headquarters
Ahmedabad

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on beardo.in, including 19 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25