KiriminAja Homepage

From "just one page in the monolith" to its own proper home

KiriminAja.com is the main front door to the whole KiriminAja ecosystem. It is where people get their first impression, learn what we do, and decide whether they want to trust us with their shipping flow. That sounds simple, but the old version lived inside a Laravel monolithic project that was busy handling many other product concerns too. Not just technical concerns. Business concerns. Operational concerns. The full "everything lives here" starter pack.

So yes, the homepage used to be part of a system that had way more on its plate than a marketing site should ever need to think about.

Why we moved it

As KiriminAja kept growing, the homepage needed to move faster than the old setup allowed. Landing pages, content sections, experiments, visual polish, and performance improvements should not need to queue behind unrelated product logic hiding in the same codebase.

We wanted the homepage to feel like a proper product surface of its own:

• fast to iterate
• easier to maintain
• cleaner to deploy
• more fun to design without poking the sleeping giant inside the monolith

That is where Nuxt came in.

Porting the homepage to Nuxt

We rebuilt and ported the main homepage into a Nuxt application, separating the public-facing web experience from the older Laravel monolith. The goal was not to throw away the history of the previous system, but to give the homepage a stack that actually fits its job.

Nuxt gave us a much better foundation for:

• structured and reusable UI sections
• smoother routing and rendering for content-heavy pages
• better control over performance and page delivery
• a frontend workflow that feels modern instead of "please do not touch this file unless you are emotionally prepared"

The result is a homepage that is easier for the team to evolve, while still staying connected to the larger KiriminAja product story.

Measurable improvements

The migration was not just about making the code feel nicer to work with. We also saw real gains on the output side.

• SEO performance improved by up to 3x compared to the previous version
• PageSpeed scores moved from roughly 60 to a range of 80-99
• overall build size became roughly 2x smaller
• developer experience got noticeably better, even if the setup is still not perfect

It is not some magical "all problems solved" rewrite story, because that would be suspicious. But it is meaningfully better than before, especially for DX. The team can move with less friction, and the homepage now behaves more like a focused frontend product instead of a side quest inside a giant monolith.

The monolith was real

This was not one of those situations where people call a project a monolith just because the repository had more than three folders.

This was a literal monolithic Laravel project with multiple purposes living together in one place. Website concerns sat near other product concerns, and over time that naturally created friction. Updating the homepage could mean navigating decisions and dependencies that had nothing to do with the homepage itself.

Porting the site out of that environment gave us cleaner boundaries. The homepage can now focus on being a sharp, high-performing marketing experience, while the older system can keep doing the heavier operational work it was originally carrying.

Tech stack

• Nuxt for building the main frontend experience with a clean component-based structure
• TypeScript for safer refactoring and less guesswork while evolving the codebase
• Tailwind CSS for a fast and consistent UI workflow
• Laravel as the previous home of the website before the migration into a dedicated frontend app

What changed for the team

Moving the homepage into Nuxt made the work feel lighter in the best way. It became easier to ship visual updates, tune sections for clarity, and keep the codebase focused on what a homepage is supposed to do: communicate value quickly and look good while doing it.

The new KiriminAja.com is still the same brand entrance, but now it runs on a stack that matches its purpose. Cleaner separation, faster iteration, and way less monolith gravity.

That is a win for engineering, a win for the product team, and honestly, a win for everyone's blood pressure.