3D & WebGL websites

3D Websites with WebGL and Three.js: When They Pay Off, Speed & SEO

9 min read Updated: Czytaj po polsku
3D Websites with WebGL and Three.js: When They Pay Off, Speed & SEO

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.

What is a 3D website?

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:

  • WebGL is a browser API for drawing hardware-accelerated 2D and 3D graphics inside a <canvas> element. WebGL 2 now works in practically every mainstream browser.
  • Three.js is an open-source JavaScript library under the MIT licence that makes WebGL manageable: cameras, lights, materials and model loading out of the box. According to the project repository, current builds include both WebGL and WebGPU renderers.
  • WebGPU is a newer graphics API that maps more closely to modern GPUs. Besides rendering, it also lets you run general-purpose computations on the GPU.
  • glTF is an open 3D file format maintained by the Khronos Group – the same body behind the WebGL standard – and designed for delivering models over the web.

Types of 3D websites: from a single accent to a full experience

“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.

When does a 3D website make sense – and when doesn’t it?

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.

When it is worth it

  • You sell a physical product that photos do not do justice to (shape, mechanism, texture) and customers want to “turn it over in their hands”.
  • The product comes in variants – colours, materials, trims. A 3D configurator replaces dozens of photos.
  • You are explaining something spatial: an interior layout, how a device is built, how a process flows.
  • You operate in a premium segment where a polished experience is part of the brand’s value.
  • You are building a campaign or a creative studio portfolio that needs to be remembered.

When to skip it

  • Visitors come for your phone number, prices and directions – a scene only lengthens their path.
  • Most of your traffic is on budget phones and there is no budget for a simplified version.
  • You have no 3D models and creating them would blow the project budget.
  • You are not planning performance tests on real devices.

How do you build a 3D website that loads fast?

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.

  1. Content first, scene second. The headline, copy and CTA render immediately in HTML. Initialise the scene after the page loads, or only when its section approaches the viewport (IntersectionObserver).
  2. Load Three.js separately. Put the library and scene code in a separate, dynamically loaded bundle (import()) so they never block the rest of the page.
  3. Slim down your models. Use glTF/GLB, simplify the mesh (a manufacturer’s CAD file usually carries far more detail than anyone will see on screen) and compress geometry with Draco.
  4. Compress textures. JPG and PNG textures have to be decompressed to full size in GPU memory. As the Khronos Group explains, KTX 2.0 textures with Basis Universal stay compressed on the GPU and reduce download size.
  5. Match quality to the device. Cap the render resolution on high-density screens, switch off expensive effects (real-time shadows, post-processing) on phones, and show an image or video instead of the scene on the weakest devices.
  6. Do not render when nobody is watching. Pause the render loop when the scene is off-screen. For static shots, draw a new frame only when something changes.
  7. Measure on real hardware. Test on a mid-range Android phone, not just a powerful laptop. Check smoothness, how hot the device gets and your field Core Web Vitals after launch.

Does a 3D website hurt SEO?

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.

How to combine 3D with SEO and GEO

  • Render content on the server (SSR) or generate static HTML, then add the 3D scene in the browser as an enhancement.
  • Give every important section or product its own URL and plain <a href> links – those are the only links Google follows.
  • Describe in words what the scene shows: put the product name, variants, dimensions and price in the text, not only in the model.
  • Add structured data (e.g. Product) directly in the HTML.
  • Do not hijack scrolling so that text only appears after an animation finishes.

We check exactly these points in technical audits as part of our SEO and GEO service, before a site goes into the index.

WebGL or WebGPU in 2026?

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.

Accessibility: motion is not for everyone

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.

  • With prefers-reduced-motion: reduce, show a still frame instead of a moving scene.
  • Add a visible pause button for any looping animation.
  • Make scene controls – rotate, zoom, switch variant – keyboard accessible.
  • Check the contrast of text over the scene on both its lightest and darkest frames.

What does a 3D website cost, and what does the process look like?

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.

  1. Goal and script. What the scene must explain and which action it leads to; a storyboard of key shots.
  2. Models. Sourcing, modelling or optimising existing files.
  3. Prototype. One scene tested on a weaker phone before the rest is built.
  4. HTML-first build. Content, SEO and structured data work independently of the scene.
  5. Testing. Performance, accessibility, cross-browser checks, fallbacks.
  6. Post-launch measurement. Field Core Web Vitals and how users behave around the scene.

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.

Frequently asked questions

Do 3D websites work on phones?

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.

Does Google index content inside a 3D 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.

How much does a 3D website cost?

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.

What is the difference between WebGL and Three.js?

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.

Will a 3D scene slow my website down?

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.

Should I use a live 3D scene or a pre-rendered 3D video?

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.

Sources

  1. Can I use – WebGL 2.0
  2. web.dev – WebGPU is now supported in major browsers (25 Nov 2025)
  3. three.js – GitHub repository (MIT licence, WebGL and WebGPU renderers)
  4. Google Search Central – Understand JavaScript SEO basics
  5. Vercel – The rise of the AI crawler (17 Dec 2024)
  6. web.dev – Largest Contentful Paint (LCP)
  7. Khronos Group – KTX 2.0 textures enable compact, visually rich glTF 3D assets (20 Apr 2021)
  8. web.dev – prefers-reduced-motion: Sometimes less movement is more
  9. W3C – Understanding WCAG 2.2 SC 2.3.3 Animation from Interactions

Need help with this?

A website people remember. We blend Three.js, shaders and scroll-driven animation with content Google and AI can read without friction.