
Lighthouse from 90 to 100: what a perfect score takes
What does it take to score 100 in Lighthouse? How performance affects Google Ads costs, rankings and conversion, and what 100/100/100/100 requires.
We find out where users get stuck in your service, and design and build what needs to change.
We build and run systems for
Most people who contact us have a website, customer portal or internal system that people struggle with. Others are building something new and want to get it right from the start.
We talk to your users and watch them use the service. That shows us where they hesitate, make mistakes or give up.
We test new pages and features as clickable sketches with a few of your users. Problems found at that stage are cheap to fix.
We tidy up menus, forms and wording, so users find their way and understand what to do.
A page that loads slowly or shows confusing error messages makes for a poor experience. Our developers fix that.
Websites and apps should work for everyone, including people using a screen reader or keyboard. We check your service against the requirements and fix what's missing.
You rarely need a completely new service. Often it's enough to change the places where most users get stuck.
Audits and fixes against WCAG, so the site works for everyone and holds up under inspection.
We map the whole service, front stage and back stage, and build it with the same people.
Design tokens and components that match in Figma and in code, versioned as a product of their own.
Customers call or emailabout things they should be able to do on the website.
Many people start an order or a formbut don't finish it.
Staff avoid an internal systemand work around it in Excel.
The service has to meet accessibility requirementsand you don't know how far off you are.
How we fixed contrast, keyboard navigation and the code behind the page until it got a full score.

What does it take to score 100 in Lighthouse? How performance affects Google Ads costs, rankings and conversion, and what 100/100/100/100 requires.
We start with a conversation about what the service should do for the business, who uses it and what doesn't work today.
We make simple sketches and let some of your users try them. What they struggle with, we fix in the sketches, where changes cost little.
Our developers build what has been designed, and the designer follows the work all the way to launch.
We look at how the service is used in the first few weeks and adjust whatever still causes problems.
ongoingWe go through the service with your users and give you a list of what should change, in order of priority.
We design, test and build the service in one team, so what gets tested is also what gets launched.
We check the service against WCAG and fix what's missing.
If you're not sure which one fits, we'll work it out in a first conversation.
UX stands for user experience. It's about how easy a website, app or system is to use: whether people find what they're looking for, understand what to do and get done what they came for.
UI is what you see, such as buttons, colours and fonts. UX is the whole experience, from the moment users arrive until their task is done. A good-looking design doesn't help much if users can't find their way.
The people who built a service know it too well to see it the way a new user does. When we watch users try it, we find problems that are hard to spot from the inside.
Rarely. Often it's enough to move a button, shorten a form or rewrite an error message. A UX review shows where it's worth starting.
In Norway, websites and apps aimed at the public have to meet the requirements, in both the public and private sector. The Norwegian Authority for Universal Design of ICT checks this and can order fixes.
Yes. Our designers and developers work in the same team, so you don't have to hand the design over to another company.
Tell us what the service is for and who uses it, and we'll suggest where it makes sense to start.