colsonjoe.com website review

About 399 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

The page goes through 1 redirect before it starts loading, costing about 3.3 s. Link and advertise the final URL directly.

45 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Yotpo and Other Google APIs/SDKs and others), adding 817 KiB and 282 ms of main-thread time.

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

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

6 KiB could be saved by minifying JavaScript.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

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 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hands tying a ribbon around a stack of gift boxes from Plat…”.

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

Visually, the page fills in at 8.5 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.

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

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

Your homepage downloads 5.3 MB in 323 requests on a phone: images 2.7 MB (77), scripts 1.2 MB (86) and other files 938 KiB (128). Under 2 MB keeps phones on slow connections fast.

8 images further down the page (201 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 1.49 g of CO₂e: 178.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: 16 elements on the page fail this check, rated critical by axe-core.

2 buttons have no accessible name, so screen readers announce just “button”.

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

<svg> elements with an img or image role must have alternative text: 11 elements on the page fail this check, rated serious by axe-core.

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

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

3 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 and h2 → h4), which makes the page harder to scan with a screen reader.

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

The homepage links to 255 pages on colsonjoe.com and 11 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56032622&Ver=2&mid=26d8a583-4d25-41bf-a1e8-a57a6e614de1&bo=1&sid=a817daf0df8111f18bc4a57b4b39284f&vid=a8182910df8111f1be823921e5d2695a&vids=1&msclkid=N&pi=918639831&lg.

6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cratejoy.cloudflareaccess.com/cdn-cgi/access/login/stats.cratejoy.com?kid=982387fa…”.

Large scripts ship without source maps.

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

The homepage carries about 1,293 words of visible text.

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