communityaxe.com website review

Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

A phone's processor spends 3.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

6 third-party services load with your homepage (Shopify, staq-cdn.com and cloudfront.net and others), adding 360 KiB and 298 ms of main-thread time.

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

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

4 images could be 35 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

5 files are served with short cache lifetimes, so returning visitors download them again (11 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “two humans tapping axes”.

Scripts block taps and scrolling for 611 ms in total while the page loads. Good is under 200 ms.

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

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

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

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.

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

9 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: 4 elements on the page fail this check, rated moderate by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 22 characters: “Community Axe Throwing”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 17 pages on communityaxe.com and 1 external page.

/products/booster-battle-1 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.

/ and /products/booster-battle-1 all use the title “Community Axe Throwing”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/leagues, /pages/waiver, /products/booster-battle-1, /policies/privacy-policy and /policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 7 pages linked from your homepage and read each the way a search engine does.

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 ()”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

communityaxe.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

communityaxe.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

communityaxe.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 131 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

communityaxe.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be communityaxe.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 7 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.