Digital sobriety
Using resources thoughtfully.
Loupe works on loading, file reuse and map rendering. Practical choices to limit unnecessary work, complemented by your content decisions.
Load features where they are needed
The map engine loads separately from content pages. Images handled by the site’s optimization can be served in WebP or AVIF depending on the browser. These mechanisms limit some transfers without making every media file lightweight by default.
Reuse instead of reloading
Versioned static files benefit from long-lived caching. Within the map, a shared cache reuses resources that have already loaded. Memory limits and release rules bound this reuse.
Manage 3D complexity
The engine groups compatible objects and their geometry, and manages scene resources by area. Model size, textures and level of detail remain key factors. Results depend on the building represented and the device used.
A project-wide approach
Choosing appropriately sized images, suitable models and useful content helps limit the resources needed. Loupe’s optimizations alone are not a carbon footprint assessment: impact must be evaluated alongside hosting, equipment and actual use.