Web Design

Most websites look fine.
Yours has to work.

For a lot of people, your website is the first real thing they learn about your company — before a meeting, before a pitch, before applying for a job. We design sites that earn that moment, in English and Japanese, and hand them over for you to own.

A web design studio. Down the left, five service cards: strategy and planning, UI and UX design, website development, SEO and performance, and content and visuals. In the centre, a large screen shows a website headed Ideas, People, Impact, with phones and floating cards around it showing it in English and Japanese, and desks of monitors below with page layouts, an analytics chart and code. Along the bottom, five steps: discover, design, develop, optimize and launch. Down the right, five cards for the kinds of organisation a site is built for: enterprises, startups, NGOs, the public sector and global teams. Lines of light run between the cards.
Illustrative artwork. The website on its screens is drawn for the picture. The cards on the right name kinds of organisation a website can be built for; they are not a list of clients. Their points - investor-ready sites, converting visitors, multi-region support and the rest - describe what a site is aimed at, not measured results and not a promise. The five steps along the bottom are a simplified picture; the process this page describes has six.
All services

The stake

People decide how serious you are before they read a sentence

It is not fair and it is not going away. A visitor forms a view of your company from layout, spacing and typography within moments of arriving — long before they reach the paragraph explaining why you are worth their time. A site that looks improvised makes everything behind it look improvised too.


A type scale, not font sizes

Sizes chosen once as a related set, then reused. It is the difference between a page that feels composed and one where every heading was nudged until it looked about right. The specimen above this paragraph is the one this page uses.

A spacing rhythm you can feel

Space comes from a fixed scale, so the gaps between things mean something: related items sit closer, sections breathe. Most template sites fail here first, and readers register it as "cheap" without being able to say why.

Contrast that is measured

Every text and background pair is checked against WCAG rather than eyeballed. ROBO LAB’s own palette documents it: #0079CB carries white at 4.57:1 for buttons, #006FBA at 5.29:1 for text. Two blues, because one number was not good enough for both jobs.

Hierarchy before decoration

A visitor should know what the page wants them to do before they have read a word of it. That is size, weight and space doing the work — not a bigger button or a brighter colour.

Motion with a reason

Movement that shows cause and effect, at a duration matched to the distance travelled, and switched off entirely for anyone whose system asks for reduced motion. Animation as garnish is how a site starts feeling slow.

Built to be read

Line length capped near 65 characters, generous leading, real text rather than words baked into images. Readable pages rank better, but more to the point they get read.

Specimen

This page is the sample

A screenshot only tells you what a page looked like on somebody else’s screen. So here is the scale governing the page you are reading: six sizes, one relationship, used everywhere. Nothing on this page was nudged until it looked about right.

Display

Headline

Section

Section heading

Subhead

Subheading

Lead

Introductory paragraph

Body

Body copy, set near 65 characters

Caption

Caption and supporting detail

And here is how it behaves at width

Change the frame and watch the layout rearrange. It is reacting to the frame’s own size rather than the window’s, which is the technique that keeps a real page composed at every width instead of merely shrinking it.

Three columns above 480px, two below it, one on a phone. The type does not get smaller; the composition changes.

Bilingual by default

English and Japanese are not the same design problem

Translating the words is the easy half. Japanese sets at a wider line-height, has no spaces to break on, and will break in the middle of a word unless the page is told not to — which is how a careful English layout ends up looking broken in Japanese. Below is the same paragraph, set both ways, with this site’s own rules applied.

Englishline-height 1.7

ROBO LAB designs and builds websites that are fast, accessible and straightforward for your own team to maintain after launch.

Latin text breaks at spaces, so the browser needs little help. A sensible measure and leading is most of the work.
日本語line-height 2.0

ROBO LABは、表示速度が速く、アクセシビリティに配慮し、公開後も自社で無理なく運用できるWebサイトを設計・構築します。

Wider leading, phrase-aware breaking (auto-phrase) and strict line-break rules, so a word never splits across two lines.

Process

Six steps, ending with you holding the keys

  1. Understand the job the site has to do

    Who it is for, what they need to do on it, and what counts as success. A site for raising investment and a site for recruiting engineers should not look the same, and usually do.

  2. Structure before surface

    Content and hierarchy first, in wireframe, while it is still cheap to change. Choosing colours before you know what the page has to say is how projects get expensive.

  3. Design in a system

    Type scale, spacing, colour roles and components defined once, so page ten is as considered as page one and your team can add page eleven without calling us.

  4. Build it properly

    Semantic, accessible markup. Responsive from the smallest screen up. Fast by construction rather than optimised afterwards.

Launch is not the end of the job. These two are what stop you needing us again.

  1. Integrate the CMS

    WordPress or Webflow, set up so your team edits content without touching layout — and without being able to break it by accident.

  2. Hand over with the keys

    Source, design system, documentation and training. You own the result outright.

Ownership

What you get to keep

The most expensive thing about a cheap website is usually discovering you cannot change it without the people who built it.

The design system

type scale, colour roles, spacing and components — documented, so the site can grow after we have gone.

The source code

in your repository, under your licence. Not rented from us.

A CMS your team can actually use

editing content without risking layout, because the fields constrain what can go wrong.

Accessibility built in

WCAG considerations from the first wireframe, not bolted on before launch when fixing them costs five times as much.

Documentation and training

how it is put together and how to extend it, delivered to the people who will maintain it.

Before you ask

Questions we get

Can we edit the site ourselves afterwards?

Yes, and that is the point of the CMS step rather than a nice extra. Content fields are set up so your team changes words and images without being able to break the layout. If you can only update your own website by emailing an agency, you do not really own it.

Do you work in WordPress, or something custom?

Both, and the answer should come from how you work rather than from what we prefer to build. WordPress or Webflow when your team needs to publish often and independently; a custom build when the site does something a CMS would fight. We will tell you which before you commit, including when the cheaper option is the right one.

We need the site in Japanese and English.

This is a real design problem rather than a translation task, and the section above is the short version of why: Japanese sets at wider line-height, breaks by phrase rather than by word, and a layout tuned for English will visibly strain. ROBO LAB runs its own site in both languages, so the rules are ones we apply daily rather than research for you.

How much does it matter if the site is slow?

It is the one quality issue your visitors measure without noticing they are doing it. Slow pages get abandoned before they render, and search engines rank them accordingly. We build for speed from the start, because retrofitting performance means rebuilding the parts that caused it.

Is accessibility a legal requirement for us?

That depends on your market and your customers, and we are not the right people to give you a legal opinion. What we can say is that designing to WCAG from the start costs very little, while retrofitting it after launch is one of the more expensive things you can do to a website — so we build that way regardless.

Next

Send us the site you have now

We will tell you what is working, what is costing you visitors, and whether you need a redesign or three specific fixes. Plenty of sites need the second.

Start a project All services
Resources

White Papers & Articles

Related white papers and articles for Web Design will appear here as they're published.

View More

Talk to us about Web Design

Get in touch and we'll help you find the right approach.

Talk to Us
Ready to Transform?

Securely Adopt AI
Built for Enterprise.

ROBO LAB helps organizations securely adopt AI through intelligent software, enterprise automation, cloud technologies, and world-class engineering talent. From strategy to deployment, we deliver outcomes that matter.

Start Your AI Journey Learn About Us
24/7
Enterprise Support
10+
AI Services
11
Industries Served
4
Flagship Platforms