WebGL serves as a bridge between javascript and shaders, but lacks the ability to provide detailed information about device performance.
You can create a simple program using WebGL to gauge client GPU performance through FPS calculation (http://jsfiddle.net/vZP3u/). By experimenting with different shaders, you can make educated guesses. However, be cautious as excessive testing could be perceived as a DOS attack, potentially causing browser crashes that deter visitors from your site.
For additional data on WebGL capabilities, refer to
In essence, native javascript does not directly reveal device information; instead, tests must be conducted for insights. Utilize ajax for insight into download/upload speeds, pure javascript for CPU performance analysis, or WebGL shaders for evaluating GPU performance - though results may vary based on user activity at the time.
Furthermore, some browsers may offer specific methods for accessing data, such as G Chrome's console.memory
; however, these approaches are not universally applicable across all browsers.