Website review, no card needed

aacipl.com logo

aacipl.com website review

Visit site (opens in a new tab)Reviewed 3 November 202626 issues · 72 checks

This review found 26 issues worth fixing on aacipl.com, 7 of them high impact, across 72 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

Full-page screenshot of aacipl.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aacipl.com at 0.9 s0.9 s
  2. aacipl.com at 1.7 s1.7 s
  3. aacipl.com at 2.6 s2.6 s
  4. aacipl.com at 3.4 s3.4 s
  5. aacipl.com at 4.3 s4.3 s
  6. aacipl.com at 5.1 s5.1 s
  7. aacipl.com at 6.0 s6.0 s
  8. aacipl.com at 6.8 s6.8 s

Speed

4 to fix75
  • Reduce unused JavaScript

    1.1 s · 201 KiB

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

  • Mobile performance score: 75

    75/100

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

  • Use efficient cache lifetimes

    600 ms · 335 KiB

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

  • Render-blocking requests

    750 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, hcaptcha.com and Cloudflare CDN and others), adding 442 KiB and 290 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 14 KiB

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

  • Improve image delivery

    158 KiB

    1 image could be 158 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 5 long tasks on the main thread

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

  • Minify JavaScript

    31 KiB

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 31 ms

    31 ms

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

Core Web Vitals

4 to fix71
  • Largest Contentful Paint: 5.5 s

    5.5 s

    Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Finest Ingredients for your Fragrance Flavor Food Cosme…”.

  • 36 images without width and height

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

  • Time to Interactive: 5.5 s

    5.5 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Total Blocking Time: 136 ms

    136 ms

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

  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

3 to fix60
  • 1 image over 500 KB

    gridimage.svg weighs 1.8 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.7 MB in 38 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 38 requests on a phone: images 2.2 MB (23), scripts 447 KiB (5) and fonts 100 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    83 KiB

    1 image is downloaded at several times the size a phone draws it, for example Ecovadis-2026.png at 1,031 px wide, shown at 262 px. Resized copies would save about 83 KiB.

  • 1 image in older formats

    1 image (198 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 (198 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.78 g

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

Accessibility

7 to fixGoogle 7585
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

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

  • 22 images without alt text

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

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

    All page content should be contained by landmarks: 18 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.

  • 2 form fields without a label

    2 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 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 27 automated accessibility rules passed

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

SEO

3 to fixGoogle 9287
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 5 H1 headlines

    There are 5 <h1> headlines (“The Finest Ingredients”, “for your Fragrance Flavor Food Cosmetic” and “creations”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • 21 internal links, 1 external

    The homepage links to 21 pages on aacipl.com and 1 external page.

5 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “Associate Allied Chemicals, a leading global supplier of high-quality ingredients, serving the fragrance and flavor, in…”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Home Page | Associate Allied Chemicals”.

  • 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://aacipl.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://aacipl.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 (296 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 4 pages share a meta description

    https://aacipl.com/products, https://aacipl.com/aboutus, https://aacipl.com/international and https://aacipl.com/contactus use the same meta description. A description written for each page earns more clicks.

  • 4 internal pages checked

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

7 checks passed
  • Linked pages load

    All 4 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 4 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 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 8196
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix75
  • 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.

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

  • About 276 words of copy

    The homepage carries about 276 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”.

  • Social proof on the page

    Social proof on the homepage: 12 customer or partner logos and “1600+ Customers”.

  • Analytics in place

    Analytics detected: 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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 aacipl.com, 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 © 2025.

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on aacipl.com, including 8 speed issues, 3 SEO issues and 1 conversion gap. 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