Website review, no card needed
acehardware.af website review
Visit site (opens in a new tab)Reviewed 18 October 202636 issues · 78 checks
This review found 36 issues worth fixing on acehardware.af, 14 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
66DClosest competitors among reviewed websites
Compare side by sideOne 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
Render-blocking requests
3.7 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.7 s.
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 80). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
580 ms · 878 KiBAbout 878 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 580 ms faster on a phone.
Reduce unused CSS
900 ms · 193 KiBAbout 193 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 451 ms. During a long task the page ignores taps.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Google Tag Manager adds 171 ms
171 msGoogle Tag Manager costs a phone 171 ms of main-thread work and 306 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics and others), adding 389 KiB and 171 ms of main-thread time.
Minify CSS
150 ms · 15 KiB15 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
39 KiB5 files are served with short cache lifetimes, so returning visitors download them again (39 KiB).
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 80 but mobile only 47. A gap that wide usually means heavy scripts and images that hit phones hardest.
Improve image delivery
8 KiB1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 441 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.281
0.281The layout shifts by 0.281 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 272 ms
272 msScripts block taps and scrolling for 272 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 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.
Images and page weight
An image on the first screen is lazy-loaded
ace new.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.6 g of CO₂ per visit
0.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 66.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 2.0 MB in 26 requests
2.0 MBYour homepage downloads 2.0 MB in 26 requests on a phone: scripts 1.6 MB (7), stylesheets 209 KiB (2) and fonts 134 KiB (3). That is a lean page.
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
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
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), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
42 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: 42 passed and 5 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.
Title is short (19 characters)
Your title is only 19 characters: “main | ACE Hardware”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “Welcome to our group of companies”). One clear main headline is easier for people and search engines.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
35 internal links, 14 external
The homepage links to 35 pages on acehardware.af and 14 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.acehardware.af/main.
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.acehardware.af/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. 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.acehardware.af/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.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://www.acehardware.af/website/social/github, which answers with an error. Visitors hit a dead end and search engines drop it.
2 linked pages hidden from search
https://www.acehardware.af/ace-hardware and https://www.acehardware.af/https/acehardwareintl-com are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
3 pages share a title
/, https://www.acehardware.af/main and https://www.acehardware.af/fa_IR/main all use the title “main | ACE Hardware”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://www.acehardware.af/shop, https://www.acehardware.af/https/acehardwareintl-com, https://www.acehardware.af/contactus, https://www.acehardware.af/event, https://www.acehardware.af/about and https://www.acehardware.af/shop/wishlist and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.acehardware.af/ace-hardware and https://www.acehardware.af/about have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://www.acehardware.af/contactus, https://www.acehardware.af/event, https://www.acehardware.af/shop/wishlist, https://www.acehardware.af/main, https://www.acehardware.af/fa_IR/main and https://www.acehardware.af/website/social/twitter 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.
2 pages slow to respond
https://www.acehardware.af/shop and https://www.acehardware.af/website/social/twitter took over 3 s to send their HTML from our server.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
2 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 45 words
The homepage has only about 45 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Shop Products”, “Contact Us” and “Get in touch”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Umami.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
5 other companies contacted
Loading the homepage contacts 5 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 acehardware.af, 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 36 issues on acehardware.af, including 14 speed issues, 3 SEO issues and 4 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.