How we got Nina.care fast, reliable & nanny-approved

Nina.care: From Hiking Trails to High-Speed Childcare Solutions

I remember the day clearly: I was hiking in the Ardennes when I got the call. "Hey Arjen, can you help us with a nanny site?" At first, I pictured an elderly couple running a small, cozy childcare service. But when I got back from my hike two days later, I was in for a surprise: Nina.care was far from that image. It’s one of the fastest-growing Dutch startups, with a rapidly expanding international clientele.

The Mission: Revolutionizing Childcare

Nina.care isn’t just another nanny service. They’re transforming the (child)care sector with AI-powered matching algorithms, connecting families with childcare workers worldwide. Reliable, affordable childcare, on a global scale. But as with all startups, fast growth brings technical challenges.

The Problem: Growing Pain

Having worked with numerous startups, I knew what to expect. After a rapid growth phase, the weight of technical debt begins to show, especially with WordPress sites. As Nina.care scaled, added new features, and expanded internationally, their site slowed down, much like a toddler dragging their feet before nap time. It was clear that we needed to tackle the Core Web Vitals head-on.

The Approach: No Guesswork Allowed

To fix the issue, there was no room for guesswork. The first step? Implementing Core Web Vitals monitoring and Real User Monitoring (RUM) using Core/Dash. I always say, "If you’re not measuring, you’re just guessing". Core/Dash quickly confirmed my suspicions about how to fight the Core Web Vials regression on the site.

Back on the fast track

Armed with insights I summarized the steps needed to quickly improve the Core Web Vitals of nina.care. The actual implementation was done by their in-house developer.  I love working with in-house developers as that means I get to use their deep knowledge on the site's architecture and history.

In cases like this I like to work closely with the developers for a short period of time. I have to train, mentor and oversee the progress to ensure the developer uses his skills to implement the changes the right way. After a few intensive sessions, I was able to step back and trust that they could continue applying the insights to the rest of the site where it mattered most.

Results

By the end of our collaboration, Nina.care saw a 90% improvement in Largest Contentful Paint (LCP), drastically speeding up load times. We also eliminated the Cumulative Layout Shift (CLS) issue, which had previously caused the site to fail Core Web Vitals tests. Interaction to Next Paint (INP) improved by 45%, creating a smoother user experience.

Parents and sitters can now access the platform without delay, ensuring that Nina.care continues to provide the fast, reliable service their users need.

Key improvements:

• 90% Improvement in Largest Contentful Paint (LCP)
  
• 100% Improvement of the Cumulative Layout Shift (CLS)
  
• 45% Improvement of the Interaction to Next Paint (INP)

"Thank you so much for all that you have done from me and the boys!  You feel like a part of the company and I like it" - Jasmijn