cratejoy.com website review

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

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

Google Tag Manager costs a phone 1.7 s of main-thread work and 652 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Yotpo and others), adding 1.6 MB and 4.5 s of main-thread time.

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

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

Shopify costs a phone 802 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.

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

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

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

Clarity costs a phone 290 ms of main-thread work and 28 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.

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

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

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

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

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

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

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

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

Your largest element takes 6.4 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…”.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 159 ms to 192 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.

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

Your homepage downloads 7.4 MB in 288 requests on a phone: images 4.3 MB (58), scripts 1.9 MB (93) and other files 819 KiB (112). Under 2 MB keeps phones on slow connections fast.

14 images are downloaded at several times the size a phone draws them, for example DDftxsrNRFCno2YDe4cY at 1,200 px wide, shown at 267 px. Resized copies would save about 1.6 MB.

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

1 image (37 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.

By the Sustainable Web Design model, a visit to your homepage emits about 2.11 g of CO₂e: 252.7 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”.

17 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 (h1 → 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 237 pages on cratejoy.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.

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

We fetched 15 pages linked from your homepage (of 143 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=9a93df9a-17bc-4473-9af0-4fa4c852825e&bo=1&sid=68b47c30d87511f1a19717cdf6edbf44&vid=68b49cc0d87511f1861adbaf383167f4&vids=1&msclkid=N&pi=918639831&lg.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

cratejoy.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

DMARC is set to p=none, so mail pretending to be cratejoy.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 32 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 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.