jaxwax.com website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

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

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

8 third-party services load with your homepage (kangarooapis.com, rebuyengine.com and Shopify and others), adding 3.2 MB and 783 ms of main-thread time.

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

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

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

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

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

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

rebuyengine.com costs a phone 150 ms of main-thread work and 666 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.

kangarooapis.com costs a phone 157 ms of main-thread work and 545 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.

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

emotivecdn.io costs a phone 111 ms of main-thread work and 384 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.

Klaviyo costs a phone 95 ms of main-thread work and 312 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.

Polyfills for old browsers add 60 KiB JavaScript that modern phones do not need.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

22 KiB could be saved by minifying CSS.

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 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

11 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.3 MB in 379 requests on a phone: scripts 2.9 MB (148), images 2.7 MB (45) and other files 965 KiB (148). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example cart_icon_black_official_a1b12dfc-e7e9-46e0-9d4e-1cc89dd52f2 at 2,750 px wide, shown at 37 px. Resized copies would save about 95 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

1 image has no alt text, which hurts accessibility and image search.

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 131 pages on jaxwax.com and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

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

https://www.jaxwax.com/customer_authentication/redirect, https://www.jaxwax.com/collections/wax-sealants, https://www.jaxwax.com/collections/wheel-tire-care, https://www.jaxwax.com/collections/soaps-cleaners, https://www.jaxwax.com/collections/spray-detailers and https://www.jaxwax.com/collections/ceramics and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jaxwax.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

Chrome logged issues while loading the page (“Cookie”).

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 300 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 21 cookies, 3 of them by other companies (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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.