Website Animation: Types, Tools and Performance Without Compromise
Website animation done right: micro-interactions, scroll animation, Lottie, CSS, GSAP and WebGL, plus how to protect speed, Core Web Vitals and accessibility.
Read
A 3D website makes sense when a three-dimensional scene shows something photos cannot: a product you can inspect from every angle, an interior, how a device works, or the feel of a premium brand. Technically it is an ordinary HTML page with a canvas element in which WebGL – usually via the Three.js library – renders graphics on the GPU. Done well, it hurts neither speed nor SEO, as long as the content stays in HTML and 3D is a layer on top rather than the foundation.
A 3D website is one where part of the content is rendered in real time as a three-dimensional scene. Visitors can rotate it, zoom in, or move through it as they scroll. This is not a video of a 3D animation – it is graphics computed live by the graphics card inside the browser. Four terms worth knowing before you brief an agency:
<canvas> element. WebGL 2 now works in practically every mainstream browser.“3D website” can mean one rotating product in the header or an entire site built like a video game. In terms of cost, performance and SEO risk, these are completely different projects.
| Approach | When it makes sense | Device load | SEO risk |
|---|---|---|---|
| 3D accent in the hero section | The brand wants to stand out on the first screen; the rest of the site is conventional | Low to medium if the scene loads after the content | Low |
| Product viewer or configurator | Furniture, cars, hardware, jewellery – products with colour and material variants | Medium | Low, provided descriptions and prices are in HTML |
| Scrollytelling (scroll-driven scene) | Product launches, campaigns, case studies | Medium to high | Medium: it is easy to “hide” text inside the animation |
| Entire site inside a canvas | Campaigns and portfolios where the effect is the point | High | High: no text for Google or AI bots |
For business sites, the first two options usually work best. They deliver impact where it matters and leave the rest of the site fast and readable.
Before you commission a 3D scene, ask one question: if you removed it, would visitors lose information or just an effect? If it is only the effect, a lighter animation or a well-edited video often works better – the kind of work we do in motion design and video production.
Start with a fact that makes life easier: the <canvas> element is not considered when LCP is measured. Among the candidates for the largest element, web.dev lists images, video, elements with a background image and blocks of text – canvas is not on the list. If the headline and first-screen copy are in HTML, LCP depends on them, not on the scene. The scene still is not free: heavy JavaScript can hurt how quickly the page responds to clicks, measured by INP. We explain how to read these metrics in our guide to Core Web Vitals and speeding up your website.
import()) so they never block the rest of the page.The technology itself does not – moving your content into a canvas does. Google processes JavaScript pages in three phases: crawling, rendering and indexing, and its documentation says plainly that Google can only see content that is visible in the rendered HTML. Pixels drawn into a canvas are not text. A headline rendered as 3D lettering simply does not exist for a search engine.
It is even stricter in AI search. A Vercel analysis from December 2024 found that none of the major AI crawlers render JavaScript: GPTBot (OpenAI) and ClaudeBot (Anthropic) fetch JS files but do not execute them. Gemini is the exception, as it runs on Googlebot’s infrastructure. If you want ChatGPT or Claude to cite your site, the content has to be in the HTML your server sends.
<a href> links – those are the only links Google follows.We check exactly these points in technical audits as part of our SEO and GEO service, before a site goes into the index.
WebGL 2 is the safe default today: according to caniuse.com, 97.29% of browsers in use worldwide support it, including Safari 15+ on macOS and iOS. Since November 2025, WebGPU has been, as the web.dev team announced, supported in all major browsers – with caveats. Firefox supports it from version 141 on Windows (and from 145 on Apple silicon Macs), and Safari from version 26 on macOS, iOS, iPadOS and visionOS.
| Criterion | WebGL 2 | WebGPU |
|---|---|---|
| Browser support | 97.29% of browsers (caniuse) | Chrome and Edge 113+, Firefox 141+ (Windows), Safari 26+ |
| Ecosystem | Mature, plenty of examples and tooling | Growing fast, some tooling still settling |
| Capabilities | Real-time 3D graphics | Graphics plus GPU compute |
| Choose it for | The default for business sites and shops | Advanced effects, simulations, thousands of objects – with a WebGL fallback |
It does not have to be either/or. Three.js has renderers for both APIs, so you can build for WebGPU and fall back to WebGL where the newer API is not available.
Some people switch on “reduce motion” in their operating system because animation makes them dizzy or breaks their focus. A site can detect this through the prefers-reduced-motion media query – web.dev shows how to switch off animation or serve a static version. WCAG 2.2 success criterion 2.3.3 (level AAA) states that motion animation triggered by interaction can be disabled, unless it is essential to the content.
prefers-reduced-motion: reduce, show a still frame instead of a moving scene.As a rough guide, on the Polish market at the end of 2026 a website with interactive 3D elements starts at about PLN 20,000 net. For wider context, see our article on how much a website costs. The biggest price drivers are whether models already exist (CAD files usually need simplifying), the number of scenes and interactions, a configurator, and how carefully the fallback for weaker devices is built.
At OrbitBuilder, Olaf Klimasz leads the visual layer, animation and front-end, while Bartłomiej Chwajoł handles back-end, integrations and SEO. That way the visual effect and search visibility are designed together, not in separate rooms.
Got a product or brand that deserves a third dimension? Tell us about your idea – we will check whether 3D makes sense for it and propose a version that is fast and visible in Google. See how we build 3D and WebGL websites or get in touch.
WebGL 2 is supported by 97.29% of browsers in use, including Safari on iOS from version 15, so a scene will run on almost any modern smartphone. Smoothness is another matter: weaker phones need a simplified version with lower resolution, fewer effects or a still image instead of the scene.
No. Google indexes text from the rendered HTML, and whatever is drawn in a canvas element is just pixels to it. Names, descriptions, prices and headings must be in HTML; the 3D scene can illustrate them but not replace them.
As a rough guide, from about PLN 20,000 net on the Polish market at the end of 2026. The price depends on whether you already have models, the number of scenes and interactions, any configurator and the fallback for weaker devices. That is a market range, not a price list – only a scoped quote gives you a real figure.
WebGL is the browser API for drawing GPU-accelerated graphics – low-level and labour-intensive. Three.js is a JavaScript library built on top of WebGL (and WebGPU) that gives you ready-made cameras, lights, materials and model loaders. Most 3D websites are built with Three.js or similar tools.
It can, if it blocks content or uses uncompressed models and textures. The canvas element is not counted towards LCP, so with content in HTML and the scene loaded later, your loading metric can stay good. You still need to keep JavaScript in check because it affects INP, or responsiveness to clicks.
If visitors need to do something – rotate a product, switch variants, explore – you need a scene rendered in real time. If they only need to see the effect, a pre-rendered video is lighter, behaves predictably on every device and often costs less to produce.
Insights

Website animation done right: micro-interactions, scroll animation, Lottie, CSS, GSAP and WebGL, plus how to protect speed, Core Web Vitals and accessibility.
Read
Explainer video for business: when it pays off, how long it should be, how to write the script, how production works and whether to choose 2D, 3D or screencast.
Read
Product video for ecommerce: product page videos, Meta and TikTok ads, 3D packshots and UGC. Ideal length, platform specs and embedding without slowdown.
ReadA website people remember. We blend Three.js, shaders and scroll-driven animation with content Google and AI can read without friction.
We use essential cookies and, with your consent, analytics (Google Analytics, Hotjar) and marketing cookies to understand how you use the site and improve it. Details in our privacy policy.