Development
Fugro
Fugro’s corporate site suffered from slow load times and poor Core Web Vitals, affecting user experience and SEO visibility.
Year :
2025
Industry :
Geoscience
Client :
Fugro
Project Duration :
8 weeks



Problem :
For a company like Fugro, credibility and trust are tied to the precision of their work. Their clients make multimillion-dollar decisions based on Fugro’s expertise, so their digital presence needs to reflect the same standard of reliability and efficiency. However, their existing site was hampered by performance issues. These bottlenecks not only undermined the user experience but also risked their visibility in search rankings, limiting reach at a time when many potential clients begin their engagement online.



Solution :
To address Fugro’s performance and codebase concerns, I worked closely with a team of SEO and performance specialists to systematically diagnose and optimize the site. Using profiling tools like Lighthouse, WebPageTest, and Chrome DevTools, we identified and addressed key bottlenecks.
Key technical improvements included:
Image optimization and smart loading strategies
Reducing data payloads, dead code elimination, and more granular code chunking
Script loading and execution policies
Refactored data fetching strategies
Font subset creation and utilization
Middleware refactor and redirect strategy overhaul
Updated Content Security Policy (CSP) for security and compliance
Component style refactoring
These changes helped address performance concerns such as LCP, FCP, blocking scripts and requests, third-party scripting issues, unused JS, and unoptimized assets.
Each fix was carefully scoped and prioritized, balancing quick wins that delivered immediate improvements with deeper structural changes that ensured long-term maintainability. This systematic approach allowed the site to achieve its best possible Lighthouse scores while keeping the codebase organized, predictable, and easier to maintain for future updates.






Challenge :
Fugro’s existing codebase had several areas of concern that needed addressing. The GraphQL layer was undocumented, used inconsistent naming conventions, and was overly abstracted. This significantly impacted developer productivity and overall project velocity, as well as making errors a more common occurrence.
From a performance perspective, the challenge was taking an old site and achieving best-possible Lighthouse scores. Working with legacy code always involves complexity: seemingly trivial updates often aren’t when a codebase has aged and evolved without structural guardrails.
Another key challenge was balancing immediate progress with meaningful impact. Quick wins — like raising web vital scores — are important for building momentum and showing value to the client. But deeper structural issues often required us to slow down perceived progress in order to address root causes properly. Striking this balance depended heavily on clear communication with stakeholders and setting expectations around short- vs long-term improvements.
Profiling, diagnosing, and resolving these issues in collaboration with performance specialists not only advanced the project but also sharpened my expertise in site optimization and reinforced my ability to manage the technical and communication demands of performance-driven work.
Summary :
This project reinforced the value of systematic, data-driven problem solving when working with complex, evolving systems. By combining technical precision with careful prioritization, I was able to deliver lasting improvements for the client while refining my own expertise in profiling, optimization, and scalable architecture. The experience highlighted how thoughtful engineering decisions directly translate into tangible business value.



More Projects
Development
Fugro
Fugro’s corporate site suffered from slow load times and poor Core Web Vitals, affecting user experience and SEO visibility.
Year :
2025
Industry :
Geoscience
Client :
Fugro
Project Duration :
8 weeks



Problem :
For a company like Fugro, credibility and trust are tied to the precision of their work. Their clients make multimillion-dollar decisions based on Fugro’s expertise, so their digital presence needs to reflect the same standard of reliability and efficiency. However, their existing site was hampered by performance issues. These bottlenecks not only undermined the user experience but also risked their visibility in search rankings, limiting reach at a time when many potential clients begin their engagement online.



Solution :
To address Fugro’s performance and codebase concerns, I worked closely with a team of SEO and performance specialists to systematically diagnose and optimize the site. Using profiling tools like Lighthouse, WebPageTest, and Chrome DevTools, we identified and addressed key bottlenecks.
Key technical improvements included:
Image optimization and smart loading strategies
Reducing data payloads, dead code elimination, and more granular code chunking
Script loading and execution policies
Refactored data fetching strategies
Font subset creation and utilization
Middleware refactor and redirect strategy overhaul
Updated Content Security Policy (CSP) for security and compliance
Component style refactoring
These changes helped address performance concerns such as LCP, FCP, blocking scripts and requests, third-party scripting issues, unused JS, and unoptimized assets.
Each fix was carefully scoped and prioritized, balancing quick wins that delivered immediate improvements with deeper structural changes that ensured long-term maintainability. This systematic approach allowed the site to achieve its best possible Lighthouse scores while keeping the codebase organized, predictable, and easier to maintain for future updates.






Challenge :
Fugro’s existing codebase had several areas of concern that needed addressing. The GraphQL layer was undocumented, used inconsistent naming conventions, and was overly abstracted. This significantly impacted developer productivity and overall project velocity, as well as making errors a more common occurrence.
From a performance perspective, the challenge was taking an old site and achieving best-possible Lighthouse scores. Working with legacy code always involves complexity: seemingly trivial updates often aren’t when a codebase has aged and evolved without structural guardrails.
Another key challenge was balancing immediate progress with meaningful impact. Quick wins — like raising web vital scores — are important for building momentum and showing value to the client. But deeper structural issues often required us to slow down perceived progress in order to address root causes properly. Striking this balance depended heavily on clear communication with stakeholders and setting expectations around short- vs long-term improvements.
Profiling, diagnosing, and resolving these issues in collaboration with performance specialists not only advanced the project but also sharpened my expertise in site optimization and reinforced my ability to manage the technical and communication demands of performance-driven work.
Summary :
This project reinforced the value of systematic, data-driven problem solving when working with complex, evolving systems. By combining technical precision with careful prioritization, I was able to deliver lasting improvements for the client while refining my own expertise in profiling, optimization, and scalable architecture. The experience highlighted how thoughtful engineering decisions directly translate into tangible business value.



More Projects
Development
Fugro
Fugro’s corporate site suffered from slow load times and poor Core Web Vitals, affecting user experience and SEO visibility.
Year :
2025
Industry :
Geoscience
Client :
Fugro
Project Duration :
8 weeks



Problem :
For a company like Fugro, credibility and trust are tied to the precision of their work. Their clients make multimillion-dollar decisions based on Fugro’s expertise, so their digital presence needs to reflect the same standard of reliability and efficiency. However, their existing site was hampered by performance issues. These bottlenecks not only undermined the user experience but also risked their visibility in search rankings, limiting reach at a time when many potential clients begin their engagement online.



Solution :
To address Fugro’s performance and codebase concerns, I worked closely with a team of SEO and performance specialists to systematically diagnose and optimize the site. Using profiling tools like Lighthouse, WebPageTest, and Chrome DevTools, we identified and addressed key bottlenecks.
Key technical improvements included:
Image optimization and smart loading strategies
Reducing data payloads, dead code elimination, and more granular code chunking
Script loading and execution policies
Refactored data fetching strategies
Font subset creation and utilization
Middleware refactor and redirect strategy overhaul
Updated Content Security Policy (CSP) for security and compliance
Component style refactoring
These changes helped address performance concerns such as LCP, FCP, blocking scripts and requests, third-party scripting issues, unused JS, and unoptimized assets.
Each fix was carefully scoped and prioritized, balancing quick wins that delivered immediate improvements with deeper structural changes that ensured long-term maintainability. This systematic approach allowed the site to achieve its best possible Lighthouse scores while keeping the codebase organized, predictable, and easier to maintain for future updates.






Challenge :
Fugro’s existing codebase had several areas of concern that needed addressing. The GraphQL layer was undocumented, used inconsistent naming conventions, and was overly abstracted. This significantly impacted developer productivity and overall project velocity, as well as making errors a more common occurrence.
From a performance perspective, the challenge was taking an old site and achieving best-possible Lighthouse scores. Working with legacy code always involves complexity: seemingly trivial updates often aren’t when a codebase has aged and evolved without structural guardrails.
Another key challenge was balancing immediate progress with meaningful impact. Quick wins — like raising web vital scores — are important for building momentum and showing value to the client. But deeper structural issues often required us to slow down perceived progress in order to address root causes properly. Striking this balance depended heavily on clear communication with stakeholders and setting expectations around short- vs long-term improvements.
Profiling, diagnosing, and resolving these issues in collaboration with performance specialists not only advanced the project but also sharpened my expertise in site optimization and reinforced my ability to manage the technical and communication demands of performance-driven work.
Summary :
This project reinforced the value of systematic, data-driven problem solving when working with complex, evolving systems. By combining technical precision with careful prioritization, I was able to deliver lasting improvements for the client while refining my own expertise in profiling, optimization, and scalable architecture. The experience highlighted how thoughtful engineering decisions directly translate into tangible business value.


