01
Clarity
Visitors understand who you are, what you offer and what to do next.
The Kanso Standard
A good website is morethan how it looks.
The Kanso Standard brings strategy, design, performance, visibility, measurement and long-term support into one deliberate system.
A complete foundation
What a complete website should give you
Good decisions should be visible in the experience and useful to the business, not hidden behind technical language.
02
Confidence
The experience feels professional, consistent and trustworthy at every size.
03
Momentum
Pages become useful quickly and important journeys stay free of unnecessary friction.
04
Control
You can understand what works, maintain the website and improve it over time.
One connected system
The six standards
These are not six separate services. They are connected criteria used to plan, build and review the website as a whole.
Every page needs a job
Purpose & Conversion
Content, journeys and calls to action are arranged around what the visitor needs to understand and do.
- Recognisable problem
- The website contains useful information, but visitors do not know what to do next.
- What Kanso considers
- Page purpose, information hierarchy, forms, contact points and unnecessary steps are reviewed against the business goal.
- Business outcome
- A clearer journey and a stronger opportunity for visitors to complete a valuable action.
- Page priorities
- Primary user journeys
- Calls to action
- Form friction
Useful before decorative
Design & User Experience
Visual hierarchy, navigation and interaction should make the website easier to understand, not merely more attractive.
- Recognisable problem
- A website can look polished and still be difficult to read, navigate or use.
- What Kanso considers
- Legibility, responsive layouts, accessibility, focus states, consistency and professional perception are considered together.
- Business outcome
- A clearer, more accessible and more convincing experience across devices.
- Visual hierarchy
- Responsive behaviour
- Accessible interaction
- Navigation clarity
Fast enough to feel immediate
Performance & Technical Quality
The main content should appear quickly, controls should respond promptly and the layout should remain stable while loading.
- Recognisable problem
- The page takes too long to become useful or shifts around even though it looks finished.
- What Kanso considers
- LCP, INP and CLS are reviewed alongside images, fonts, external scripts, component loading and maintainable code.
- Business outcome
- Less waiting, less frustration and a more solid experience on realistic devices and connections.
- Core Web Vitals
- Image and font delivery
- Third-party scripts
- Real-device review
Structured to be understood
Search & Discoverability
Important pages need a clear structure for people, search engines and multilingual audiences.
- Recognisable problem
- The business has a website, but key pages remain difficult to find or interpret.
- What Kanso considers
- Semantic HTML, headings, metadata, indexing, canonicals, hreflang, internal links and relevant structured data form the base.
- Business outcome
- A clearer foundation for visibility, local search and a sustainable content strategy.
- Semantic structure
- Indexing foundations
- Metadata and canonicals
- Internal linking
Evidence without excess
Measurement & Improvement
Publishing should create a useful starting point for learning, not an endpoint that is never reviewed.
- Recognisable problem
- The website receives visits, but the business cannot tell which pages or actions matter.
- What Kanso considers
- Search Console, privacy-conscious analytics, forms, key events, landing pages and search queries are matched to the actual scope.
- Business outcome
- Better information for deciding what to keep, change or improve without unnecessary analytics complexity.
- Search Console
- Key-event validation
- Consent and privacy
- Useful reporting
Useful after launch
Support & Longevity
The structure should remain understandable, editable and ready for the next sensible change.
- Recognisable problem
- After launch, every small update creates dependency, delay or a new technical problem.
- What Kanso considers
- Maintainable components, content editing, documentation, security, backups and ongoing support are considered where relevant.
- Business outcome
- More continuity, less uncertainty and a foundation that can evolve with the business.
- Maintainable structure
- Content ownership
- Handover and guidance
- Support when contracted
Designed as a whole
Nothing is treated in isolation.
Design affects performance. Performance affects experience. Experience affects conversion. Search, measurement and support keep the system useful after launch.
See how Kanso uses AI under human direction簡素
Practical verification
How the standard is applied
The exact checks depend on the project, but the method stays visible: important assumptions are reviewed before launch and the agreed foundations are verified afterwards.
Before launch
01- Responsive checks
- Content hierarchy review
- Core journeys and CTA testing
- Performance review
- Core Web Vitals review
- Search foundations
- Form and interaction checks
- Browser and device checks
After launch
02- Indexing and Search Console
- Key-event validation when included
- Error monitoring when included
- Content observations
- Performance observations
- Handover and documentation
- Maintenance plan when contracted
- A clear next review point
Depending on the project, business goals and agreed scope, some tools or recurring checks may be optional. The standard defines how decisions are made; it does not imply that every project includes every ongoing service.
Start with the right questions
Build on better foundations.
Tell us what the website needs to achieve. We will help turn it into a clear, considered system built around your business.
