
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.
Web applications and APIs in Laravel, one of the most widely used PHP frameworks, built by senior developers who have worked with it since it launched in 2011.
We build and run systems for
From a single API to a full SaaS platform, with code that’s easy to maintain for years.
Customer portals, line-of-business systems and SaaS platforms with sign-in, roles and payments.
REST APIs with Sanctum for mobile apps, partners and other systems.
Inertia and React give admin panels that behave like an app, without a separate API in between.
Horizon and Redis handle heavy jobs such as PDFs, email and imports in the background.
WebSockets with Laravel Reverb for notifications, chat and dashboards that update themselves.
We take over existing Laravel projects, clean up technical debt and upgrade to the latest version.
We have our own packages for the Norwegian services most businesses need, so integrations go in quickly and safely.
BankIDSign-in and signing with the Norwegian national e-ID, over OIDC.
Vipps MobilePayPayments, recurring charges and sign-in.
Tripletex and PowerOffice GoOrders, invoices and payroll kept in sync with the accounting system.
Bring, PostNord and PorterbuddyShipping, labels and tracking.
The site you’re reading is built in Laravel with Inertia and React. This is how we took it from 90 to 100.

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.
Laravel is the most widely used PHP framework in the world, and it's what we use to build web applications, customer portals and APIs. Our developers have worked with Laravel since it launched in 2011.
We pick tools based on what the project needs. For many Norwegian businesses Laravel is a good choice: it's quick to get started, security is built in, and the code stays easy to maintain for many years.
Laravel works well when a system has a lot of business logic, related data in a database and integrations with other systems. Typical examples are customer portals, line-of-business systems, booking systems and SaaS products with sign-in, user roles and payments.
Most of what you need is built into the framework, including queues for heavy jobs, scheduled tasks, email, notifications, caching and authentication. That leaves more time for the parts that are specific to your business.
Laravel isn't always the answer, though. If you need a website with a lot of editorial content, WordPress is often a better fit. If you need to train your own machine-learning models, we build that part in Python and connect it to Laravel.
Plenty of people still think large systems have to be built in .NET or Java, and that PHP is only for simple websites. That isn't the case. VG, Norway's largest news site, and much of Schibsted run on PHP, and both Facebook and Slack started out on it.
Laravel builds on that with current PHP 8, typed code and thousands of ready-made packages. We use it for systems that handle many concurrent users and are as easy to change after five years as after five weeks.
The basics of a new system, such as sign-in, access control, database setup and email, are in place in Laravel from day one. In our experience that can cut development time by up to 50% compared with similar .NET projects:
As a result, more of the budget goes on the features users actually notice.
One of the first decisions in a Laravel project is how the frontend talks to the backend. With Inertia we build the interface in React, but the pages get their data directly from Laravel. You get one codebase, no separate API to maintain, and a web application that feels like an app. It works well for admin panels, customer portals and internal tools.
If a mobile app, partners or other systems need the same data, we build a standard API with Sanctum instead. We often end up with both: Inertia for the web application and an API for everything else.
Our hourly rate starts at NOK 1,500, and projects with a clear scope get a fixed price. The cost of a Laravel project depends mostly on three things: how many integrations it needs, how many user roles and permissions it has, and whether data has to be migrated from an existing system. After a short discovery phase you get an estimate, so you know what you're getting before we start.
Many businesses have a Laravel application that's a few years old and whose original developer has moved on. In that case we start with a technical review. We read the code, look at dependencies, tests and hosting, and give you a prioritised list of what needs doing. The list is yours to use, whoever ends up doing the work.
We upgrade one major version at a time, and before we start we write tests for the most important user flows. That's how even old Laravel 5 projects get safely up to Laravel 13 and PHP 8.5.
When an older PHP application moves to Laravel, we migrate it piece by piece. The old and new versions run side by side until everything has moved, so users don't notice the switch.
Almost every Norwegian system needs some of the same integrations. We have our own packages for the most common ones, so they're quick and safe to put in place:
Standard PHP boots the application from scratch on every request. With Laravel Octane and FrankenPHP it's loaded into memory once and stays ready:
We run the applications on Kubernetes in the EU/EEA, with automated deploys that don't cause downtime. Horizon shows how the queues are doing, and monitoring alerts us before users notice a problem. Read more about infrastructure and DevOps, or see how we reached 99.99% uptime with Kubernetes.
Laravel protects against the most common attacks, but security depends just as much on how an application is built and run. We keep the framework and packages up to date, scan dependencies for known vulnerabilities and give each user only the access they need.
Personal data is stored in the EU/EEA. We build in logging, deletion and data access requests so you can comply with GDPR. Interfaces are built to WCAG 2.2 AA, so they work for everyone and meet accessibility requirements.
Code should be as easy to change in five years as it is today, so we stick to a few habits:
Everyone on our team has more than ten years of experience. You won't get juniors on the project, and you won't lose time to handovers along the way.
These are the tools we use in most Laravel projects, layer by layer.
Wondering whether Laravel is right for your project? Book a chat and we’ll go through it together.
We find out why the system is needed, who will use it and what success looks like.
We sketch the data model, choose the technology and plan security, privacy and accessibility early.
You see working software often and can adjust course along the way.
Readable code, automated tests and a structure that’s easy to change later.
ongoingLaravel lets you build quickly and still copes with large systems. The framework is mature, the documentation is good, and there are ready-made packages for most needs. For PHP projects it’s often the safest choice.
Yes. We start with a technical review of the code, dependencies, tests and operations, and then propose the way forward.
Our hourly rate starts at NOK 1,500. Projects with a clear scope get a fixed price, and you get an estimate before we start.
New projects start on Laravel 13 and PHP 8.5. We upgrade older projects one major version at a time, with tests along the way.
It depends on the project. For admin panels and internal tools we often use Inertia with React. For mobile apps and integrations with other systems we build plain APIs.
We write tests with Pest, and a pipeline runs them before every deploy. New versions go out with zero downtime.
We can run the Laravel application on our own Kubernetes infrastructure, or set it up on Laravel Forge, Vapor or another cloud platform.
You own the code we write for you, and it can live in your own repository if you prefer.
Interfaces that load fast, work with keyboard and screen reader and are easy to build on.
APIs and integrations with Vipps, BankID, Altinn and accounting systems that hold up when other systems fail.
One team that owns the whole application, from data model and API to the interface users see.
Tell us about the project, and we’ll work out together whether Laravel is the right choice.