Website review, no card needed

aquapharm-india.com logo

aquapharm-india.com website review

Visit site (opens in a new tab)Reviewed 1 November 202654 issues · 99 checks

This review found 54 issues worth fixing on aquapharm-india.com, 26 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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
11.4 s2.1 sMay 9Oct 243.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 202610.3 s
May 16, 20267.0 s
May 23, 20265.1 s
May 30, 20263.6 s
Jun 6, 20263.5 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.7 s
Jul 4, 20263.6 s
Jul 11, 20263.6 s
Jul 18, 20263.7 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.7 s
Aug 29, 20263.9 s
Sep 5, 20263.8 s
Sep 12, 20263.6 s
Sep 19, 20263.4 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
1.5 s62 msMay 9Oct 24268 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 20261.4 s
May 16, 20261.1 s
May 23, 2026862 ms
May 30, 2026584 ms
Jun 6, 2026383 ms
Jun 13, 2026398 ms
Jun 20, 2026491 ms
Jun 27, 2026446 ms
Jul 4, 2026339 ms
Jul 11, 2026287 ms
Jul 18, 2026268 ms
Jul 25, 2026296 ms
Aug 1, 2026312 ms
Aug 8, 2026376 ms
Aug 15, 2026312 ms
Aug 22, 2026282 ms
Aug 29, 2026271 ms
Sep 5, 2026248 ms
Sep 12, 2026233 ms
Sep 19, 2026255 ms
Sep 26, 2026275 ms
Oct 3, 2026309 ms
Oct 10, 2026264 ms
Oct 17, 2026263 ms
Oct 24, 2026268 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 aquapharm-india.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aquapharm-india.com at 1.6 s1.6 s
  2. aquapharm-india.com at 3.1 s3.1 s
  3. aquapharm-india.com at 4.7 s4.7 s
  4. aquapharm-india.com at 6.3 s6.3 s
  5. aquapharm-india.com at 7.8 s7.8 s
  6. aquapharm-india.com at 9.4 s9.4 s
  7. aquapharm-india.com at 11.0 s11.0 s
  8. aquapharm-india.com at 12.6 s12.6 s

Speed

17 to fix30
  • Reduce unused JavaScript

    4.0 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

  • Render-blocking requests

    4.5 s

    27 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.

  • amcharts.com adds 2.2 s

    2.2 s

    amcharts.com costs a phone 2.2 s of main-thread work and 733 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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

    1.8 s · 349 KiB

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

  • Font display

    1.9 s

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

  • Reduce unused CSS

    1.4 s · 286 KiB

    About 286 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6,749 HTML elements

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

  • Main-thread work: 6.5 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (amcharts.com, Google CDN and Google Tag Manager and others), adding 1.5 MB and 2.7 s of main-thread time.

  • Reduce initial server response time

    670 ms

    Reduce initial server response time. Google estimates savings of 670 ms on a phone.

  • Document request latency

    650 ms

    The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Improve image delivery

    400 ms · 206 KiB

    9 images could be 206 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Google CDN adds 238 ms

    238 ms

    Google CDN costs a phone 238 ms of main-thread work and 349 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.

  • Google Tag Manager adds 231 ms

    231 ms

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

  • Server response: 770 ms

    770 ms

    Your server takes 770 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Minify JavaScript

    150 ms · 23 KiB

    23 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    100 ms · 56 KiB

    Polyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

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

Core Web Vitals

11 to fix33
  • 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.7 s

    4.7 s

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

  • Real-user INP: 951 ms

    951 ms

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 30.4 s

    30.4 s

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

  • Speed Index: 19.9 s

    19.9 s

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

  • Time to Interactive: 31.4 s

    31.4 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • 2 images without width and height

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

4 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 79% faster for real visitors

    -79%

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

  • Largest content (LCP) got 58% faster for real visitors

    -58%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 13.8 MB in 151 requests

    13.8 MB

    Your homepage downloads 13.8 MB in 151 requests on a phone: images 10.6 MB (55), scripts 2.1 MB (51) and fonts 453 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    2.-Brain-Treat.jpg weighs 3.0 MB. On a phone connection a single image that size takes seconds.

  • 26 images in older formats

    26 images (9.8 MB) 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 3.9 g of CO₂ per visit

    3.91 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

13 to fixGoogle 8086
  • Form elements should have a visible label (3 elements)

    Form elements should have a visible label: 3 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.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • <marquee> elements are deprecated and must not be used (1 element)

    <marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

  • 31 images without alt text

    31 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Main landmark should not be contained in another landmark (1 element)

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

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 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.

  • 10 form fields without a label

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

  • 1 link without text

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

  • Headings skip levels

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

1 checks passed
  • 50 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: 50 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10088
  • Meta description is long (169 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 69 internal links, 3 external

    The homepage links to 69 pages on aquapharm-india.com and 3 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “About Aquapharm”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Aquapharm - specialty chemicals manufacturer and supplier.”.

  • Canonical URL set

    The canonical URL is https://aquapharm-india.com/.

  • 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://aquapharm-india.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

  • No llms.txt

    There is no https://aquapharm-india.com/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
  • 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 (2,583 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://aquapharm-india.com/methylene-bis-thiocynate-mbt, whose canonical is https://aquapharm-india.com/other-products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://aquapharm-india.com/detergents took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 50 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.

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: “More than 1000 patients”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 24-field form

    Your longest form asks for 24 fields (15 required). Every extra field lowers completion.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 1,215 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 4 calls to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 8 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Public Domain Registry

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on aquapharm-india.com, including 28 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

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