Website review, no card needed

am-ind.com logo

am-ind.com website review

Visit site (opens in a new tab)Reviewed 20 October 202630 issues · 89 checks

This review found 30 issues worth fixing on am-ind.com, 15 of them high impact, across 89 checks. The most urgent: mobile performance score: 37. 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
7.9 s3.2 sMay 2Oct 177.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.4 s
May 9, 20266.2 s
May 16, 20266.2 s
May 23, 20266.2 s
May 30, 20264.9 s
Jun 6, 20264.5 s
Jun 13, 20264.4 s
Jun 20, 20264.2 s
Jun 27, 20264.0 s
Jul 4, 20263.7 s
Jul 11, 20263.8 s
Jul 18, 20264.1 s
Jul 25, 20264.8 s
Aug 1, 20265.9 s
Aug 8, 20266.2 s
Aug 15, 20265.9 s
Aug 22, 20265.0 s
Aug 29, 20264.5 s
Sep 5, 20264.0 s
Sep 12, 20264.5 s
Sep 19, 20265.1 s
Sep 26, 20265.7 s
Oct 3, 20266.0 s
Oct 10, 20266.5 s
Oct 17, 20267.3 s
Real-visitor tap response (INP)75th percentile, phones
249 ms112 msMay 2Oct 17192 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026215 ms
May 9, 2026171 ms
May 16, 2026177 ms
May 23, 2026181 ms
May 30, 2026204 ms
Jun 6, 2026212 ms
Jun 13, 2026195 ms
Jun 20, 2026205 ms
Jun 27, 2026213 ms
Jul 4, 2026205 ms
Jul 11, 2026213 ms
Jul 18, 2026169 ms
Jul 25, 2026147 ms
Aug 1, 2026132 ms
Aug 8, 2026128 ms
Aug 15, 2026144 ms
Aug 22, 2026146 ms
Aug 29, 2026155 ms
Sep 5, 2026171 ms
Sep 12, 2026224 ms
Sep 19, 2026232 ms
Sep 26, 2026233 ms
Oct 3, 2026232 ms
Oct 10, 2026220 ms
Oct 17, 2026192 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 am-ind.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. am-ind.com at 1.3 s1.3 s
  2. am-ind.com at 2.5 s2.5 s
  3. am-ind.com at 3.8 s3.8 s
  4. am-ind.com at 5.0 s5.0 s
  5. am-ind.com at 6.3 s6.3 s
  6. am-ind.com at 7.5 s7.5 s
  7. am-ind.com at 8.8 s8.8 s
  8. am-ind.com at 10.1 s10.1 s

Speed

9 to fix37
  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 4.2 s

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

  • Use efficient cache lifetimes

    150 ms · 741 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hubspot and hs-sites.com and others), adding 1.3 MB and 657 ms of main-thread time.

  • Document request latency

    693 KiB

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

  • Google Tag Manager adds 463 ms

    463 ms

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

  • Reduce unused JavaScript

    474 KiB

    About 474 KiB of JavaScript is downloaded but never used on this page.

  • 14 long tasks on the main thread

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

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 599 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 · 215 KiB

    22 images could be 215 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.

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    13 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 499 ms

    499 ms

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

Core Web Vitals

10 to fix67
  • 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: 7.4 s

    7.4 s

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

  • Real-user FCP: 6.7 s

    6.7 s

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

  • Real-user TTFB: 5.4 s

    5.4 s

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

  • Speed Index: 18.3 s

    18.3 s

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

  • Largest Contentful Paint: 8.8 s

    8.8 s

    Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Kennametal Has ArrivedExplore over 40,000 Kennametal tools …”. Most of its time is resource load delay (6.5 s).

  • Time to Interactive: 20.9 s

    20.9 s

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

  • First Contentful Paint: 5.9 s

    5.9 s

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

  • Total Blocking Time: 760 ms

    760 ms

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

  • 19 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

3 checks passed
  • Real-user INP: 195 ms

    195 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 107 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 107 requests on a phone: scripts 1.2 MB (15), HTML 1.0 MB (2) and images 618 KiB (60). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.95 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 8695
  • 4 buttons without a name

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

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

  • 6 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 10090
  • Title is short (21 characters)

    Your title is only 21 characters: “Home | A&M Industrial”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image (also missing: 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.

  • 117 internal links, 10 external

    The homepage links to 117 pages on am-ind.com and 10 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Leading U.S. industrial distributor of metalworking tools, abrasives, safety products, PPE, MRO supplies, material hand…”.

  • One H1 headline

    Your main headline reads: “Kennametal Has Arrived”.

  • Canonical URL set

    The canonical URL is https://www.am-ind.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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.am-ind.com/sitemapindex.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.am-ind.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.

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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

100
  • 8 pages slow to respond

    https://www.am-ind.com/catalog/abrasives, https://www.am-ind.com/catalog/adhesives-and-sealants, https://www.am-ind.com/catalog/cutting-tools-and-metalworking, https://www.am-ind.com/catalog/janitorial-and-facility-maintenance, https://www.am-ind.com/catalog/fasteners and https://www.am-ind.com/catalog/hand-tools and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    8 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

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

Best practices

2 to fixGoogle 7394
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 distorted image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 opening hours

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

  • No form on the homepage

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

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

    The homepage carries about 647 words of visible text.

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Request A Quote”, “Pricing Updates” and “Quick Order”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

  • 22 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on am-ind.com, including 19 speed issues, 2 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