Website review, no card needed
ahfproducts.com website review
Visit site (opens in a new tab)Reviewed 25 October 202632 issues · 87 checks
This review found 32 issues worth fixing on ahfproducts.com, 13 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 96 ms |
| May 9, 2026 | 96 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 92 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 102 ms |
| Jul 4, 2026 | 102 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 94 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 92 ms |
| Aug 22, 2026 | 91 ms |
| Aug 29, 2026 | 93 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 110 ms |
| Oct 17, 2026 | 117 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
1.6 s · 3.8 MB31 files are served with short cache lifetimes, so returning visitors download them again (3.8 MB).
Reduce unused JavaScript
1.5 s · 164 KiBAbout 164 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.6 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.
Improve image delivery
1.7 MB13 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 87). Pages that score under 90 lose visitors before the first paint.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 677 ms. During a long task the page ignores taps.
Minify JavaScript
600 ms · 53 KiB53 KiB could be saved by minifying JavaScript.
Reduce unused CSS
450 ms · 98 KiBAbout 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,845 HTML elements
The page has 1,845 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (tagembed.com, Cookiebot and tagbox.com and others), adding 477 KiB and 309 ms of main-thread time.
Minify CSS
150 ms · 15 KiB15 KiB could be saved by minifying CSS.
Legacy JavaScript
150 ms · 8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Document request latency
21 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Phones get a much slower page than desktops
Desktop scores 87 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.7 s
19.7 sYour largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.5 s
21.5 sThe page becomes fully interactive after 21.5 s. Good is under 3.8 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
38 images without width and height
38 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 334 ms
334 msScripts block taps and scrolling for 334 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 96 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 610 ms
610 msReal visitors wait 610 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 165 requests
5.5 MBYour homepage downloads 5.5 MB in 165 requests on a phone: images 4.3 MB (44), scripts 750 KiB (49) and fonts 176 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Orphan list items
Some list items are not inside a list.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h5, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Structured data has 1 problem
Structured data found (Organization and WebPage) but with 1 problem, for example “Organization: missing name”.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
56 internal links, 13 external
The homepage links to 56 pages on ahfproducts.com and 13 external pages.
5 checks passed
One H1 headline
Your main headline reads: “honoring our Past. Innovating for the future”.
Title: 62 characters
Your title is a healthy 62 characters: “AHF | Residential, Commercial & Builder Hard Surface Solutions”.
Canonical URL set
The canonical URL is https://www.ahfproducts.com/en-us.
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.ahfproducts.com/en-us/sitemap_content.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.ahfproducts.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 (874 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.ahfproducts.com/en-us/connect.html, https://www.ahfproducts.com/en-us/our-brands.html, https://www.ahfproducts.com/en-us/newsroom.html, https://www.ahfproducts.com/en-us/newsroom/press-releases.html, https://www.ahfproducts.com/en-us/newsroom/product-awards.html and https://www.ahfproducts.com/en-us/about-us.html and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
https://www.ahfproducts.com/en-us/newsroom/press-releases.html and https://www.ahfproducts.com/en-us/about-us/history.html have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
13 distorted images
13 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
36 of 43 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,002 words of copy
The homepage carries about 1,002 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Learn More”.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Direct contact links
Visitors can reach you directly: 1 phone link 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
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.
2 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 ahfproducts.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 © 2024.
Stack
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on ahfproducts.com, including 16 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.