joandjax.com website review

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

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

8 third-party services load with your homepage (Yotpo, rebuyengine.com and Shopify and others), adding 2.6 MB and 1.3 s of main-thread time.

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

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

About 801 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.

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

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

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

Yotpo costs a phone 429 ms of main-thread work and 459 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.

rebuyengine.com costs a phone 307 ms of main-thread work and 665 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 253 ms of main-thread work and 365 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 167 ms of main-thread work and 311 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.

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

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

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

About 43 KiB of CSS is downloaded but never applied on this page.

39 KiB could be saved by minifying JavaScript.

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.

2 KiB could be saved by minifying CSS.

Your largest element takes 13.5 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 27.2 s. Good is under 3.8 s.

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

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

3 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 157 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.1 MB in 367 requests on a phone: images 2.7 MB (42), scripts 2.0 MB (128) and other files 825 KiB (123). Under 2 MB keeps phones on slow connections fast.

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

50 form fields have no label, so screen readers announce an empty box and autofill guesses.

Your meta description is 235 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.

No XML sitemap at https://www.joandjax.com/sitemap.xml, so Google discovers your pages only by following links.

Your <h1> is empty.

The homepage links to 143 pages on joandjax.com and 12 external pages.

There is no https://www.joandjax.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.

15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

6 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

3 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Yotpo Loyalty SDK loader script already loaded”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

The homepage carries about 410 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo (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 17 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.