Website review, no card needed

abeer.in logo

abeer.in website review

Visit site (opens in a new tab)Reviewed 27 October 202639 issues · 79 checks

This review found 39 issues worth fixing on abeer.in, 18 of them high impact, across 79 checks. The most urgent: avoid multiple page redirects. 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

Full-page screenshot of abeer.in (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abeer.in at 0.6 s0.6 s
  2. abeer.in at 1.1 s1.1 s
  3. abeer.in at 1.7 s1.7 s
  4. abeer.in at 2.2 s2.2 s
  5. abeer.in at 2.8 s2.8 s
  6. abeer.in at 3.3 s3.3 s
  7. abeer.in at 3.9 s3.9 s
  8. abeer.in at 4.5 s4.5 s

Speed

5 to fix58
  • Avoid multiple page redirects

    2.9 s

    The page goes through 2 redirects before it starts loading, costing about 2.9 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    1.9 s · 484 KiB

    About 484 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

  • Minify JavaScript

    300 ms · 50 KiB

    50 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.7 s

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

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    31 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 90 but mobile only 58. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 4 KiB and 0 ms of main-thread time.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

7 to fix100
  • 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: 14.3 s

    14.3 s

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

  • Time to Interactive: 14.4 s

    14.4 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

    The first text or image appears after 4.8 s on a phone. Good is under 1.8 s.

  • Speed Index: 7.3 s

    7.3 s

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

  • Real-user TTFB: 845 ms

    845 ms

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

  • 18 images without width and height

    18 images have no width and height attributes, so the layout jumps as each one loads.

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Total Blocking Time: 122 ms

    122 ms

    Scripts block the page for only 122 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix69
  • Page weight: 2.8 MB in 307 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 307 requests on a phone: scripts 1.1 MB (79), other files 776 KiB (110) and images 558 KiB (58). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Duke_fd01b1b7-6945-4aa6-9144-eb74fbf08aad_170x.jpg 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

    42 KiB

    1 image is downloaded at several times the size a phone draws it, for example gift-set.png at 480 px wide, shown at 80 px. Resized copies would save about 42 KiB.

  • 1 image in older formats

    1 image (64 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.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

Accessibility

12 to fixGoogle 7584
  • ARIA roles used must conform to valid values (1 element)

    ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • <dt> and <dd> elements must be contained by a <dl> (40 elements)

    <dt> and <dd> elements must be contained by a <dl>: 40 elements on the page fail this check, rated serious by axe-core.

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (20 elements)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 20 elements on the page fail this check, rated serious by axe-core.

  • 7 tap targets too small

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails 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.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 20 images without alt text

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 10 links without text

    10 visible links have no text or label, so screen readers cannot say where they go.

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (13 characters)

    Your title is only 13 characters: “abeer-perfume”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “ABOUTAbeer”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 57 internal links, 0 external

    The homepage links to 57 pages on abeer.in and 0 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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://abeer.in/sitemap.xml.

AI search readiness

100
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 (816 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://abeer.in/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://abeer.in/collections/all-products, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 8 pages without a meta description

    https://abeer.in/collections/all, https://abeer.in/collections/men, https://abeer.in/collections/women, https://abeer.in/collections/unisex, https://abeer.in/collections/gift-set and https://abeer.in/pages/contact and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://abeer.in/collections/all, https://abeer.in/collections/men, https://abeer.in/collections/women, https://abeer.in/collections/unisex, https://abeer.in/collections/gift-set and https://abeer.in/collections/perfumes have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://abeer.in/pages/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

4 checks passed
  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-bundler.nice-team.net/app/css/style.css?shop=house-of-fragrance-in.myshopify.c…”.

2 checks passed
  • Tap targets are thumb-sized

    30 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 604 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Subscribe” and “Contact Us”.

  • 18 short forms

    18 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 36 testimonial or review blocks, 5 customer or partner logos and a star rating.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 4 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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 abeer.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
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on abeer.in, including 12 speed issues, 4 SEO issues and 3 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