johnny-beach.com website review

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

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

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

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

1clicklabs.io costs a phone 21 ms of main-thread work and 382 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.

7 third-party services load with your homepage (Shopify, 1clicklabs.io and esc-apps-cdn.com and others), adding 867 KiB and 231 ms of main-thread time.

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

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

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

6 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.

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW ARRIVALS”. Most of its time is element render delay (2.4 s).

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

Your homepage downloads 2.4 MB in 184 requests on a phone: other files 849 KiB (101), scripts 754 KiB (51) and images 655 KiB (20). Under 2 MB keeps phones on slow connections fast.

7qh3tz6garxmrlus8gfaqmltzbto_jpg.webp 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).

1 image (88 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

ARIA toggle fields must have an accessible name: 21 elements on the page fail this check, rated serious by axe-core.

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

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

Your title is only 12 characters: “Johnny Beach”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (MensClothingStore and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("johnny-beach.com")”.

The homepage links to 155 pages on johnny-beach.com and 10 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://johnny-beach.com/collections/clothing has no meta description, so Google writes the search snippet from whatever text it finds.

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

4 images failed to load on a phone, for example https://johnny-beach.com/.

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

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.

Social proof on the homepage: 20 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 154 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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