Website review, no card needed

crazyshirts.com logo

crazyshirts.com website review

Visit site (opens in a new tab)Reviewed 9 November 202637 issues · 90 checks

This review found 37 issues worth fixing on crazyshirts.com, 12 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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.2 s1.4 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.0 s
May 23, 20262.8 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
223 ms116 msMay 16Oct 31128 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026211 ms
May 23, 2026204 ms
May 30, 2026171 ms
Jun 6, 2026171 ms
Jun 13, 2026170 ms
Jun 20, 2026168 ms
Jun 27, 2026163 ms
Jul 4, 2026163 ms
Jul 11, 2026164 ms
Jul 18, 2026171 ms
Jul 25, 2026178 ms
Aug 1, 2026180 ms
Aug 8, 2026187 ms
Aug 15, 2026186 ms
Aug 22, 2026180 ms
Aug 29, 2026175 ms
Sep 5, 2026167 ms
Sep 12, 2026169 ms
Sep 19, 2026171 ms
Sep 26, 2026170 ms
Oct 3, 2026165 ms
Oct 10, 2026154 ms
Oct 17, 2026137 ms
Oct 24, 2026128 ms
Oct 31, 2026128 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 crazyshirts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crazyshirts.com at 4.1 s4.1 s
  2. crazyshirts.com at 8.2 s8.2 s
  3. crazyshirts.com at 12.4 s12.4 s
  4. crazyshirts.com at 16.5 s16.5 s
  5. crazyshirts.com at 20.6 s20.6 s
  6. crazyshirts.com at 24.7 s24.7 s
  7. crazyshirts.com at 28.8 s28.8 s
  8. crazyshirts.com at 33.0 s33.0 s

Speed

14 to fix39
  • Reduce unused JavaScript

    3.8 s · 1,004 KiB

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

  • Improve image delivery

    1.0 s · 621 KiB

    13 images could be 621 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 7.5 s

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

  • 3,945 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 2.4 MB and 1.6 s of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 106 KiB

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

  • Minify JavaScript

    450 ms · 107 KiB

    107 KiB could be saved by minifying JavaScript.

  • Shopify adds 394 ms

    394 ms

    Shopify costs a phone 394 ms of main-thread work and 1,015 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.

  • Duplicated JavaScript

    350 ms · 59 KiB

    59 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.

  • Clarity adds 305 ms

    305 ms

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

  • Render-blocking requests

    300 ms

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

  • Klaviyo adds 237 ms

    237 ms

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

  • zoom.us adds 122 ms

    122 ms

    zoom.us costs a phone 122 ms of main-thread work and 402 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.

  • Reduce unused CSS

    170 ms · 55 KiB

    About 55 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.

  • 17 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 59 KiB

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

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

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 44.0 s

    44.0 s

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

  • Speed Index: 20.5 s

    20.5 s

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

  • Time to Interactive: 44.4 s

    44.4 s

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

  • Cumulative Layout Shift: 0.215

    0.215

    The layout shifts by 0.215 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 458 ms

    458 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

8 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: 2.3 s

    2.3 s

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

  • Real-user INP: 135 ms

    135 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 783 ms

    783 ms

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

  • Tap response (INP) got 38% faster for real visitors

    -38%

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

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

    -46%

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

Images and page weight

2 to fix64
  • Page weight: 10.3 MB in 524 requests

    10.3 MB

    Your homepage downloads 10.3 MB in 524 requests on a phone: images 3.2 MB (47), fonts 3.1 MB (5) and scripts 2.3 MB (148). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    2800x1000_Desktop_dac9edbf-5d78-45d4-bc9c-341d109a519e.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).

  • About 2.9 g of CO₂ per visit

    2.93 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8992
  • 5 tap targets too small

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

  • <svg> elements with an img or image role must have alternative text (2 elements)

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

  • 2 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (15 elements)

    ARIA role should be appropriate for the element: 15 elements on the page fail this check, rated minor by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Headings skip levels

    Headings skip levels (h1 → h4 and h2 → h6), 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. (1 element).

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • Meta description is long (280 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 638 internal links, 16 external

    The homepage links to 638 pages on crazyshirts.com and 16 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Crazy Shirts”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Crazy Shirts | Memorable artwork on quality products since 1964!”.

  • Canonical URL set

    The canonical URL is https://crazyshirts.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://crazyshirts.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 (2,308 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://crazyshirts.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://crazyshirts.com/collections/long-sleeve-pants-sale, https://crazyshirts.com/collections/heroes-collection, https://crazyshirts.com/collections/mens-apparel-just-in and https://crazyshirts.com/collections/collaborations have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 7785
  • 6 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static-recommendations.fastsimon.com/no-code-recommendations/style.css?v=1.0.492-0…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Local business without LocalBusiness data

    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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 422 words of copy

    The homepage carries about 422 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP MEN'S” and “SHOP WOMEN'S”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “SHOP NOW”, “Start shopping” and “SHOP MEN'S”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks, 7 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

  • 35 other companies contacted

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

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 crazyshirts.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Judge Me Reviews · Sc Easy Redirects · Klaviyo Email Marketing Sms · Gsc Countdown Timer · Optimonk Popup Cro A B Test · Pagefly Ai Page Builder · Aimerce First Party Pixel · Instant Ai Page Builder · Product Filters Search · Monk Free Gift With Purchase · Gdpr Backpack · Page Speed Optimizer · nfcube.com · rakutenadvertising.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
SvelteKit
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
1 open role
Job board
smartrecruiters

Company

Employees
230
Founded
1964
Headquarters
Honolulu

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on crazyshirts.com, including 20 speed issues, 2 SEO issues and 1 conversion gap. 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