Website review, no card needed

aepl-india.com logo

aepl-india.com website review

Visit site (opens in a new tab)Reviewed 17 November 202633 issues · 76 checks

This review found 33 issues worth fixing on aepl-india.com, 10 of them high impact, across 76 checks. The most urgent: improve image delivery. 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 aepl-india.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aepl-india.com at 0.4 s0.4 s
  2. aepl-india.com at 0.8 s0.8 s
  3. aepl-india.com at 1.1 s1.1 s
  4. aepl-india.com at 1.5 s1.5 s
  5. aepl-india.com at 1.9 s1.9 s
  6. aepl-india.com at 2.3 s2.3 s
  7. aepl-india.com at 2.6 s2.6 s
  8. aepl-india.com at 3.0 s3.0 s

Speed

4 to fix74
  • Improve image delivery

    8.8 s · 2.7 MB

    35 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.8 s faster on a phone.

  • Use efficient cache lifetimes

    3.9 s · 1.3 MB

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

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused CSS

    150 ms · 15 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (GoDaddy, JSDelivr CDN and Cloudflare CDN and others), adding 288 KiB and 55 ms of main-thread time.

  • Font display

    50 ms

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.2 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

3 to fix67
  • Largest Contentful Paint: 12.8 s

    12.8 s

    Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Crafting Industrial Excellence Since 1971 Explore More”.

  • Time to Interactive: 12.8 s

    12.8 s

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

  • 3 images without width and height

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

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

4 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • 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

4 to fix48
  • 12 images far larger than shown

    1.4 MB

    12 images are downloaded at several times the size a phone draws them, for example founder.PNG at 563 px wide, shown at 110 px. Resized copies would save about 1.4 MB.

  • Page weight: 3.5 MB in 56 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 56 requests on a phone: images 3.2 MB (45), fonts 228 KiB (2) and scripts 50 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 16 images in older formats

    16 images (1.7 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.

  • 20 images below the first screen load straight away

    20 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    1.00 g

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

Accessibility

7 to fixGoogle 8886
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

1 checks passed
  • 30 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 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

6 to fixGoogle 10066
  • 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: “AEPL - Amalgamated Engineers Private Limited | Industrial Tools & Engineering Solutions”.

  • No structured data

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

  • 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 (224 characters)

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

  • No robots.txt

    There is no robots.txt at aeplindustrials.com/robots.txt, the first file search crawlers ask for.

  • 12 internal links, 5 external

    The homepage links to 12 pages on aepl-india.com and 5 external pages.

2 checks passed
  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.aeplindustrials.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.aeplindustrials.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 6 pages share a title

    https://www.aeplindustrials.com/products/kennametal-widia, https://www.aeplindustrials.com/products/grindwell-norton-limited-saint-gobain-abrasives, https://www.aeplindustrials.com/products/fuji-atlas-copco, https://www.aeplindustrials.com/products/desoutter-atlas-copco, https://www.aeplindustrials.com/products/chicago-pneumatic-atlas-copco and https://www.aeplindustrials.com/products/rodcraft-atlas-copco all use the title “AEPL Product List”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.aeplindustrials.com/products/kennametal-widia, https://www.aeplindustrials.com/products/grindwell-norton-limited-saint-gobain-abrasives, https://www.aeplindustrials.com/products/fuji-atlas-copco, https://www.aeplindustrials.com/products/desoutter-atlas-copco, https://www.aeplindustrials.com/products/chicago-pneumatic-atlas-copco and https://www.aeplindustrials.com/products/rodcraft-atlas-copco have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.aeplindustrials.com/products/desoutter-atlas-copco 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.

  • 6 internal pages checked

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

5 checks passed
  • Linked pages load

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

Best practices

4 to fixGoogle 9270
  • 3 broken images

    3 images failed to load on a phone, for example https://www.aeplindustrials.com/images/about-us.jpg.

  • 7 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • 1 distorted image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 653 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get in Touch”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Get in Touch” and “[email protected]”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks and 32 customer or partner logos.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 3 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 aepl-india.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

Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on aepl-india.com, including 7 speed issues, 6 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