Website review, no card needed
acmerifles.com website review
Visit site (opens in a new tab)Reviewed 2 November 202632 issues · 81 checks
This review found 32 issues worth fixing on acmerifles.com, 8 of them high impact, across 81 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
79C- #53,051 of 117,615 reviewed websitesbeats 49%
- #35,157 of 66,923 online storesbeats 42%
- #274 of 884 BigCommerce storesbeats 63%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
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.9 s · 310 KiB23 files are served with short cache lifetimes, so returning visitors download them again (310 KiB).
Reduce unused JavaScript
1.6 s · 400 KiBAbout 400 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (POWr, Bigcommerce and Facebook and others), adding 1.4 MB and 1.3 s of main-thread time.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
690 ms · 81 KiBAbout 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 690 ms faster on a phone.
Render-blocking requests
550 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
POWr adds 467 ms
467 msPOWr costs a phone 467 ms of main-thread work and 13 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.
Bigcommerce adds 270 ms
270 msBigcommerce costs a phone 270 ms of main-thread work and 537 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.
Google Tag Manager adds 197 ms
197 msGoogle Tag Manager costs a phone 197 ms of main-thread work and 294 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 · 98 KiB6 images could be 98 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.
Minify JavaScript
150 ms · 37 KiB37 KiB could be saved by minifying JavaScript.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 11.3 s
11.3 sThe page becomes fully interactive after 11.3 s. Good is under 3.8 s.
Speed Index: 4.7 s
4.7 sVisually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 338 ms
338 msScripts block taps and scrolling for 338 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 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.
3 checks passed
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image in older formats
1 image (35 KiB) is 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.
About 0.5 g of CO₂ per visit
0.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.1 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: 1.7 MB in 119 requests
1.7 MBYour homepage downloads 1.7 MB in 119 requests on a phone: scripts 980 KiB (44), images 364 KiB (37) and fonts 142 KiB (3). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 59 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“ACME RIFLES”, “ACME RIFLES” and “ACME RIFLES”). One clear main headline is easier for people and search engines.
Meta description is long (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 4 problems
Structured data found (BreadcrumbList, FAQPage, Organization and Store) but with 4 problems, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 5)”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
106 internal links, 5 external
The homepage links to 106 pages on acmerifles.com and 5 external pages.
4 checks passed
Title: 63 characters
Your title is a healthy 63 characters: “ACME Rifles | Sub-MOA Guaranteed AM-15 & AM-10 Rifles | Indiana”.
Canonical URL set
The canonical URL is https://www.acmerifles.com/.
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.acmerifles.com/xmlsitemap.php.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.acmerifles.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 (880 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.acmerifles.com/compare declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.acmerifles.com/compare all use the title “ACME Rifles | Sub-MOA Guaranteed AM-15 & AM-10 Rifles | Indiana”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages without a meta description
https://www.acmerifles.com/about-us, https://www.acmerifles.com/marksmanship, https://www.acmerifles.com/our-team, https://www.acmerifles.com/terms-services, https://www.acmerifles.com/contact-us and https://www.acmerifles.com/firearms/am-pcc/pistols/lil-ruck-am-9-pcc-9mm-7-5-10-5-16-barrel-ambidextrous-controls and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.acmerifles.com/about-us has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.acmerifles.com/compare took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
2 checks passed
Tap targets are thumb-sized
21 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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.
About 469 words of copy
The homepage carries about 469 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ORDER NOW”.
8 calls to action
The homepage has 8 calls to action, for example “CONTACT US”, “Contact” and “Register”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
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.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
20 other companies contacted
Loading the homepage contacts 20 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 acmerifles.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Bigcommerce
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 acmerifles.com, including 16 speed issues, 5 SEO issues and 1 conversion gap. 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.