So is it mainly a web-brower benchmark or strictly web browser benchmark?
The test itself is designed to run in a web browser.
It mainly says how fast your system is (in combination with your specific browser) in the test.
CSS is the only language that all the major web browsers natively understand for content presentation and markup.
There is no alternative to CSS at the moment.
It is also sometimes used in other fields such as user interface development.
For example, the GNOME foundation also uses CSS for user interfaces:
Read-only mirror of https://gitlab.gnome.org/GNOME/gtk - GNOME/gtk
github.com
Read-only mirror of https://gitlab.gnome.org/GNOME/gnome-shell - GNOME/gnome-shell
github.com
However, I don't think this is a good idea and LXQt feels more responsive to me than GNOME Shell and XFCE.
In most cases, the performance of CSS-based animations is almost the same as JavaScripted animations — in Firefox at least.
jQuery is usually slower than CSS but there are fast JS alternatives to jQuery.
Some JavaScript-based animation libraries, like GSAP and Velocity.JS, even claim that they are able to achieve better performance than native CSS transitions/animations.
The conclusion from these observations is that for some websites with a lot of CSS content in 2023, the CSS part can still be heavier than the JS part.
The fact that companies like Apple and Google have created JavaScript/DOM/WebAssembly/HTML benchmarks (Octane, JetStream, Speedometer, Chalkboard) every time without creating a CSS test proves that there is no basic understanding of website performance to be found at these types of large companies.
laceholder are now fully supported.
