Projects
Projects
Real work, measured results. For each one: what was there, what I decided and what changed.
Online store with a slow catalog
Online store with a slow catalog
Starting point
The catalog took several seconds on mobile and visitors left before seeing a product.
What I did
- I measured load times, errors and the purchase journey before touching anything.
- I separated the frontend from the CMS and served pre-generated pages.
- I redid image processing and lazy loading.
Technical decisions
Server-side generation with caching instead of rendering everything in the browser: the catalog changes little and what mattered was the first impression.
Result
Loads in just over a second on mobile and less abandonment on product pages. [Replace with your real data]
A website no one could edit
A website no one could edit
Starting point
An outdated CMS meant calling support for any change. The team had stopped publishing.
What I did
- I reorganized the content around what a customer is looking for.
- I migrated to a maintained CMS and structured the templates.
- I trained the team to publish and translate on their own.
Technical decision
Phased migration with careful redirects, so as not to lose rankings earned in search engines.
Result
The team publishes in three languages and the site loads in under two seconds. [Replace with your real data]
Internal dashboard with scattered data
Internal dashboard with scattered data
Starting point
Every department in its own spreadsheet. No one had the full picture.
What I did
- I designed the data model with the team before coding.
- I built a single interface with role-based permissions.
- I set up automatic imports from existing sources.
Technical decision
A single internal API, so any future tool uses the same data.
Result
One single point of reference and less time cross-checking files. [Replace with your real data]
