Free5 minutesbeginner

Globe Not Loading

Fix issues when the 3D globe visualization doesn't display or performs poorly.

globe3dvisualizationwebglperformance
Last updated: January 15, 2025

Troubleshoot issues when the 3D globe visualization doesn't load or display correctly.

Common Globe Issues

Globe Shows Blank/Black

Cause: WebGL not supported or disabled

Check WebGL support:

  1. Visit get.webgl.org
  2. If you see a spinning cube, WebGL works
  3. If not, your browser doesn't support WebGL

Solutions:

  • Update your browser to latest version
  • Enable hardware acceleration
  • Update graphics drivers

"WebGL Not Supported" Error

Browser requirements:

  • Chrome 56+
  • Firefox 51+
  • Safari 11+
  • Edge 79+

Enable WebGL in Chrome:

  1. Go to chrome://settings
  2. Advanced → System
  3. Enable "Use hardware acceleration"
  4. Restart browser

Enable WebGL in Firefox:

  1. Go to about:config
  2. Search for webgl.disabled
  3. Set to false

Globe Loads But No Markers

Causes:

  1. No visitor data yet
  2. Wrong date range selected
  3. Geographic data unavailable

Solutions:

  1. Check Real-Time view for active visitors
  2. Expand date range
  3. Ensure IP anonymization isn't set to "full"

Globe Very Slow

Causes:

  1. Integrated graphics
  2. Old computer
  3. Too many markers

Solutions:

Enable performance mode:

  1. Click the Settings icon on the globe
  2. Enable Performance Mode
  3. This reduces visual quality for speed

Or manually:

  • Reduce marker count
  • Disable animations
  • Use 2D map instead

Globe Freezes Browser

Cause: GPU overload or memory issues

Solutions:

  1. Enable performance mode
  2. Close other GPU-intensive tabs
  3. Reduce browser zoom level
  4. Try incognito mode (no extensions)

Browser-Specific Issues

Chrome

Black screen:

  • Disable conflicting extensions
  • Clear GPU cache: chrome://gpu
  • Reset Chrome flags: chrome://flags

Firefox

Rendering issues:

  • Update Firefox
  • Check about:support for WebGL info
  • Try Safe Mode

Safari

Globe not appearing:

  • Ensure macOS updated
  • Check Safari → Preferences → Privacy
  • Enable WebGL in Develop menu

Edge

Performance issues:

  • Disable extensions
  • Enable hardware acceleration
  • Update to latest Edge

Hardware Requirements

Minimum Requirements

ComponentMinimum
GPUIntel HD 4000 or equivalent
RAM4 GB
BrowserSee above
Display1280x720
ComponentRecommended
GPUDedicated graphics card
RAM8 GB+
BrowserLatest Chrome/Firefox
Display1920x1080+

Mobile Device Issues

Globe Not Loading on Mobile

The globe is optimized for desktop. On mobile:

  • Performance mode auto-enabled
  • Some features disabled
  • Consider using the 2D map view

Tablet Rendering Issues

  • Ensure tablet has sufficient GPU
  • Try landscape orientation
  • Use performance mode

Checking GPU Status

Chrome GPU Info

  1. Go to chrome://gpu
  2. Check "Graphics Feature Status"
  3. Look for:
    • WebGL: Hardware accelerated ✓
    • WebGL2: Hardware accelerated ✓

Firefox GPU Info

  1. Go to about:support
  2. Scroll to "Graphics"
  3. Check WebGL renderer

Alternative Views

If globe issues persist, use alternatives:

2D Map View

  1. In the Globe tab, click 2D Map
  2. Same data, less GPU intensive
  3. Works on all browsers

Table View

  1. Click View as Table
  2. See geographic data as list
  3. No GPU requirements

Corporate/Enterprise Environments

IT Policy Blocking WebGL

Some corporate policies disable WebGL:

  • Contact IT department
  • Request exception for Zenovay
  • Use alternative views

VPN/Proxy Issues

VPNs may slow globe loading:

  • Try without VPN temporarily
  • Check for WebGL blocking proxies

Clearing Cache

If globe worked before:

  1. Clear browser cache
  2. Clear site data for Zenovay
  3. Hard refresh (Ctrl+Shift+R)

Chrome:

  1. Settings → Privacy → Clear browsing data
  2. Select "Cached images and files"
  3. Clear data

Firefox:

  1. Settings → Privacy
  2. Clear Data → Cached Web Content

Contacting Support

If issues persist, provide:

  1. Browser and version
  2. Operating system
  3. GPU model (from chrome://gpu)
  4. Screenshot of error
  5. Console errors (F12 → Console)

Next Steps

Was this article helpful?