Website review, no card needed

aimil.com logo

aimil.com website review

Visit site (opens in a new tab)Reviewed 20 November 202651 issues · 91 checks

This review found 51 issues worth fixing on aimil.com, 15 of them high impact, across 91 checks. The most urgent: render-blocking requests. 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.8 s2.3 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.6 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.5 s
Oct 31, 20262.4 s
Nov 7, 20262.4 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
196 ms125 msMay 30Nov 14188 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026133 ms
Jun 6, 2026135 ms
Jun 13, 2026135 ms
Jun 20, 2026134 ms
Jun 27, 2026135 ms
Jul 4, 2026137 ms
Jul 11, 2026139 ms
Jul 18, 2026144 ms
Jul 25, 2026143 ms
Aug 1, 2026141 ms
Aug 8, 2026150 ms
Aug 15, 2026160 ms
Aug 22, 2026167 ms
Aug 29, 2026167 ms
Sep 5, 2026163 ms
Sep 12, 2026161 ms
Sep 19, 2026166 ms
Sep 26, 2026172 ms
Oct 3, 2026170 ms
Oct 10, 2026170 ms
Oct 17, 2026168 ms
Oct 24, 2026169 ms
Oct 31, 2026175 ms
Nov 7, 2026185 ms
Nov 14, 2026188 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 aimil.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aimil.com at 1.1 s1.1 s
  2. aimil.com at 2.1 s2.1 s
  3. aimil.com at 3.2 s3.2 s
  4. aimil.com at 4.2 s4.2 s
  5. aimil.com at 5.3 s5.3 s
  6. aimil.com at 6.4 s6.4 s
  7. aimil.com at 7.4 s7.4 s
  8. aimil.com at 8.5 s8.5 s

Speed

9 to fix56
  • Render-blocking requests

    4.7 s

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

  • Use efficient cache lifetimes

    1.9 s · 1.6 MB

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

  • Reduce unused JavaScript

    2.4 s · 440 KiB

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

  • Font display

    1.8 s

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

  • Mobile performance score: 56

    56/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 990 KiB and 765 ms of main-thread time.

  • Google Tag Manager adds 564 ms

    564 ms

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

  • Improve image delivery

    150 ms · 292 KiB

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 29 KiB

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

  • Minify JavaScript

    150 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 3 KiB

    3 KiB could be saved by minifying CSS.

  • Reduce unused CSS

    39 KiB

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

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

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

  • Server response: 249 ms

    249 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 12.7 s

    12.7 s

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

  • Speed Index: 13.6 s

    13.6 s

    Visually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 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: 3.0 s

    3.0 s

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

  • Real-user INP: 209 ms

    209 ms

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

  • Real-user CLS: 0.13

    0.13

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

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

    +39%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 216 ms

    216 ms

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

2 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 2.4 MB in 116 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 116 requests on a phone: scripts 1.1 MB (35), images 1.1 MB (47) and fonts 96 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (814 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 below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.69 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

11 to fixGoogle 7485
  • Unlabelled dropdowns

    1 dropdown has no label.

  • Orphan list items

    Some list items are not inside a list.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 13 form fields without a label

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

  • 2 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

6 to fixGoogle 7772
  • No H1 headline

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

  • Title is long (87 characters)

    Your title is 87 characters, so Google will cut it off around 60: “Cement, Material Testing Instruments, Concrete Equipment, Civil Engineering - Aimil Ltd”.

  • Meta description is long (200 characters)

    Your meta description is 200 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.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 207 internal links, 12 external

    The homepage links to 207 pages on aimil.com and 12 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.aimil.com/.

  • Structured data in place

    Structured data found: WebSite.

  • 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://www.aimil.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://www.aimil.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 (1,198 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.aimil.com/newsletters has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.aimil.com/exhibitions-and-trainings has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

4 to fixGoogle 6983
  • 18 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

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

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 3 low-resolution images

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

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.

  • Thin social proof

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

  • A 13-field form

    Your longest form asks for 13 fields (0 required). Every extra field lowers completion.

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

    The homepage carries about 661 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Register Your Products”, “Contact Us” and “Apply”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

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.

  • 9 cookies set on arrival

    9

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 aimil.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 © 2016.

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Company

Headquarters
New Delhi

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on aimil.com, including 21 speed issues, 6 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