Website

Ślusarstwo Floriańczyk

Craft we put our name to

How a family metalworking shop turned a business-card site into one call to action: the phone

A redesign for a family metalworking and welding shop: jargon and empty phrases cut out, real risk closed (10 high-severity vulnerabilities, GDPR), and the site reduced to the single action the business actually sells through — a phone call. A real client, consent granted.

10 → 0

High-severity vulnerabilities in dependencies

Visit site ↗

Client: Ślusarstwo Floriańczyk
Year: 2026
Tech stack: Next.js 16 · React 19 · TypeScript
Timeline: 4 days (redesign of an existing 2024 site)
Location: Otwock / Pogorzel Warszawska, Poland
Live version: florianczyk.com

01Context

Challenge

The old site advertised a service the company does not provide: four mentions of "locks" on the home page, when Floriańczyk makes gates, fences and steel structures. That was a bad SEO copy-paste — it pulled in traffic that would never call and confused the traffic that would. The headline stated the company name instead of what the company does, and the copy was full of "passion" and "comprehensive solutions" with nothing behind them.

On top of that sat real risk: 10 high-severity vulnerabilities in dependencies (with the site on next/image, they genuinely applied), GA4 collecting data with no consent and no privacy policy — GDPR exposure for a real business owner — and no measurement of the goal at all. There was no phone-click event, so nobody knew whether the site made the phone ring.

02Solution

Approach

We cut the lock jargon and the unbacked phrases — facts stay (the family name, the phone number, the experience, the actual products), marketing filler goes. In place of an adjective we introduced an angle: "one contractor — from measurement to installation", set against competitors reselling a catalogue standard. The hero was reduced to a single call to action: tap and call.

We closed the risk: migrating Next 14 → 16 removed the vulnerabilities (checked as low-risk before we started, not after), and a privacy policy with Consent Mode v2 put GDPR in order — analytics only starts after consent, and the advertising signals stay off because the company runs no ads. We added measurement of the right goal: the phone click as a named event. URL slugs were left untouched, so the redesign did not cost a single Google position.

03Proof

Results

10 → 0

High-severity vulnerabilities in dependencies

4 → 0

Mentions of a service the company does not offer

CLS — all 10 runs

84–540 ms

LCP in production

GA4 without consent → Consent Mode v2

GDPR put in order

The site is live, fully static, showing the client's real work instead of stock photography. Real risk is closed: 10 high-severity vulnerabilities → 0, and "locks" disappeared from the home page entirely. GDPR went from "GA4 with no consent and no policy" to Consent Mode v2 with a banner and a policy — we removed an exposure the owner did not know he had.

We say plainly what the redesign did not improve: performance (the page weight is the client's own video, which deliberately stays). The tempting "we made the site faster" would simply be untrue, so it is not in this case study. We are not quoting business metrics either — not because there were none, but because we installed the goal measurement together with the redesign. The first real business number (phone clicks over a clean period) will exist after roughly three months.

Real risk removed (10 high-severity vulnerabilities → 0, GDPR put in order) and the site reduced to one sales channel: the phone.

Desktop and mobile

One call to action: the phone

Someone looking for a metalworker wants to call, not read — on both screens the number stays within reach, while the work section shows the real thing instead of marketing.

Before and after

A real front page instead of an empty one

The old site said neither what the company does nor how to reach it. The new hero names the service immediately and puts the phone number in view — the first screen finally does work that no screen did before.