Website review, no card needed
madhappy.com website review
Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 86 checks
This review found 34 issues worth fixing on madhappy.com, 11 of them high impact, across 86 checks. The most urgent: main-thread work: 9.2 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84B- #18,190 of 99,948 reviewed websitesbeats 77%
- #11,510 of 54,914 online storesbeats 73%
- #11,161 of 49,854 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 240 ms |
| May 23, 2026 | 246 ms |
| May 30, 2026 | 262 ms |
| Jun 6, 2026 | 271 ms |
| Jun 13, 2026 | 286 ms |
| Jun 20, 2026 | 288 ms |
| Jun 27, 2026 | 294 ms |
| Jul 4, 2026 | 289 ms |
| Jul 11, 2026 | 289 ms |
| Jul 18, 2026 | 287 ms |
| Jul 25, 2026 | 271 ms |
| Aug 1, 2026 | 262 ms |
| Aug 8, 2026 | 260 ms |
| Aug 15, 2026 | 264 ms |
| Aug 22, 2026 | 279 ms |
| Aug 29, 2026 | 285 ms |
| Sep 5, 2026 | 272 ms |
| Sep 12, 2026 | 256 ms |
| Sep 19, 2026 | 239 ms |
| Sep 26, 2026 | 237 ms |
| Oct 3, 2026 | 244 ms |
| Oct 10, 2026 | 238 ms |
| Oct 17, 2026 | 235 ms |
| Oct 24, 2026 | 228 ms |
| Oct 31, 2026 | 219 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 6.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,264 HTML elements
The page has 6,264 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, Google Tag Manager and Clarity and others), adding 3.1 MB and 1.8 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Shopify adds 512 ms
512 msShopify costs a phone 512 ms of main-thread work and 1.1 MB 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.
Google Tag Manager adds 473 ms
473 msGoogle Tag Manager costs a phone 473 ms of main-thread work and 694 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 adds 243 ms
243 msKlaviyo costs a phone 243 ms of main-thread work and 610 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 adds 300 ms
300 msClarity costs a phone 300 ms of main-thread work and 31 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.
Use efficient cache lifetimes
283 KiB26 files are served with short cache lifetimes, so returning visitors download them again (283 KiB).
Reduce unused CSS
150 ms · 52 KiBAbout 52 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.
Minify JavaScript
150 ms · 19 KiB19 KiB could be saved by minifying JavaScript.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 150 ms. During a long task the page ignores taps.
Legacy JavaScript
84 KiBPolyfills for old browsers add 84 KiB JavaScript that modern phones do not need.
Improve image delivery
81 KiB5 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 103 ms
103 msYour server sent the HTML in 103 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 28.3 s
28.3 sThe page becomes fully interactive after 28.3 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A person stands on a beach, wearing a knitted gray bomber j…”.
Total Blocking Time: 416 ms
416 msScripts block taps and scrolling for 416 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 240 ms to 219 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 424 ms
424 msReal visitors wait 424 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 549 requests
6.0 MBYour homepage downloads 6.0 MB in 549 requests on a phone: scripts 3.2 MB (167), other files 1.6 MB (345) and images 777 KiB (22). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 202.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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 (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (24 characters)
Your title is only 24 characters: “Madhappy | Official Site”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (61 characters)
Your meta description is only 61 characters: “Madhappy is clothing for a community of optimists. Born 2017.”. 70 to 160 characters is enough to sell the click.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
225 internal links, 36 external
The homepage links to 225 pages on madhappy.com and 36 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Madhappy: Clothing for a Community of Optimists”.
Canonical URL set
The canonical URL is https://www.madhappy.com/.
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.madhappy.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,345 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.madhappy.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://www.madhappy.com/collections/special-projects, https://www.madhappy.com/collections/winter-classics, https://www.madhappy.com/collections/lucky-brand, https://www.madhappy.com/collections/t-shirts and https://www.madhappy.com/collections/sweatpants have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.madhappy.com/collections/new-arrivals, https://www.madhappy.com/collections/classics, https://www.madhappy.com/collections/favorites, https://www.madhappy.com/collections/special-projects, https://www.madhappy.com/collections/winter-classics and https://www.madhappy.com/collections/fall-classics and 9 others 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 73 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
116 small tap targets
116 of 144 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 340 words of copy
The homepage carries about 340 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “Learn More”.
22 calls to action
The homepage has 22 calls to action, for example “Contact”, “Learn More” and “Join Us”.
12 short forms
12 short forms (0 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 14 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
54 cookies set on arrival
54Opening the homepage sets 54 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.
53 other companies contacted
Loading the homepage contacts 53 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 madhappy.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Attentive · Microsoft Clarity · Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Gdpr Cookie Consent · Xapps Geo · Rivo Loyalty Rewards Referrals · 56071677a62720b5cde4241477474f626e61c35a · Back In Stock · Swym Wishlist Plus · gorgias.chat · attn.tv · global-e.com · amazonaws.com · retention.com · pdqprod.link · 9gtb.com
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
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 24 open roles
- Teams
- Retail (21), Operations & Customer Care (2), Marketing (1)
- Job board
- lever
- Careers page
- jobs.lever.co/madhappy (opens in a new tab)
Company
- Founded
- 2017
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on madhappy.com, including 15 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.