Website review, no card needed

alamo-group.com logo

alamo-group.com website review

Visit site (opens in a new tab)Reviewed 18 October 202636 issues · 78 checks

This review found 36 issues worth fixing on alamo-group.com, 14 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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.1 s1.5 sApr 25Oct 101.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.8 s
May 2, 20261.7 s
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.8 s
May 30, 20262.1 s
Jun 6, 20261.9 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20262.1 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
118 ms75 msApr 25Oct 1087 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202688 ms
May 2, 202687 ms
May 9, 202686 ms
May 16, 202694 ms
May 23, 202696 ms
May 30, 202699 ms
Jun 6, 202687 ms
Jun 13, 202680 ms
Jun 20, 202680 ms
Jun 27, 202685 ms
Jul 4, 2026113 ms
Jul 11, 2026107 ms
Jul 18, 2026112 ms
Jul 25, 202696 ms
Aug 1, 202693 ms
Aug 8, 202688 ms
Aug 15, 202690 ms
Aug 22, 202689 ms
Aug 29, 202686 ms
Sep 5, 2026102 ms
Sep 12, 2026100 ms
Sep 19, 202696 ms
Sep 26, 2026100 ms
Oct 3, 202687 ms
Oct 10, 202687 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 alamo-group.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix60
  • Use efficient cache lifetimes

    2.7 s · 10.5 MB

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

  • Render-blocking requests

    4.7 s

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

  • Improve image delivery

    2.4 MB

    8 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60 (desktop: 60). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    460 ms · 96 KiB

    About 96 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 88 KiB

    About 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and geeksforgeeks.org), adding 257 KiB and 77 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

7 to fix100
  • 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: 16.1 s

    16.1 s

    Your largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to improve your experience and to understand…”.

  • First Contentful Paint: 6.1 s

    6.1 s

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

  • Time to Interactive: 17.1 s

    17.1 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user TTFB: 882 ms

    882 ms

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

  • 93 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

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

  • Real-user INP: 100 ms

    100 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, 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

5 to fix18
  • Page weight: 15.8 MB in 97 requests

    15.8 MB

    Your homepage downloads 15.8 MB in 97 requests on a phone: media 11.1 MB (6), images 3.7 MB (69) and fonts 574 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Municipal Workers.png weighs 1.7 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1,009 KiB

    1 image is downloaded at several times the size a phone draws it, for example Municipal Workers.png at 1,680 px wide, shown at 366 px. Resized copies would save about 1,009 KiB.

  • 17 images in older formats

    17 images (3.3 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.

  • 9 images below the first screen load straight away

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

  • About 4.5 g of CO₂ per visit

    4.47 g

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

Accessibility

3 to fixGoogle 9493
  • 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.

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

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

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 76 images in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

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

SEO

7 to fixGoogle 8272
  • No H1 headline

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

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

  • No XML sitemap

    No XML sitemap at https://www.alamo-group.com/sitemap.xml, so Google discovers your pages only by following links.

  • 16 links with vague text

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

  • No robots.txt

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

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 225 internal links, 3 external

    The homepage links to 225 pages on alamo-group.com and 3 external pages.

3 checks passed
  • Meta description: 85 characters

    Your meta description is 85 characters: “Alamo Group, the parent company ofglobal brands focused in infrastructure maintenance”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Alamo Group - Alamo Group Inc.”.

  • Open Graph tags complete

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

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.alamo-group.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,000 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 14 pages share a title

    https://www.alamo-group.com/privacy.html, https://www.alamo-group.com/robert-hureau.html, https://www.alamo-group.com/agnes-kamps.html, https://www.alamo-group.com/greg-lucas.html, https://www.alamo-group.com/kevin-thomas.html and https://www.alamo-group.com/ed-rizzuti.html and 8 others all use the title “Alamo Group”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages share a meta description

    https://www.alamo-group.com/privacy.html, https://www.alamo-group.com/about-us, https://www.alamo-group.com/agnes-kamps.html, https://www.alamo-group.com/greg-lucas.html, https://www.alamo-group.com/kevin-thomas.html and https://www.alamo-group.com/ed-rizzuti.html and 3 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.alamo-group.com/privacy.html, https://www.alamo-group.com/about-us, https://www.alamo-group.com/robert-hureau.html, https://www.alamo-group.com/agnes-kamps.html, https://www.alamo-group.com/greg-lucas.html and https://www.alamo-group.com/kevin-thomas.html and 9 others have 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 80 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • 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.

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

    The homepage carries about 434 words of visible text.

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Information Request”, “Contact” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 18 cookies set on arrival

    18

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

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics

Company

Employees
3,070
Founded
1969
Headquarters
Seguin

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on alamo-group.com, including 13 speed issues, 7 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