JakuninOleg

01 / Corporate website / industry

KEMZ Making complex manufacturing clear

I urgently rebuilt the factory website as a B2B sales tool: bold industrial design, an equipment catalog, technical inquiries, a CMS, and SEO — from concept to launch.

Explore case
Actual screen of the updated KEMZ website
Project / design / development / CMS / SEO01 — 10
Corporate websiteNext.js + OJ CMSCatalog and inquiriesVisit website ↗

02 / Before and after

Strong manufacturing. A weak digital front door.

The former site had a side menu, rotating product banner, and long factory introduction. Engineers and buyers had to search for the right machine, its specifications, and a way to make a technical inquiry. I rebuilt the structure around those tasks.

Before / 201926.12.2019
The former first screenScattered navigation and a generic template buried the essentials: specific equipment and the customer's next step.
Todayaokemz.ru
Updated KEMZ home page with a catalog link and key company data
A clearer routeLarge typography, real machinery, and signature blue. The first screen leads to the catalog, documents, and an inquiry with project parameters.
Mining excavator

03 / Context

The site slowed the journey from equipment model to inquiry

According to the KEMZ team, the former site loaded slowly, converted too few relevant visitors, and gave product pages little search visibility. Forms let spam through, while some important inquiries failed to reach sales. This needed a fast, complete rebuild of the customer journey, not a cosmetic update.

What blocked inquiries
  • Slow mobile loading
  • A confusing route to a model
  • Spam and missed inquiries
  • Weak search visibility

04 / Solution

From a factory problem to a working sales tool

Design concept, development, content, and deployment in one fast delivery.

01

Bold industrial design

I removed the old template's visual noise. Oversized type, quarry textures, signature blue, and real machinery convey the scale of production without obscuring technical details.

02

Catalog and CMS

I built the category-to-model journey and integrated OJ CMS on Payload for products, categories, news, documents and publishing states.

03

Inquiries without spam

I created a technical inquiry with equipment parameters, field validation, and spam protection, then routed requests to the right team.

04

Speed and search

I optimized loading, mobile experience, and Core Web Vitals, then prepared product-page structure, metadata, and a sitemap for search engines.

05 / Details

From catalog to technical inquiry

Engineers and buyers can start with a product category, inspect a model's specifications, and send the factory the requirements of their project. These are fragments of that interface.

01 / Find equipmentSearch, categories, and filters narrow the list to relevant models.
02 / Inspect a modelA product page brings together the description, technical data, and an inquiry action.
03 / Send requirementsThe form carries equipment type, machine model, and required power.

06 / RESEARCH AND CONTENT

Understand the factory before speaking for it.

The old site did not explain enough about the company or its production. I studied KEMZ’s history, product range and teams before shaping the new site structure and copy.

01 / INTERVIEWS

Learn from the people behind production

I spoke with the CEO and people in marketing, production and sales to learn what customers need before they contact the factory.

02 / EDITORIAL

Turn knowledge into useful pages

I helped write the copy and select imagery. The site gained useful company and production pages, alongside news the team can update.

03 / POSITIONING

Show scale without corporate filler

Imagery, structure and copy work together to show real machines, engineering expertise and a direct path to the right model and technical team.

07 / Behind the scenes

Built to work after launch

I planned not only the public pages, but also how the team updates the catalog, receives inquiries, and grows search visibility.

How I build catalog websites ↗
CONTENT / CMS

Editing without a developer

I adapted OJ CMS on Payload to the KEMZ catalog. The team edits products, categories, news and documents, with separate draft and publishing actions for product changes.

LEADS / FORMS

An inquiry with context

Form inquiries are saved in the CMS before email notifications are sent. Editors can view inquiries; administrators handle processing and deletion.

SEARCH / SEO

Pages for each product line

Categories and models have their own URLs, titles, and descriptions; the site also provides a sitemap, canonicals, and structured data.

OJ CMS / LIVE AT KEMZ

Catalog, inquiries and analytics in one dashboard

For the KEMZ website on Next.js and React, I integrated Payload and adapted OJ CMS to the factory’s workflows. These are actual implementation screens.

Live KEMZ OJ CMS dashboard: products, categories, news, recent changes and inquiries
Actual KEMZ interface · October 2026. Personal inquiry data is not shown.

Content and catalog

Products, categories, news and documents live in OJ CMS, built on Payload. Content has publishing states, and product edits can be saved as drafts.

Inquiries in the CMS

Website inquiries are saved before an email notification is sent. Editors can view them; processing and deletion are reserved for administrators.

Analytics alongside content

The Yandex Metrika API brings visitors, visits, page views and popular pages into the dashboard, with a selectable reporting period.

KEMZ product editor with category, image, draft and publishing controls
Product editing: fields for a technical catalog and a separate publishing action.
KEMZ Yandex Metrika data in OJ CMS: visits, views, chart and popular pages
This analytics snapshot illustrates the dashboard, not sales growth.

08 / A DETAIL THAT STILL WORKS

Even a dead end offers a way forward

I designed the 404 page in the factory’s visual language, with clear routes to the homepage and catalog. An old or mistyped link can still lead a visitor to equipment or an inquiry.

Open the 404 page ↗
KEMZ engineering artwork on the 404 page
404Page not foundHome → Product catalog →

09 / Outcome

Faster. Clearer. Closer to an inquiry.

The website brings the catalog, technical inquiries and team workflows together in OJ CMS.

Before ≈60–70After 95
PageSpeed Insights / Mobile23.09.2026
95
Performance
100Accessibility
96Best practices
100SEO
1,7 сFCP
2,5 сLCP
0 мсTBT
0CLS
4,2 сSpeed Index

10 / Client feedback

“Thank you for the fast turnaround. The new site helps us present our equipment and receive more precise customer inquiries.”

Alexey P.Head of Marketing, KEMZ