Your site looks fine. But a security vulnerability has been sitting unpatched for 194 days. A broken link from your paid ad campaign is converting at exactly $0. Your last deployment quietly broke something in production that staging never caught. These are the silent killers — the website problems that drain revenue without triggering a single alert. Meeky and Matt walk through the most damaging silent killers they see on real websites, what each one actually costs, and what to do about it. Over Dragon Milk Stout and Coffee. 

🍺 Featured Drinks: Meeky: Dragon Milk Stout | Matt: Coffee 

💡 WHAT WE COVER:
✅ How deployment disasters happen — and what a live site collapse actually looks like on the other side 
✅ Security monitoring: the signals worth watching vs. the noise that isn't 
✅ What's running under the hood of your site — and why 96% of WordPress vulnerabilities hide in your plugins 
✅ Why customers don't tell you when something breaks. They close the tab and buy from someone else. 
✅ The 1% performance gain that compounds into real revenue over time
✅ Broken links from paid ads: how a single bad URL turns a $10 click into $0 
✅ The 3-step process for broken links that most dev teams skip 

📊 KEY TAKEAWAYS: 
• The average breach goes undetected for 194 days — most brands find out from a customer, not their own monitoring 
• 7,966 new WordPress vulnerabilities were discovered in 2024. 96% were in third-party plugins. 
• 96% of shoppers who hit a site error never report it. They just leave. 
• A 100ms speed improvement drives 8.4% higher conversion and 9.2% higher average order value 
• Downtime costs the average e-commerce store $5,600 per minute — most brands have no real-time alert for it 
• Every click from a paid ad that lands on a broken page returns exactly $0 on that spend 

🔗 LINKS & RESOURCES: 
Boozy Browsing: https://www.boozybrowsing.com/ 
Submit your site for a free 3E audit: https://boozybrowsing.com#submit 
Matt Dorman on LinkedIn: https://www.linkedin.com/in/matthewdorman/ 
Meeky Hwang on LinkedIn: https://www.linkedin.com/in/meekyhwang

Meeky and Matt dig into the infrastructure gaps that bleed revenue from mid-market outdoor and DTC brands — not through obvious disasters, but through the quiet, daily losses nobody's measuring. Over Breakfast Stout and Not Your Father's Root Beer, they walk through eight validated pain points, the data behind each one, and what brands are doing (or not doing) about it. 

🍺 Featured Drinks: Meeky: Breakfast Stout | Matt: Not Your Father's Root Beer 

💡 WHAT WE COVER: 
✅ Why 30% of e-commerce sites crash during Black Friday — and 77% of those shoppers buy from a competitor instead 
✅ The silent customer loss problem: 96% of shoppers who hit a site error never report it. They just leave. 
✅ How 100 milliseconds of speed improvement translates to 8.4% higher conversion and 9.2% higher average order value 
✅ WordPress plugin risk in 2024: 7,966 new vulnerabilities, 96% in third-party plugins, 43% exploitable without authentication 
✅ The 194-day average time to detect a breach — and why most brands find out from their customers, not their monitoring 
✅ Why outdoor brands spend 10x more on marketing than on the infrastructure that determines whether that marketing converts 
✅ Platform fees and forced migrations: what Shopify Plus's 25% price increase and new per-transaction fees mean for brands under $10M GMV 
✅ The $260 billion cart abandonment problem — and the checkout friction that's responsible for most of it 

📊 KEY TAKEAWAYS: 
• Technical infrastructure gaps cost mid-market DTC brands 5–14% of annual revenue. For a $30M brand, that's $1.5M–$4.2M per year. 
• 88% of e-commerce brands have lost $100K or more in a single month to preventable, undetected errors 
• A 1-second load time converts at 3x the rate of a 5-second load time — not a marginal difference 
• Brands that detect breaches internally save roughly $1M compared to finding out from an attacker or a customer 
• The spend math is broken: a $20M outdoor brand typically puts $2.4M into marketing and $2,400 into hosting 

🔗 LINKS & RESOURCES: 
Boozy Browsing: https://www.boozybrowsing.com/ 
Submit your site for an audit: https://boozybrowsing.com#submit 
Matt Dorman on LinkedIn: https://www.linkedin.com/in/matthewdorman/ 
Meeky Hwang on LinkedIn: https://www.linkedin.com/in/meekyhwang

Open source won. That much is settled — 96% of commercial codebases contain open-source components, and WooCommerce still powers more e-commerce stores globally than any other platform. But winning doesn't mean you're done thinking about it. Meeky and Matt dig into what open source actually means for your business today: why Shopify's advantage over established platforms isn't technical, what the "iceberg" of a production site looks like from a developer's perspective, and how agentic software engineering is changing who gets to build — and why expertise still matters more than ever. Over Octopoda California Cabernet Franc and Coffee. 

🍺 Featured Drinks: Meeky: Octopoda California Cabernet Franc | Matt: Coffee 

💡 WHAT WE COVER:
✅ Why Shopify's real advantage over open-source platforms isn't technology — it's distribution and lock-in by design 
✅ Open source as the internet's public trail system: who maintains it, who freeloads, and why that tension matters 
✅ The iceberg effect: what's actually running under a production site that clients never see 
✅ Flexibility vs. responsibility — what you're signing up for when you go open source 
✅ Agentic software engineering: what it changes, what it doesn't, and why domain expertise isn't optional 
✅ Vibe coding is not real coding (and why that distinction is going to cost some teams dearly) 

📊 KEY TAKEAWAYS: 
• 96% of all commercial codebases contain open-source components — open source isn't an alternative anymore, it's the default 
• WooCommerce powers roughly 39% of all e-commerce sites globally; Shopify holds about 27% among the top 1 million 
• Shopify's advantage is network effects and merchant tools, not a better technology stack — that's a solvable problem if you own your data 
• The "iceberg" of a production site: caching layers, deployment pipelines, monitoring, auth systems, job queues — all invisible to the client, all load-bearing 
• Agentic dev tools raise output speed — they don't replace the judgment that keeps production sites stable 
• Vibe coding produces working demos. It doesn't produce maintainable systems. 

🔗 LINKS & RESOURCES: 
Boozy Browsing: https://www.boozybrowsing.com/ 
Submit your site for a free 3E audit: https://boozybrowsing.com#submit 
Matt Dorman on LinkedIn: https://www.linkedin.com/in/matthewdorman/ 
Meeky Hwang on LinkedIn: https://www.linkedin.com/in/meekyhwang

Episode 50. We made it. 
Meeky and Matt look back on the full run — the guests who shifted how they think, the technical disasters that became the best stories, and the AI debates that keep getting louder every year. 
This one's less structured than usual. It's a reflection. 
Pull up a drink. 

🍺 Featured Drinks: Meeky: Seaglass Sauvignon Blanc Matt: Upslope Brewing Oatmeal Stout 
💡 WHAT WE COVER: 
✅ How the podcast started vs. where episode 50 finds it 
✅ The guest appearances that changed the conversation 
✅ Technical failures that turned into the most memorable moments 
✅ Whether AI is genuinely helping developers think — or quietly replacing the thinking
 ✅ How AI is hitting a creativity ceiling and what that means for the tools we build with 
✅ Why oversight in AI usage isn't optional — it's the whole point 
✅ What the next 50 episodes look like 

📊 KEY TAKEAWAYS: 
* 44 published episodes on the road to 50 — the catalog is bigger than it feels 
* Constructive criticism is built into how Meeky and Matt approach every topic, even when it's uncomfortable 
* AI's impact on critical thinking is the sleeper issue — it compounds quietly before anyone notices 
* The hosts who stay sharp are the ones who treat AI as a starting point, not a finish line 
* Technical mishaps aren't failures — they're the episodes people remember 
* Future episodes will keep pushing on AI efficiency vs. human oversight, because that tension isn't going away 

🔗 LINKS & RESOURCES: Boozy Browsing: https://www.boozybrowsing.com/ 
Submit your site: https://boozybrowsing.com#submit 
Matt Dorman on LinkedIn: https://www.linkedin.com/in/matthewdorman/ 
Meeky Hwang on LinkedIn: https://www.linkedin.com/in/meekyhwang

Meeky and Matt audit a real local business website, covering accessibility, design consistency, competitor benchmarking, and what's holding the site back from converting visitors into customers.

💡 WHAT WE COVER:
✅ Accessibility and readability issues that cost local businesses customers
✅ Design consistency problems and how they erode user trust
✅ Competitor analysis: what the good sites in this space are doing differently
✅ Service page clarity: how to communicate what you do without making visitors work for it

📊 KEY TAKEAWAYS:
• Accessibility is both a legal consideration and a conversion driver
• Consistency in design signals professionalism to first-time visitors
• Clear service communication is more valuable than visual polish for local businesses

Meeky and Matt ditch live audits and unpack three internet-is-getting-weird trends: the Dead Internet Theory, vibe coding vs. junior developers, and whether AI agents are productivity magic or a security nightmare. Over Bourbon Barrel-aged Cabernet and Busey Brews beer, they debate whether bots are inflating engagement and whether the future of websites is built for humans or agents.

🍺 Featured Drinks:
Meeky: Cabernet Sauvignon Ménage à trois (California)
Matt: Busey Brews Smash beer

💡 WHAT WE COVER:
✅ What the Dead Internet Theory actually means (and why bot traffic is no longer fringe)
✅ Why analytics are getting dirty as AI bots behave more like real browsers
✅ The reality of vibe coding vs actually engineering production-ready systems
✅ How AI accelerates the build phase but compounds tech debt in maintenance
✅ Whether junior developers are being quietly eliminated from the pipeline

📊 KEY TAKEAWAYS:
• Bot traffic is growing fast, and engagement metrics are becoming harder to trust
• Vibe coding can ship fast but every iteration can silently add technical debt
• Prompting AI does not equal engineering systems
• Junior developers are how senior engineers are created

Meeky and Matt dig into AI-driven personalization: the marketing promise, the real implementation gap, and why a segment of one sounds great until it gets creepy. Over Meeky's Sweet Baby Jesus Porter and Matt's White River Saison, they break down why ROI stats are often misleading, why pilot purgatory happens, and what it really takes to personalize without tanking user trust.

🍺 Featured Drinks:
Meeky: Sweet Baby Jesus Porter
Matt: White River Saison (Ferment Brewing Company)

💡 WHAT WE COVER:
✅ What AI-driven personalization actually means (and why real-time is the hardest part)
✅ Why most ROI claims are marketing math
✅ Pilot purgatory and why personalization projects fail
✅ The creepy line: when personalization feels like you know too much
✅ Why you must measure trust alongside conversions
✅ The long-term risk of giving customer data to SaaS platforms

📊 KEY TAKEAWAYS:
• AI personalization only works when your data is clean, relevant, and actually usable
• 399% ROI is often ROI on the tool cost, not your revenue
• Short-term conversion wins can destroy long-term trust
• The real personalization war might happen in the LLM layer, not your website

Meeky and Matt skip the live site audits and dig into what's actually trending in dev tools. Over a Josh Cellars Sauvignon Blanc and Matt's mushroom coffee experiment, they break down why Cursor and Claude Code are blowing up, what agents actually change, why MCP is being called the USB-C of AI, and where the hype gets messy with AI washing.

🍺 Featured Drinks: Josh Cellars 2024 Sauvignon Blanc and Mushroom coffee

💡 WHAT WE COVER:
✅ Why Cursor is replacing VS Code for many developers
✅ The difference between AI chatbots vs AI agents: asking questions vs assigning tasks
✅ Why AI is still incredible at prototypes but unreliable for production code
✅ What Claude Computer Use is and why it's both exciting and risky
✅ MCP (Model Context Protocol) explained without the buzzwords
✅ AI washing and agent washing: how companies exaggerate AI-powered features

📊 KEY TAKEAWAYS:
• AI is still best for the first 40%: prototypes, exploration, getting to a working demo fast
• Vibe coding can look finished while hiding missing backend logic, security, and performance work
• MCP is a protocol layer that helps AI tools talk to each other without endless custom code
• The future of websites may split between built for humans and built for LLMs

Meeky goes solo to share a fascinating experiment: recreating her entire 2013 thesis film using AI in just 2 days. Over a 32oz Boozy Brews Citrus Smash, she breaks down why AI nailed the prototype but failed spectacularly at consistency—and how this mirrors exactly what happens with AI coding tools. Spoiler: the problems are identical.

🍺 FEATURED BEER:
Boozy Brews Citrus Smash (Nederland, CO) 

🚨 KEY TAKEAWAYS:
- AI excels at generating individual outputs but fails at maintaining consistency across iterations—characters, styles, and specifications constantly drift
- The 40% Rule: AI speeds up prototyping and exploration dramatically, but the final 60% (fine-tuning, polish, coherence) still requires human expertise
- AI doesn't fail because it's stupid—it fails because it doesn't remember previous decisions, treating every generation as a fresh remix

🎯 THE BOTTOM LINE:
Use AI to accelerate the first 40%, then human expertise takes over. The film experiment proved what developers already know from vibe coding: AI is incredible at starting projects, terrible at finishing them. This isn't a bug—it's the current limitation of how AI generates content.

#AIExperiment #AIAnimation #VibeCoding #AILimitations #FilmProduction #3DAnimation #AITools #BoozyBrowsing #ContentGeneration #AIConsistency #CreativeAI #ProductionWorkflow

Matt's eyes are completely dilated from his eye check-up, so he literally can't see—which makes him the perfect accessibility tester. Over 32oz cans of Busey Brews Milk Stout, Matt and Meeky audit websites while functionally blind, revealing how broken sites expose catastrophic backlog mismanagement. Spoiler: SSL failures and missing images aren't accidents—they're symptoms.

🍺 Featured Beer: Busey Brews Muleshoe Milk Stout https://buseybrews.com/muleshoe/

💡 WHAT WE COVER:
✅ How dilated eyes expose accessibility failures instantly
✅ SSL certificate errors = backlog chaos (guaranteed)
✅ Missing images reveal overwhelmed development teams
✅ Tiny text and poor contrast = accessibility lawsuits waiting
✅ What smooth performance tells you about internal processes
✅ Clean design = well-managed backlog (not coincidence)
✅ Broken checkout flows expose priority misalignment
✅ Simple navigation = organizational clarity
✅ How to spot backlog disasters just by browsing a site

📊 KEY TAKEAWAYS:
- You can diagnose backlog health just by browsing a website
- SSL failures mean critical tasks are being ignored
- Broken hero images = triage priority problems
- Accessibility issues = overwhelmed or misaligned teams
- Clean, simple sites = well-managed internal processes
- Getting out of backlog chaos costs less than staying in it
- Proper triage prevents small issues from becoming disasters

🔗 BONUS RESOURCE:
Watch our Media Endeavor clip on Managing Your Backlog: "Stop Being Busy, Start Being Productive" -  https://youtu.be/zAchRXUly2w

🎯 Want us to audit YOUR site and diagnose backlog issues? Submit at https://boozybrowsing.com#submit

#BacklogManagement #WebAccessibility #SSLCertificate #SiteAudit #TechnicalDebt #TriageProcess #BoozyBrowsing #QAProcess #WebDevelopment #AccessibilityTesting #DevWorkflow