Sustainability

Learn how WheelOfSpins keeps data transfer and energy use low with in-browser rendering, lightweight pages, long-term caching, and a static hosting setup.

Wheel rendering in your browser

WheelOfSpins draws the wheel, its labels, and the spin animation locally with HTML5 Canvas. Spinning a wheel does not send a request to a server, so no data center has to process each spin, and the tool keeps working even on slow connections once the page has loaded.

  • HTML5 Canvas rendering on your device
  • No server request needed to spin
  • Works on slow connections after loading

Lightweight pages and long-term caching

Pages are pre-built so they load quickly. Scripts and styles are served with long-term cache headers, so returning visitors download very little again, and larger features such as PDF export are only downloaded when you use them. The site loads no advertising, video backgrounds, or third-party tracking scripts.

  • Pre-built pages
  • Year-long caching for scripts and styles
  • No ads or tracking scripts

Hosting and honest claims

The site is served as static files by a managed hosting platform, so no always-on application server is needed to view pages or spin a wheel. Data is only stored on our servers when you choose to save a wheel to an account or create a share link. We do not claim carbon neutrality or publish emissions figures we cannot verify; instead we focus on sending less data and using fewer resources.

  • Static hosting without an always-on app server
  • Server storage only when you save or share
  • No unverified carbon claims

Frequently asked questions

Does spinning a wheel use server resources?

No. The spin happens entirely in your browser, so no server has to process it. Our servers are only used to deliver the page and, if you choose, to save or share wheels.

Does WheelOfSpins run heavy background scripts?

No. The site loads no advertising or third-party tracking scripts, which keeps CPU usage and battery drain low, especially on mobile devices.

Are files cached to save bandwidth?

Yes. Scripts, styles, and other build assets are cached by your browser for up to a year, so return visits download only what has changed.