apexxbows.com website review

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

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

13 images could be 280 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

The page has 1,870 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 112 ms of main-thread work and 607 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.

6 third-party services load with your homepage (Shopify, Google CDN and edgecdn.dev and others), adding 708 KiB and 180 ms of main-thread time.

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

About 22 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

5 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

The first text or image appears after 2.4 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.

Your homepage downloads 8.7 MB in 330 requests on a phone: media 5.6 MB (1), images 1.2 MB (39) and other files 876 KiB (139). Under 2 MB keeps phones on slow connections fast.

homepage-video-fallback.jpg 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).

8 images further down the page (419 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.

Elements must only use permitted ARIA attributes: 9 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

22 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

8 visible links have no text or label, so screen readers cannot say where they go.

There are 2 <h1> headlines (“” and “Elevate your archery experience”). One clear main headline is easier for people and search engines.

Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 59 pages on apexxbows.com and 4 external pages.

https://apexxbows.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://apexxbows.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://apexxbows.com/products/apexx-predator-bow and https://apexxbows.com/products/2023-apexx-predator-one all use the title “APEXX PREDATOR BOW – Apexx Bows”. Search engines can't tell which page to show for a search, so each competes with the others.

https://apexxbows.com/pages/about-apexx, https://apexxbows.com/customer_authentication/redirect, https://apexxbows.com/pages/customer-gallery, https://apexxbows.com/collections/apparel-accessories, https://apexxbows.com/pages/contact and https://apexxbows.com/pages/returns-warranty and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://apexxbows.com/products/apexx-predator-bow and https://apexxbows.com/products/2023-apexx-predator-one use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://apexxbows.com/products/apexx-predator-bow, whose canonical is https://apexxbows.com/products/2023-apexx-predator-one. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://apexxbows.com/pages/about-apexx, https://apexxbows.com/customer_authentication/redirect and https://apexxbows.com/pages/customer-gallery have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is served at too low a resolution for sharp phone screens.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 carries about 607 words of visible text.

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.