Smart Cup — Čaša koja razgovara
Vaš osobni AI suputnik ugrađen u toplu, utješnu čašu.
Report generated on April 6, 2026
A note on how to read this
This report is ProdPoke's take on your site — think of it as a first impression from a very opinionated robot. We check real things (load times, broken links, accessibility patterns), but we also try to understand what your site is trying to do and whether the technical details support that goal. Some of our observations might not apply to your specific situation, and that's okay. We're getting sharper with every scan. If something feels off, tell us — it makes us better.
Key Insights for Smart Cup — Čaša koja razgovara
Your 1712KB main app bundle takes 395ms to load, making the voice demo feel sluggish.
Visitors exploring Smart Cup's interactive voice conversation demo experience a delayed, unresponsive interface. For a product that emphasizes real-time AI interaction, slow loading undermines your core value proposition and increases bounce rates before users even try the demo.
Missing Open Graph tags mean your Smart Cup product page shows no image or description when shared on social media.
When potential customers share your product link on Facebook, LinkedIn, or messaging apps, platforms display a blank preview instead of your device image and compelling description. This kills social referral traffic and makes your product invisible in the feeds where early adopters discover new gadgets.
No privacy policy link exists, yet Smart Cup collects voice data—a critical trust gap for privacy-conscious buyers.
Your product's key differentiator is on-device voice processing for privacy, but customers have no way to verify your privacy claims or understand how conversational data is handled. This missing link signals unprofessionalism and raises red flags for security-conscious consumers considering an AI companion device.
One interactive element lacks an accessible name, blocking screen reader users from discovering your voice demo functionality.
Blind or low-vision users cannot understand or navigate a critical feature of your Smart Cup showcase, whether it's the voice control button or LED display toggle. This excludes an audience segment and may violate accessibility compliance expectations for a technology product.
No sitemap.xml or canonical URLs mean search engines can't efficiently index your Smart Cup pages.
Potential customers searching for 'AI smart mug' or 'voice-controlled beverage device' may not find your product because search engines lack clear crawl guidance. These are quick wins that improve discoverability for premium tech buyers actively searching for your category.
What ProdPoke understands about Smart Cup — Čaša koja razgovara
Smart Cup is an AI-powered smart mug device that combines advanced artificial intelligence with specialized hardware to function as an intelligent companion. The product features voice conversation capabilities powered by advanced language models, temperature control to keep beverages at optimal temperatures, and an expressive LED display ring that shows emotions and status through light patterns. The hardware is built on a Raspberry Pi 5 with integrated microphones, speakers, temperature sensors, and wireless connectivity, with voice processing designed to prioritize user privacy through on-device wake word detection. Users can interact with Smart Cup by speaking to it in real-time, with the device processing their words and responding naturally through the demo interface shown on the website.
Based on exploring 2 pages across the site
First Impression — How clear is your site?
Smart Cup is an AI-powered mug that functions as a personal AI assistant. According to the page, it's "not an ordinary cup — it's your personal AI companion hidden in an elegant, modern design." The device has integrated microphone, speaker, and an animated "face" that can listen, understand, and converse in real time while you drink coffee or tea. It connects via Wi-Fi to AI models and can answer questions, provide reminders, give advice, tell facts, or offer motivation.
This score measures how quickly a first-time visitor understands what your site does — based on visible headings, navigation, and visual hierarchy alone.
Overall Score
Strong foundation.
Performance
76/100Large asset: 1712KB — https://smart-cup.app/_next/static/chunks/main-app.js?v=1775
Your main app bundle is 1712KB and takes 395ms to load. This significantly slows down the interactive demo experience for visitors trying out Smart Cup's voice conversation features. Faster loading improves user engagement with the product showcase.
Found: 1712KB
Large asset: 526KB — https://smart-cup.app/_next/static/chunks/app/layout.js
The layout bundle is 526KB and takes 226ms to load. This delays the rendering of Smart Cup's interface elements and LED display demo, reducing the perceived responsiveness of your product showcase.
Found: 526KB
Large asset: 509KB — https://smart-cup.app/_next/static/chunks/app/page.js
The page bundle is 509KB and takes 219ms to load. This delays interactive elements like the voice demo and LED display visualization, making the Smart Cup product feel sluggish to potential customers exploring its capabilities.
Found: 509KB
SEO
86/100Missing Open Graph tags: og:title, og:description, og:image
When potential customers share Smart Cup's product page on social media or messaging apps, platforms like Facebook, Twitter, and LinkedIn won't display a compelling preview with the device's image and description. This hurts your ability to drive traffic from social sharing and reduces click-through rates from social channels.
Found: Missing: og:title, og:description, og:image
No canonical URL specified
Without a canonical URL, search engines may struggle to identify the primary version of your Smart Cup landing page, potentially leading to crawl inefficiencies or lower search visibility for the product.
No sitemap.xml found
A sitemap would help search engines discover and index your Smart Cup product pages more effectively, improving SEO visibility for potential customers searching for AI-powered smart devices.
Accessibility
92/1001 interactive element(s) without accessible names
One interactive element on your Smart Cup demo lacks an accessible name, meaning users with screen readers cannot understand its function. This could be a voice control button, LED demo toggle, or conversation interface element that accessibility users cannot navigate.
Found: 1 missing: <button[type=submit].text-gray-300>
Functional
100/100Compliance
99/1001 check passed
No privacy policy link found
No privacy policy link is visible on the Smart Cup website. Given that the device collects voice data and uses on-device processing, customers need clear information about how their conversational data is handled, stored, and protected.
Key Metrics
Crawlability
Standards
Improvement Plan
Your Smart Cup website has a critical performance problem that directly undermines your product experience. The three largest JavaScript bundles (main app, layout, and page) total 2.7MB and take over 800ms combined to load. Since your entire value proposition is immediate, responsive voice interaction with an AI companion, visitors are seeing a laggy, unresponsive interface before they even try your demo. This is your top priority: audit your Next.js bundle composition, implement code splitting by feature (separate bundles for voice demo, LED visualization, and conversation interface), and consider lazy-loading non-critical features. Aim to get initial interactive time below 200ms.
Your second priority is social distribution. Without Open Graph tags, every share of your Smart Cup page on LinkedIn, Facebook, or Twitter appears as a bare link with no image or description. For a device-focused product, the visual appeal is everything—add og:title, og:description, og:image (showcase the physical device or LED display), and og:url immediately. This unlocks viral potential and dramatically improves click-through rates from tech communities and early adopter forums.
Third, add a privacy policy link in your footer that explicitly explains your on-device voice processing architecture. This is your competitive advantage—but only if customers can verify it. Write a clear, concise policy that addresses how voice data is processed locally, what data never leaves the device, and what (if any) data is transmitted to your servers. This converts privacy concerns into trust, especially among the security-conscious buyers most likely to purchase an AI companion device.
Fourth, fix the unnamed interactive element blocking screen reader access. Audit your demo controls (voice button, LED toggle, conversation interface) and ensure each has a descriptive aria-label or semantic HTML element. This removes an accessibility barrier and signals professionalism to compliance-conscious enterprise buyers.
Finally, add a sitemap.xml file listing all your product pages, and specify canonical URLs on each page variant. These are low-effort, high-impact SEO foundations that help search engines discover and rank your product for high-intent keywords like 'smart mug with AI' or 'voice-controlled beverage container.'
Suggested priority order:
- Large asset: 1712KB main app bundle — optimize and code-split to reduce to <600KB
- Large assets: layout and page bundles (1035KB combined) — implement lazy loading and feature-based splitting
- Missing Open Graph tags — add og:title, og:description, og:image for social sharing
- No privacy policy link — write and link a clear policy explaining on-device voice processing
- 1 interactive element without accessible name — add aria-labels to voice demo controls and LED toggles
- No canonical URL — add canonical tags to all product pages
- No sitemap.xml — create and submit to search engines
This is your site? Get the full picture.
Claim this report to unlock ongoing monitoring, deeper analysis, and actionable alerts.
What is ProdPoke?Automated analysis generated on April 6, 2026. Not professional advice. Contact us to modify or remove this report.