A working demonstration of 3D web capability. The town was modeled in Blender, exported to glTF, and is rendered live in your browser with Three.js. Nothing on this page is a video or a pre-baked image.

Will a 3D page still work on slow phones and bad rural internet?

That is the first constraint on every build. Models are compressed and decimated, the scene is budgeted against a target device, and a static fallback is always shipped so the page still reads and converts when WebGL is unavailable or the connection is slow.

3D City Demo | Gorden Web Design

Q: Does my small business site need 3D?

No. Most small business sites do not need 3D and should not pay for it. Interactive 3D is worth it when a product is hard to show in a flat photo, when a location or process needs to be explained spatially, or when the demo is the point of the page. Otherwise a fast static site that ranks and converts is the better investment.

Q: What does a 3D build cost and how long does it take?

A scoped 3D product viewer or configurator on a normal site budget runs a few weeks and is quoted as its own line item, separate from the site build. You get a fixed price and a fixed launch date after the discovery call.

What you are looking at

A small Central Washington town: a grid downtown, a lake on the east side, a rail line with a grain elevator on the west, and a park in the middle. Every window is lit individually in the texture. It is a real model, not a picture of one.

96

Buildings, each with its own floors and facade phase

9,030

Triangles in the scene after join and merge

650 KB

glTF download, small enough to load on a phone

0

Stock photos or image sequences. All geometry plus one procedural texture.

Rendered offline in Blender

The same scene, rendered on a CPU-only Linux box with Cycles. No GPU, no render farm. Each frame took about two minutes.

The town skyline seen from across the lake at dusk, with lit windows reflected in the water — Across the lake at dusk

Street level view down a town avenue with lit windows, a street lamp, and cars with headlights — Down Main Street

Top-down plan view of the town showing the street grid, blocks, and park — Town plan, from above

How the build works

The pipeline is the same one we would use for a product viewer, a configurator, or a location explainer. The city is just a small sample of it.

Model in Blender

Geometry is generated from a script, so the town is reproducible and can be re-tuned. Buildings, roads, the rail spur, the elevator, trees, cars, and street lights are all real geometry.

# one building, one call box(x, y, w, d, floors) # facade UVs tile the atlas uv = world_xy / 8.0 # windows are baked lit = rng() < 0.55

Scripted, not hand-placed

Random placement would look fake. The script instead derives every building from the same rules, so the result is consistent.

Export to glTF

One file, one draw call per material group. Emissive window materials carry over, so the lights still glow in a browser engine.

Render live with Three.js

The browser loads the model, lights it, and lets the visitor orbit. No video, no image sequence, no pre-baked turntable.

Budgeted for the device on the other end

Model complexity, texture resolution, and frame rate are set against a target phone, not a workstation. Where a 3D scene is the wrong call for a small business site, we say so and quote the static build instead.

Where a 3D build earns its cost

Most small business sites should stay flat. These are the cases where interactive 3D does work that a photo or a paragraph cannot.

01

Product configuration

Color, size, and option choices that change what the customer is looking at. A furniture maker, a sign shop, or a fabricator sees the change before they order.

02

Site and process explanation

A facility, a farm, a piece of equipment, or a route. When a flat photo leaves the customer guessing, a model they can turn answers the question.

03

Equipment and training

Interactive parts breakdowns for a repair shop, a dealer, or a vocational program. Far more useful than a PDF that scrolls.

04

The demo is the point

When the product is the technology itself, a live 3D experience is the portfolio piece. That is what this page is.

Questions we get first

What is this page, technically?

A working demonstration of 3D web capability. The town was modeled in Blender, exported to glTF, and is rendered live with Three.js in your browser. Nothing on it is a video or a pre-baked image.

Does my small business site need 3D?

No. Most small business sites do not need 3D and should not pay for it. It is worth it when a product is hard to show in a flat photo, when a location or process needs to be explained spatially, or when the demo is the point of the page. Otherwise a fast static site that ranks and converts is the better investment.

What does it cost and how long does it take?

A scoped 3D viewer or configurator on a normal site budget runs a few weeks and is quoted as its own line item, separate from the site build. You get a fixed price and a fixed launch date after the discovery call.

Will it work on a slow phone or bad rural internet?

That is the first constraint on every build. Models get compressed and decimated, the scene is budgeted against a target device, and a static fallback always ships so the page still reads and converts when WebGL is unavailable or the connection is slow.

Got a product that photographs badly?

Send us the photos and the product. We will tell you whether 3D is worth it, and what it costs.

Start a project