johnnyslicks.com website review

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Klaviyo and others), adding 3.3 MB and 1.7 s of main-thread time.

22 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

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

Google Tag Manager costs a phone 548 ms of main-thread work and 702 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.

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

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

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

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

cloudfront.net costs a phone 291 ms of main-thread work and 522 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 229 ms of main-thread work and 540 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 204 ms of main-thread work and 689 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.

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

LoyaltyLion costs a phone 79 ms of main-thread work and 359 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 KiB could be saved by minifying CSS.

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

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.

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

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

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

reviews.svg weighs 13.4 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 8.4 MB in 420 requests on a phone: scripts 3.8 MB (195), images 2.6 MB (79) and fonts 997 KiB (12). Under 2 MB keeps phones on slow connections fast.

15 images further down the page (14.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

25 images (2.3 MB) are 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.

Merry_Slickmas_Holiday_Product_Display.png 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 is downloaded at several times the size a phone draws it, for example johnny-slicks-white-logo.svg at 400 px wide, shown at 69 px. Resized copies would save about 56 KiB.

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

Certain ARIA roles must be contained by particular parents: 6 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

Some list items are not inside a list.

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 123 pages on johnnyslicks.com and 7 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.

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

https://johnnyslicks.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “twq is not defined”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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 978 words of visible text.

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