American Shooters
Site Audit & Recommendations

Elementor generates deeply nested HTML with hundreds of wrapper divs, inline style attributes, and widget-specific CSS/JS loaded on every page regardless of use. This directly inflates page weight, increases browser parse time, and causes Core Web Vitals failures — particularly LCP (Largest Contentful Paint) and CLS (Cumulative Layout Shift).

A typical Elementor homepage contains 4–8× the DOM node count of a hand-coded equivalent. For a booking-driven business, every second of load time on mobile costs an estimated 7–10% in conversion rate.

• Estimated page weight: 3.5–6MB (images + scripts + styles)
• Probable mobile LCP: 5–9 seconds on mid-tier Android
• Google PageSpeed Insights mobile score: likely 15–35

WP Rocket is a band-aid over a structural problem. It can cache static HTML and defer some scripts, but it cannot remove Elementor's fundamental overhead, reduce the plugin ecosystem weight, or eliminate render-blocking resources injected by third-party widgets.

• Admin bar visible to logged-out users indicates WP Rocket cache may not be firing correctly, or is misconfigured to exclude certain URL patterns
• Plugin conflicts common between Rocket + Imagify + FareHarbor widget scripts

The WordPress admin toolbar is rendering for logged-out users — this is a security misconfiguration that exposes the CMS type, version hints, and login endpoints to the public. It also pushes page content down by 32px, creating layout shifts and eating into the hero visual area.

• Security risk: confirms CMS is WordPress, making the site a target for automated WP vulnerability scanners
• UX impact: 32px of wasted screen real estate above the fold on desktop
• CLS impact: admin bar loads after initial paint, causing layout shift

FareHarbor's booking widget loads in an iframe from a different domain (fareharbor.com). Standard Google Analytics and Meta Pixel tracking does not cross iframe boundaries. This means that when a user completes a booking, that conversion is almost certainly not being recorded — or if it is, it's being attributed to FareHarbor's domain, not americanshooters.com.

The practical consequence: if you're running Google or Meta ads, your reporting shows zero or near-zero conversions even when real bookings are being made. This leads to incorrect campaign optimization, wasted budget on mis-attributed spend, and no ability to calculate true ROAS.

• FareHarbor does offer a postMessage API and/or server-side webhook for tracking — these must be configured manually
• Google Ads conversion tags need to fire on booking confirmation, not on button click
• Meta Pixel purchase events need to fire with actual booking value passed through

A common and costly mistake in booking-site tracking: the Meta Pixel Purchase event fires when a user clicks the booking button — not when they actually complete the transaction. This inflates "conversion" counts, corrupts lookalike audiences built on that data, and makes ROAS calculations completely unreliable.

Real-world consequence: an account might report $8 ROAS on Meta ads while the actual revenue from completed bookings is negative after ad spend. This is impossible to detect without server-side verification.

• Pixel should fire Purchase event only on booking confirmation page or via FareHarbor webhook
• Purchase event must include value (actual booking amount) and currency parameters
• Deduplicate events using Conversions API + browser Pixel to avoid double-counting

Without consistent UTM tagging on all paid and organic link sources, it's impossible to attribute bookings to specific campaigns, ad sets, or channels in GA4. This means budget allocation decisions are made on incomplete data.

• All paid ads (Google, Meta) should use UTM source, medium, campaign, content parameters
• Google Ads auto-tagging (gclid) should be enabled and verified
• GA4 → Advertising → Attribution report should show last-click and data-driven models

The current nav presents users with too many choices at once, which research consistently shows reduces click-through rates on primary CTAs. A gun range website has one primary conversion goal: get the visitor to book. Every additional nav item dilutes that intent.

• Current approximate nav items: Home, About, Packages, Events, Membership, Firearms, Gallery, Contact, Book Now
• Recommendation: 4–5 items maximum — About, Packages, Events, Contact — with a high-contrast "Book Now" button isolated in the nav rail
• Secondary content (Membership, Firearms info, Gallery) should live as page sections, not top-level nav items

A floating chat widget (observed in the bottom-right corner) is overlapping key page content on mobile viewport widths. For a booking business where the "Book Now" button is the primary CTA, any element obscuring that button is directly costing conversions.

• Mobile users represent 65–75% of traffic for entertainment/leisure businesses in Las Vegas
• Chat widget should be auto-minimized on mobile until user explicitly opens it
• Consider replacing live chat (high maintenance overhead for a gun range) with a simple "Call Us" or "Email Us" sticky button

The packages page lists all options at equal visual weight with no "recommended" or "most popular" indicator. Pricing psychology research shows that featuring one option prominently (with a visual callout) increases average order value by 15–35% — users anchor to the featured option and either buy it or compare up or down from it.

• Pick Your Poison ($170) or Allied ($190) are natural candidates to feature as "Most Popular" or "Best Value"
• Add short, benefit-driven descriptions to each package rather than listing items neutrally
• Include a "Not sure? Build your experience →" CTA that routes to a contact/consultation form

American Shooters has excellent reviews — but they're buried. For a Las Vegas entertainment business competing in a crowded market, social proof in the first visible viewport is a conversion multiplier. A visitor who sees "★★★★★ 4.8/5 — 2,400+ reviews" immediately before clicking "Book Now" is significantly more likely to complete the booking.

• Add a review count + star rating directly in the hero section, below the headline
• Pull 2–3 short review quotes into the page near the booking CTA
• Consider a TripAdvisor or Google Reviews widget for dynamic social proof

Since Google's Page Experience update, Core Web Vitals (LCP, CLS, INP) are a ranking factor. A site with an Elementor build and no systematic performance optimization is almost certainly failing LCP on mobile — which means Google is actively suppressing organic rankings for competitive queries like "Las Vegas gun range" and "shooting range Las Vegas."

• Run Google Search Console → Core Web Vitals report to confirm current status
• Run PageSpeed Insights (pagespeed.web.dev) on homepage and /packages page
• Expected findings: LCP > 4s (failing), CLS likely elevated due to Elementor widgets loading async

For a local Las Vegas business, structured data (Schema.org) is a significant ranking lever that most competitors skip. LocalBusiness schema with opening hours, geo coordinates, price range, and review aggregate helps Google understand and surface the business in local packs and "near me" searches.

• Add LocalBusiness + SportsActivityLocation schema to homepage
• Add openingHoursSpecification with all operating hours
• Add aggregateRating with review count and rating value
• Add geo coordinates for Google Maps integration
• Add hasMap link to Google Maps listing

The most valuable search queries for a booking business are transactional — "book gun range Las Vegas," "shooting range Las Vegas packages," "indoor gun range Las Vegas." Current title tags likely default to the site name without keyword optimization for these high-intent terms.

• Homepage title: "Indoor Shooting Range Las Vegas | Book Your Experience — American Shooters"
• Packages page title: "Shooting Range Packages Las Vegas | From $100 — American Shooters"
• Each meta description should include a clear benefit + CTA: "21 lanes, all levels welcome. Packages from $100. Book online in 2 minutes."

The current site uses a dated gold/brown/white color scheme with significant white-background sections that undercut the tactical, premium, veteran-owned brand identity. Competitors in the Las Vegas entertainment market (escape rooms, axe throwing, racing experiences) are investing heavily in immersive dark-mode aesthetics that make their experiences feel premium and exciting in the browser before the customer ever arrives in person.

American Shooters has a genuinely compelling story — veteran-operated, 21 lanes, serious equipment, unmatched local expertise — but the website doesn't communicate any of that visually. A visitor comparing this site to a competitor with modern dark design may unconsciously perceive the competitor as higher-quality, even if the reverse is true.

• The demo at nicespaceship.com/americanshooters demonstrates what the site could look like with near-black backgrounds, gold accent typography (#c9a84c), red CTAs (#cc2127), and Rajdhani typography — all evoking precision, quality, and tactical authority

The site mixes professional facility photography with lower-quality images and possible stock photography. For a premium experiential brand, every image needs to communicate quality, safety, and excitement. A visitor's first impression is formed in under 50ms — primarily through imagery.

• Invest in a half-day professional photography session — real customers, real instructors, real lanes in action
• Hero image should show the facility at its best with clear depth and activity (not just static equipment)
• Package pages benefit from images showing the specific experience of that package
• Optimize all images: WebP format, correct dimensions, lazy loading for below-fold images

Elementor builds are typically designed desktop-first and then awkwardly adapted to mobile. For a Las Vegas attraction where 70%+ of visitors are discovering the business on a mobile device (often while already in the area), the mobile experience is arguably more important than desktop.

Key mobile-specific issues to audit:

• Hero section layout on 375px viewport width — is the CTA button immediately visible without scrolling?
• Touch target sizes — buttons should be minimum 44px tall per Apple/Google guidelines
• Font legibility — Elementor sometimes collapses font sizes in ways that make body copy unreadable on mobile
• FareHarbor booking widget — is the entire booking flow functional on a mobile keyboard?
• Phone number and address should be tappable (tel: and maps: deep links)

Las Vegas visitors make impulse decisions. A significant portion of potential customers will want to call rather than book online — especially for group bookings, corporate events, or custom experiences. A prominent click-to-call button on mobile nav or as a sticky floating CTA would capture this segment.

• Add click-to-call button to mobile nav (<a href="tel:+17028000000">)
• Consider a sticky bottom bar on mobile: [📞 Call] [📅 Book] — two equal CTAs
• Track call clicks as conversions in GA4 and Google Ads