Website review, no card needed

alchemistindia.net logo

alchemistindia.net website review

Visit site (opens in a new tab)Reviewed 18 October 202637 issues · 74 checks

This review found 37 issues worth fixing on alchemistindia.net, 8 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. 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.6 s1.7 sApr 25Oct 102.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.4 s
May 2, 20262.5 s
May 9, 20262.3 s
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.0 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
106 ms72 msApr 25Oct 1094 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202688 ms
May 2, 202688 ms
May 9, 202688 ms
May 16, 202687 ms
Jun 13, 202684 ms
Jun 20, 202685 ms
Jun 27, 202685 ms
Jul 4, 202682 ms
Jul 11, 202682 ms
Jul 18, 202676 ms
Jul 25, 202680 ms
Aug 1, 202691 ms
Aug 8, 202695 ms
Aug 15, 2026102 ms
Aug 22, 202693 ms
Aug 29, 202693 ms
Sep 5, 202689 ms
Oct 10, 202694 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 alchemistindia.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alchemistindia.net at 0.5 s0.5 s
  2. alchemistindia.net at 1.0 s1.0 s
  3. alchemistindia.net at 1.5 s1.5 s
  4. alchemistindia.net at 2.0 s2.0 s
  5. alchemistindia.net at 2.5 s2.5 s
  6. alchemistindia.net at 3.0 s3.0 s
  7. alchemistindia.net at 3.5 s3.5 s
  8. alchemistindia.net at 4.0 s4.0 s

Speed

5 to fix75
  • Use efficient cache lifetimes

    1.4 s · 1.0 MB

    31 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

  • Font display

    2.2 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.2 s).

  • Mobile performance score: 75

    75/100

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

  • Render-blocking requests

    950 ms

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

  • Improve image delivery

    320 KiB

    8 images could be 320 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    150 ms · 30 KiB

    About 30 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cloudflare, Bootstrap CDN and GitHub and others), adding 59 KiB and 21 ms of main-thread time.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

2 checks passed
  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 74 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

10 to fix0
  • 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.

  • Real-user LCP: 4.4 s

    4.4 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Case Study Coca Cola”. Most of its time is resource load delay (1.7 s).

  • Real-user CLS: 0.18

    0.18

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • Cumulative Layout Shift: 0.127

    0.127

    The layout shifts by 0.127 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 16 images without width and height

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

  • Time to Interactive: 4.2 s

    4.2 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

2 checks passed
  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

3 to fix73
  • 12 images in older formats

    12 images (690 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.

  • 4 images far larger than shown

    138 KiB

    4 images are downloaded at several times the size a phone draws them, for example anujita_jain.jpg at 1,000 px wide, shown at 150 px. Resized copies would save about 138 KiB.

  • 6 images below the first screen load straight away

    6 images further down the page (320 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.3 g of CO₂ per visit

    0.30 g

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

1 checks passed
  • Page weight: 1.1 MB in 45 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 45 requests on a phone: images 744 KiB (28), fonts 239 KiB (3) and scripts 65 KiB (7). That is a lean page.

Accessibility

5 to fixGoogle 7891
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 4 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 10071
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Alchemist | Unlocking Brand Potential | Advertising Agency in India”.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (162 characters)

    Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 26 internal links, 6 external

    The homepage links to 26 pages on alchemistindia.net and 6 external pages.

3 checks passed
  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://alchemistindia.net/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://alchemistindia.net/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.

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 contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

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

Other pages

4 to fix81
  • 13 pages share a title

    /, https://alchemistindia.net/about.php, https://alchemistindia.net/services.php, https://alchemistindia.net/work.php, https://alchemistindia.net/careers.php and https://alchemistindia.net/contact.php and 7 others all use the title “Alchemist | Unlocking Brand Potential | Advertising Agency in India”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://alchemistindia.net/more2026 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages share a meta description

    https://alchemistindia.net/about.php, https://alchemistindia.net/services.php, https://alchemistindia.net/work.php, https://alchemistindia.net/careers.php, https://alchemistindia.net/contact.php and https://alchemistindia.net/case-study-coca-cola.php and 6 others use the same meta description. A description written for each page earns more clicks.

  • 12 pages without an H1

    https://alchemistindia.net/about.php, https://alchemistindia.net/services.php, https://alchemistindia.net/work.php, https://alchemistindia.net/careers.php, https://alchemistindia.net/contact.php and https://alchemistindia.net/case-study-coca-cola.php and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

    2 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'setAttribute')”.

1 checks passed
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 221 words

    The homepage has only about 221 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “CONTACT”, “JOIN OUR TEAM” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and “over 200 brands”.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

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

  • 5 other companies contacted

    Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 alchemistindia.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2023.

Stack

Framework
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on alchemistindia.net, including 15 speed issues, 5 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