Website review, no card needed

crazyaarons.com logo

crazyaarons.com website review

Visit site (opens in a new tab)Reviewed 18 October 202627 issues · 79 checks

This review found 27 issues worth fixing on crazyaarons.com, 8 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.1 s642 msApr 25Oct 10922 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.6 s
May 2, 20262.6 s
May 9, 20262.6 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.5 s
Jul 18, 20262.0 s
Jul 25, 20261.5 s
Aug 1, 20261.1 s
Aug 8, 2026976 ms
Aug 15, 2026969 ms
Aug 22, 2026977 ms
Aug 29, 2026980 ms
Sep 5, 2026975 ms
Sep 12, 2026978 ms
Sep 19, 2026965 ms
Sep 26, 2026947 ms
Oct 3, 2026942 ms
Oct 10, 2026922 ms
Real-visitor tap response (INP)75th percentile, phones
118 ms93 msApr 25Oct 10104 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202696 ms
May 2, 202696 ms
May 9, 202696 ms
May 16, 202697 ms
May 23, 202699 ms
May 30, 2026104 ms
Jun 6, 2026106 ms
Jun 13, 2026112 ms
Jun 20, 2026113 ms
Jun 27, 2026114 ms
Jul 4, 2026115 ms
Jul 11, 2026112 ms
Jul 18, 2026108 ms
Jul 25, 2026105 ms
Aug 1, 2026104 ms
Aug 8, 2026103 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026104 ms
Sep 5, 2026103 ms
Sep 12, 2026103 ms
Sep 19, 2026103 ms
Sep 26, 2026103 ms
Oct 3, 2026104 ms
Oct 10, 2026104 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of crazyaarons.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crazyaarons.com at 0.4 s0.4 s
  2. crazyaarons.com at 0.8 s0.8 s
  3. crazyaarons.com at 1.1 s1.1 s
  4. crazyaarons.com at 1.5 s1.5 s
  5. crazyaarons.com at 1.9 s1.9 s
  6. crazyaarons.com at 2.3 s2.3 s
  7. crazyaarons.com at 2.6 s2.6 s
  8. crazyaarons.com at 3.0 s3.0 s

Speed

5 to fix70
  • Render-blocking requests

    1.1 s

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

  • 4,371 HTML elements

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

  • Improve image delivery

    500 ms · 1.1 MB

    30 images could be 1.1 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.

  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70 (desktop: 83). Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 3.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (smile.io, Shopify and Bugsnag and others), adding 387 KiB and 205 ms of main-thread time.

  • 10 long tasks on the main thread

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

  • Reduce unused JavaScript

    65 KiB

    About 65 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    52 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 7.4 s

    7.4 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • Tap response (INP) held steady for real visitors

    +8%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 112 ms

    112 ms

    Real visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 420 ms

    420 ms

    Real visitors wait 420 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 64% faster for real visitors

    -64%

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

  • Total Blocking Time: 140 ms

    140 ms

    Scripts block the page for only 140 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 4.2 MB in 280 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 280 requests on a phone: images 2.6 MB (54), other files 763 KiB (99) and scripts 551 KiB (73). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    AMZN_TreasureHunt_theme.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).

  • 2 images far larger than shown

    108 KiB

    2 images are downloaded at several times the size a phone draws them, for example 01.1-treasure-trove-mega-tin-thinking-putty-main.jpg at 342 px wide, shown at 22 px. Resized copies would save about 108 KiB.

  • 3 images in older formats

    3 images (266 KiB) 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.

  • About 1.2 g of CO₂ per visit

    1.20 g

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

Accessibility

6 to fixGoogle 8793
  • 25 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (3 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 6 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 55 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8581
  • Title is short (28 characters)

    Your title is only 28 characters: “Crazy Aaron's Thinking Putty”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (258 characters)

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

  • 10 links with vague text

    10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 246 internal links, 10 external

    The homepage links to 246 pages on crazyaarons.com and 10 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.crazyaarons.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.crazyaarons.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,564 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.crazyaarons.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 14 pages without a meta description

    https://www.crazyaarons.com/collections/thinking-putty, https://www.crazyaarons.com/collections/liquid-glass-putty-copy, https://www.crazyaarons.com/collections/mini-tins-of-thinking-putty, https://www.crazyaarons.com/collections/full-size-tins, https://www.crazyaarons.com/collections/mega-tins-of-thinking-putty and https://www.crazyaarons.com/collections/liquid-glass-putty and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 28 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: “Trusted by 365,000+ Customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • About 507 words of copy

    The homepage carries about 507 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop All”, “Shop Now” and “Contact Us”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at crazyaarons.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on crazyaarons.com, including 9 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25