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:
- Visit get.webgl.org
- If you see a spinning cube, WebGL works
- 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:
- Go to
chrome://settings - Advanced → System
- Enable "Use hardware acceleration"
- Restart browser
Enable WebGL in Firefox:
- Go to
about:config - Search for
webgl.disabled - Set to
false
Globe Loads But No Markers
Causes:
- No visitor data yet
- The selected date range has no visits
- Geographic data unavailable for those visits
Solutions:
- Open the Live View tab to confirm visitors are arriving in real time
- Widen the date range using the period selector
- Some visits cannot be geolocated (for example, requests behind certain VPNs or proxies); these still count in your stats but may not place a marker
Globe Very Slow
Causes:
- Integrated graphics
- Older computer
- Many concurrent visitors plotted at once
Solutions:
- Enable hardware acceleration in your browser (see the browser-specific sections below)
- Update your graphics drivers
- Close other GPU-intensive tabs
- For a lightweight view of the same geographic data, use the breakdowns in the Analytics tab instead
Globe Freezes Browser
Cause: GPU overload or memory issues
Solutions:
- Close other GPU-intensive tabs
- Reduce browser zoom level
- Try incognito mode (no extensions)
- Use the Analytics tab for a non-GPU view of the same data
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:supportfor 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
| Component | Minimum |
|---|---|
| GPU | Intel HD 4000 or equivalent |
| RAM | 4 GB |
| Browser | See above |
| Display | 1280x720 |
Recommended
| Component | Recommended |
|---|---|
| GPU | Dedicated graphics card |
| RAM | 8 GB+ |
| Browser | Latest Chrome/Firefox |
| Display | 1920x1080+ |
Mobile Device Issues
Globe Not Loading on Mobile
The globe runs best on desktop. On a phone:
- Plotting many markers can be heavy on the GPU
- For a lighter experience, use the Analytics tab to see the same geographic data
- Make sure your mobile browser is up to date
Tablet Rendering Issues
- Ensure your tablet has sufficient GPU capability
- Try landscape orientation
- Keep your browser up to date
Checking GPU Status
Chrome GPU Info
- Go to
chrome://gpu - Check "Graphics Feature Status"
- Look for:
- WebGL: Hardware accelerated ✓
- WebGL2: Hardware accelerated ✓
Firefox GPU Info
- Go to
about:support - Scroll to "Graphics"
- Check WebGL renderer
Alternative Views
If globe issues persist, you can see the same geographic data without a 3D view:
Analytics Tab
- Open your website's dashboard and select the Analytics tab
- The countries and locations breakdown shows the same geographic data as a sortable list
- No WebGL or GPU required, so it works on any browser
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:
- Clear browser cache
- Clear site data for Zenovay
- Hard refresh (Ctrl+Shift+R)
Chrome:
- Settings → Privacy → Clear browsing data
- Select "Cached images and files"
- Clear data
Firefox:
- Settings → Privacy
- Clear Data → Cached Web Content
Contacting Support
If issues persist, provide:
- Browser and version
- Operating system
- GPU model (from chrome://gpu)
- Screenshot of error
- Console errors (F12 → Console)