// Tech

Stats.js — FPS Monitor for Three.js Development

Stats.js puts an FPS monitor in the corner of your scene during development — essential for catching performance regressions early.

Get a quote All 3D services

Stats.js (mrdoob/stats.js, same author as Three.js) is a tiny FPS monitor that you call once per frame. Three modes: FPS (frames per second), MS (frame time in milliseconds), MB (allocated memory). I keep it visible on every dev session — if I add a feature and FPS drops from 60 to 45, I know immediately rather than discovering it on QA day. For production I keep a lightweight version that logs FPS to console only on debug=true URL flag, never visible to users. Pairs well with quality.tier device detection — track the actual achieved FPS per tier on real devices to validate your tier classifications.

When this is overkill

If the goal is a simple e-commerce listing or content blog, a full stats js three setup is overkill — a CSS-driven hero plus static images converts just as well at 1/10 the cost. stats js three earns its keep when the brand needs a memorable visual moment or when 3D actually clarifies the product (configurators, tours, demos).

What you get hands-off

After delivery: source repository on GitHub (private), commented code, a 5-min Loom walkthrough explaining the scene logic, and the asset pipeline documented. First year of hosting and minor revisions is included. After that we agree on a maintenance plan if needed.

What this delivers

Concrete output: a working stats js three integration on a real production site, not a demo. The integration includes device-tier detection so weak phones get a lighter version automatically. Source files are handed over in their original formats — Blender, GLSL, glTF — so any future developer can continue where I stopped.

How I work with it

On a typical project, stats js three ships as a self-contained module: one entry-point JS file, one CSS file, asset bundle below 1.5MB total. I keep the integration sandboxed so the rest of the site stays SEO-friendly classical HTML. Frame budget targets 60 FPS on a mid-range Android, with a measurable fallback below.

Frequently asked questions

Why pick this technology over alternatives?

It has the largest production-quality ecosystem, the most documentation, and the most experienced developers available. For a site you want to maintain for 3+ years, ecosystem maturity matters more than feature peak.

What if a newer tool comes out next year?

I track new tooling and migrate when it makes sense, but only after the new tool ships stable production releases for at least 6-9 months. I don't rebuild client sites on bleeding-edge tools — that's the path to broken sites.

How long does this take?

Standard scope: 4-6 weeks from contract signature to live site. Larger scope (configurator, multi-scene scrollytelling) takes 8-12 weeks. Rush projects (2-3 weeks) are accepted with a 30-40% rush surcharge.

What does it cost?

Hero-section 3D upgrade: \$1,500-\$2,500. Full multi-scene 3D site: \$3,500-\$8,000. Configurator with custom shaders: \$5,000-\$12,000. All fixed-price, source code included. EUR equivalents on request.

What if my visitors are on weak phones?

The site detects device tier before the first scene loads and serves a lighter version on weak hardware (fewer particles, simpler shaders). Devices without WebGL get a static fallback that preserves the visual language and conversion path.

Ready to ship a 3D experience?

Tell me what you need — fixed price, fixed deadline, no surprises.

Get a quote +381 61 224 8989