Skip to main content

Device & Technology Analytics

The Devices section reveals the technology your visitors use to access your site - from device types to browsers and operating systems. This information is crucial for ensuring your site works perfectly for your actual audience.

Three-Level Breakdown​

Ovyxa organizes technology data in a hierarchical three-level drill-down:

Device Types → Browsers → Operating Systems

This structure lets you explore progressively deeper: start with broad device categories, then narrow down to specific browsers, and finally examine operating systems.

Device Types​

The first level shows three main device categories:

Desktop 💻​

Traditional computers including laptops, desktops, and workstations.

Typical patterns:

  • Higher on B2B/SaaS sites (40-70%)
  • Work hours traffic spikes
  • Longer session durations
  • More pageviews per visit

What it means: Desktop visitors often have more time and screen space for detailed exploration. If desktop dominates, prioritize desktop-optimized layouts for complex tasks.

Mobile 📱​

Smartphones of all sizes running iOS, Android, or other mobile operating systems.

Typical patterns:

  • Higher on consumer/content sites (50-80%)
  • Evening and weekend traffic spikes
  • Shorter sessions
  • Higher bounce rates

What it means: Mobile-first visitors want speed and simplicity. If mobile dominates, ensure fast loading, large touch targets, and streamlined navigation.

Tablet 📱​

iPads, Android tablets, and other tablet devices.

Typical patterns:

  • Usually 5-15% of total traffic
  • Similar behavior to desktop (longer sessions)
  • Often used for leisure browsing

What it means: Tablets blend desktop and mobile characteristics. They typically use mobile layouts but have more screen space.

Click to Drill Down​

Click any device type to see which browsers are used on that device type. For example:

  • Click "Mobile" → see Safari, Chrome Mobile, Samsung Internet breakdown
  • Click "Desktop" → see Chrome, Firefox, Safari, Edge breakdown

Browsers​

The second level shows specific browser applications:

Common Browsers​

  • Chrome - Google Chrome (desktop and mobile)
  • Safari - Apple Safari (macOS, iOS, iPadOS)
  • Firefox - Mozilla Firefox
  • Edge - Microsoft Edge
  • Samsung Internet - Pre-installed browser on Samsung devices
  • Opera - Opera browser
  • Brave - Privacy-focused Chromium browser

What the data tells you:

If you see 80% Chrome/Safari/Edge (Chromium-based browsers), modern web features are safe to use. If Firefox or older browsers represent significant traffic, test compatibility carefully.

Click to Drill Down​

Click any browser to filter the dashboard to visitors using that browser, then check Operating Systems to see the OS distribution for that browser.

Operating Systems​

The third level shows the operating systems your visitors run:

Common Operating Systems​

  • Windows - Various Windows versions (10, 11, etc.)
  • macOS - Apple desktop operating system
  • iOS - Apple mobile operating system (iPhone, iPad)
  • Android - Google mobile operating system
  • Linux - Various Linux distributions
  • Chrome OS - Chromebook operating system

What the data tells you:

  • High iOS percentage suggests affluent audience (premium devices)
  • Android dominance indicates broader demographic
  • Linux visitors might be developers or tech enthusiasts
  • Windows/macOS split reveals professional/creative audience balance

Privacy-First Detection​

Ovyxa determines device information by parsing the User-Agent string that browsers send with every request:

What we collect:

  • Device family (desktop/mobile/tablet)
  • Browser family (Chrome, Safari, Firefox, etc.)
  • Operating system family (Windows, macOS, iOS, Android, etc.)

What we don't collect:

  • Specific device models (iPhone 15 Pro vs. iPhone 12)
  • Exact version numbers (beyond major versions)
  • Screen resolution or pixel density
  • Any fingerprinting data (canvas, fonts, WebGL)

The User-Agent is parsed on the server, categorized into broad families, and the raw string is discarded. This provides useful insights while maintaining privacy.

Use Cases​

Optimize for Your Audience​

If 70% of your traffic is mobile, but your site loads slowly on mobile devices, you're losing most of your potential audience. Prioritize optimization for your dominant device type.

Action items:

  • Desktop-heavy → optimize for productivity features, keyboard shortcuts, multi-column layouts
  • Mobile-heavy → optimize loading speed, touch targets, vertical scrolling

Browser Testing Priorities​

Focus testing efforts on browsers your audience actually uses.

Example: If your data shows:

  • Chrome: 60%
  • Safari: 25%
  • Firefox: 10%
  • Edge: 5%

Test thoroughly in Chrome and Safari first. Firefox and Edge get secondary priority.

Detect Technical Issues​

Sudden changes in device distribution might indicate problems:

Warning signs:

  • Mobile traffic drops 50% overnight → mobile site broken?
  • Specific browser disappears from stats → browser compatibility issue?
  • Unusual OS showing high traffic → bot traffic?

Responsive Design Validation​

Filter by device type and check bounce rates:

Questions to answer:

  • Is mobile bounce rate 20% higher than desktop? (mobile UX problem)
  • Do tablet users behave like desktop or mobile? (optimize layouts accordingly)
  • Which device types convert best? (prioritize those experiences)

Cross-Device Campaigns​

Combine device data with sources:

Example insights:

  • Social media traffic is 90% mobile → optimize social landing pages for mobile
  • Email campaigns are 60% desktop → design emails for desktop previews
  • Paid ads are 80% mobile → ensure mobile landing page conversion path

Click-to-Filter Workflows​

Troubleshoot Mobile Issues​

  1. Click "Mobile" in device types
  2. Check bounce rate (is it higher than desktop?)
  3. Check top pages (which pages do mobile users visit?)
  4. Click "Chrome Mobile" to see OS breakdown (iOS vs. Android)

Optimize for Dominant Platform​

  1. Identify your #1 device type (e.g., Desktop: 65%)
  2. Click it to filter
  3. Check which browsers dominate (e.g., Chrome: 70% of desktop)
  4. Focus testing on Desktop + Chrome combination

Investigate Browser-Specific Problems​

  1. Notice Edge traffic dropped in recent data
  2. Click "Edge" to filter to only Edge visitors
  3. Check which pages they visit (or don't visit anymore)
  4. Test those pages in Edge to find the issue

Understanding the Numbers​

Device Type Distribution by Industry​

Typical ranges:

  • B2B SaaS: 50-70% desktop
  • E-commerce: 60-80% mobile
  • News/Media: 70-85% mobile
  • Documentation: 50-60% desktop
  • Gaming: 40-60% mobile

If your distribution differs dramatically from your industry norms, investigate why.

Browser Market Share Evolution​

Browser distributions shift over time:

  • Chrome continues growing across all platforms
  • Safari dominates on Apple devices (iOS enforces Safari engine)
  • Firefox declining but stable among developers
  • Edge growing on Windows (default browser)

Monitor changes quarterly to adjust testing priorities.

Tips & Best Practices​

  1. Test on real devices - Emulators miss real-world performance issues. If 50% of traffic is iPhone Safari, test on actual iPhones.

  2. Monitor trends monthly - Device distributions change as your audience grows. What worked six months ago might not work today.

  3. Compare device bounce rates - Filter by device type and check if metrics differ dramatically (indicates device-specific UX issues)

  4. Cross-reference with page analytics - Filter by mobile, then check which pages have high bounce rates on mobile specifically

  5. Use for progressive enhancement - If 5% of traffic uses older browsers, don't block them - provide a functional baseline and enhance for modern browsers

  6. Consider device context - Mobile users might browse casually while desktop users are researching purchases - adjust content and CTAs accordingly

The Devices section helps you ensure your site works perfectly for the technology your real visitors use, not just the devices you test on. Use it to prioritize development, testing, and optimization efforts.