Case

NOVOFRUCT SK

Over eighty products across several ranges plus two separate brands. The client supplied the design; our job was to turn it into a fast, manageable site.

Open novofruct.sk
Client
NOVOFRUCT SK
Sector
Food production, Nové Zámky
Year
2025
Role
Rebuild 1:1
Stack
WordPress, Elementor, custom CSS

Food production, Nové Zámky 2025

The brief

A food producer from Nové Zámky, making food since 1975. Over eighty products across several ranges — baby food, preserved vegetables, spreads, ready meals — plus the separate brands Ovko and DayUp.

The design arrived finished. What was missing was the working implementation that keeps a catalogue that size fast and at the same time manageable for people who are not developers.

What was solved

  • Turning the supplied design into a working WordPress site
  • A product catalogue with categories, ranges and separate brands
  • Content management for non-technical people
  • Speed with a large number of items and images

When the design arrives finished, and what that changes

On this project the visual design came from the client and our job was the implementation. That is not less work, just different work — and it has risks of its own.

A finished design almost never covers everything. The states nobody draws in a static file are missing: what a category with two products instead of twelve looks like, what happens with a long name, what the form looks like after it is sent. These things either get settled at the start, or they get settled during development according to whatever occurs to whoever.

We went through the design and named the missing states before any code was written.

How to manage a catalogue of over eighty products

Eighty products is the line past which a catalogue cannot be kept up by hand. On top of that Novofruct has several product ranges and two separate brands — Ovko and DayUp — which need their own presentation but share the same structure.

We built it on a custom content type with taxonomies for range and brand. In practice that means a new product is a filled-in form: name, image, description, classification. The categories fill themselves from the classification. Nobody has to add a product in three places by hand and remember everywhere it has to be deleted from.

This is the difference between a catalogue that is still current a year later and a catalogue nobody adds to any more because it is a nuisance.

Speed with a large number of images

A food catalogue is mostly photographs, and photographs are the most common cause of a slow site. The product photos come from the client at print quality — several megabytes, dimensions over four thousand pixels.

The fix has three layers. On upload, images are converted to WebP automatically and generated at several sizes, so a phone downloads a small version and not the same one the desktop sees. They load only once they come near the screen. And the product listing uses a cropped thumbnail, not a scaled-down original.

Without that, a category with twenty products would download tens of megabytes and would take several seconds to load on a mobile connection.

Content management for people who are not developers

The site is run by a person who works on marketing for a food company, not on WordPress. So the admin is cut down to what they actually need — add a product, edit text, swap a photo.

Everything else is hidden. Fewer options means fewer chances to break something and fewer questions they would have to ask someone.

What a company with a large catalogue can take from this

If you sell more than a few dozen items, the decisive question is not what the catalogue will look like, but who will be adding to it a year from now and whether it will be bearable for them. A catalogue that is hard to manage stops being current — and an out-of-date catalogue is worse than none, because it lies to the customer.

The second thing: deal with images at upload, not afterwards. Automatic conversion and resizing save more time and more speed than any later optimisation.

If you have a finished design and are looking for someone to build it, we do production from supplied designs.

How it turned out

The client runs the catalogue themselves — a new product is added through a form, not through code.

Live

Take the site for a spin

Scroll right inside the screen. Tap the screen, then scroll. Open the live site ↗

Full NOVOFRUCT SK homepage on desktop
Full NOVOFRUCT SK homepage on mobile

Contact

Want something like this?

A few sentences about the project are enough. You'll hear back whether it can be taken on, a rough timeline and what needs to be known next.

Write a brief hello@oneless.eu