---
title: "Figma to a custom WordPress theme with ACF · Case study"
description: "teknovud.com case: a Figma redesign built as a custom WordPress theme with 182 ACF fields, two languages with Polylang and an accessibility and SEO audit."
url: https://lazarosantana.dev/en/cases/teknovud/
---

case 04 · corporate website · custom solutions

# From a Figma design to a *WordPress* theme

teknovud.com is the website of a custom software company, in Spanish and English. A designer redesigned the site in Figma and I took it to WordPress: templates, editable fields, filters and effects. Afterwards we audited the theme for accessibility, SEO and performance.

[View live site](https://teknovud.com) [How I built it](https://lazarosantana.dev/en/cases/teknovud/#recorrido)

*teknovud.com*

Home page of teknovud.com, a corporate website for a custom software company

**182** ACF fields in 9 groups

**100*·*100** accessibility and SEO

**87** Perf.

**100** Access.

**100** Best pr.

**100** SEO

Mobile Lighthouse · teknovud.com in production

Client

Teknovud, a custom software and business solutions company

Starting point

Base theme from 2021 built by the original team; the Figma redesign is by a designer

My role

Turning the design into code since January 2026, and auditing the theme

Languages

Spanish and English with Polylang, one theme, two sites

// the challenge

## A new design on an old theme

The original theme was years old and the company wanted a different site: a new home page, three service pages and a catalog of web templates with filters. All editable from the admin, in two languages, and faithful to the designer's Figma.

Once the design was live came the second part: measuring the theme, closing the accessibility and SEO gaps and cutting down what was heavy.

01

### Fidelity to Figma

Home, three services, contact, collaboration models and catalog, with the same spacing and the same effects as the design.

02

### Editable content

Every section has its fields in the admin. The team changes texts and images without touching code.

03

### Two languages

Spanish and English with the same templates. Menus, texts and settings fields are translated with Polylang.

04

### Measured quality

The accessibility report found 24 issues, 6 of them critical, and the best-practices audit flagged 13 failures.

// walkthrough

## From Figma to production

Six steps, from the designer's design to the audited site. Scroll down and follow them in order.

01 · design to code

### Each frame, a template

I started from the designer's Figma. Each screen became a PHP template, the styles became Tailwind 3 classes and the interactions became JavaScript, like the 3D effect on the cards.

Figma design · by the designer templates and styles · built

02 · fields and templates

### Everything is edited from the admin

Nine ACF field groups cover the home page, the three services, contact, the collaboration models and the catalog. Services and web templates are custom post types.

ACF groups · built ACF Pro · third-party

03 · catalog

### A filter that doesn't reload the page

The web template catalog is filtered by category with AJAX, with a nonce and input sanitizing. On mobile it loads two templates per page and on desktop six.

inc/ajax.php · improved templates-all.js · built

04 · accessibility and SEO

### Auditing the theme from the inside

The auditors found 24 accessibility issues, 6 of them critical, and ran 33 SEO checks. The result: a skip link, a clean heading hierarchy, escaped output and breadcrumbs.

templates · improved Rank Math · configured

05 · performance

### Less CSS, WebP images

Production CSS went from 211 to 155 KB after removing 9,722 unused lines. Images are served as WebP with srcset, non-critical CSS is deferred and fonts are preloaded.

inc/performance.php · built Tailwind 3 · improved

06 · forms

### Notices Turnstile doesn't wipe

The contact form uses Contact Form 7 with Cloudflare Turnstile and a honeypot. Turnstile reset the form and wiped the error notices, so the theme moves that reset to a different event.

Contact Form 7 · improved Turnstile · third-party

**from design to theme** step 1 / 6

Figma frame PHP template

Spacing and color Tailwind classes

Texts and images ACF fields

Cards with 3D effect main.js

Mobile screens dedicated image

**fields and templates** step 2 / 6

**9** ACF field groups

**182** fields to edit the content

**3** service pages, each with its template

**2** custom post types

top-level fields of the exported groups

**catalog filter** step 3 / 6

Click on a category templates-all.js

Request with nonce admin-ajax

Template query 2 or 6 per page

New cards without reloading done

**accessibility and SEO** step 4 / 6

**24** accessibility issues, 6 critical

**33** SEO checks, 0 errors

**100** accessibility on mobile, today

**100** SEO on mobile, today

July 2026 reports; October Lighthouse in production

**performance** step 5 / 6

**211→155 KB** production CSS, 9,722 fewer lines

**−588 KB** images in WebP with srcset

**−220 KB** backgrounds in WebP

**−740 ms** non-critical CSS deferred

savings estimated by PageSpeed when applying each fix

**contact** step 6 / 6

*Enter a valid email address*

Cloudflare Turnstile **verified**

submit → Contact Form 7 validates

→ the error appears under each field

**✓ Turnstile resets without wiping the error**

// real problems

## What breaks while optimizing

Six cases taken from my commits on this project. Each card carries the commit that fixed it.

`feat · 14c33054` built

### A 211 KB CSS file, mostly unused

Tailwind compiled without purging left 9,722 dead lines. The production build purges per template and the file drops to 155 KB.

`revert · 0bf3ad5e` improved

### Rewriting to vanilla JavaScript broke the 3D effect

I moved `main.js` from jQuery to vanilla JavaScript to save weight and the cards stopped tilting. I reverted it and moved jQuery to the footer so it doesn't block rendering.

`fix · 41b56cf8` improved

### The mobile image leaked onto desktop

A bento card showed its mobile image on large screens. Also, a numeric field went through `wp_kses_post`, which is meant for HTML. Both fixed.

`perf · 5ec37324` improved

### A forced reflow and a slow LCP on mobile

PageSpeed flagged a JavaScript-forced reflow, the main image without priority and a font without preload. All three were fixed in one commit.

`fix · e51cd3ea` improved

### Turnstile wiped the form errors

The plugin reset its widget on the `submit` event and took Contact Form 7's notices with it. The theme listens to `wpcf7submit` to keep them.

`feat · a198a21e` built

### Filtering the catalog without reloading the page

Web templates are filtered by category with AJAX, with a nonce on the request and a different page size on mobile and desktop, decided by the JavaScript.

// under the hood

## What sits behind the site

Where a visit goes

visitor**Browser** in Spanish or English, on mobile and desktop

Teknovud team**WordPress admin** texts, images and settings with ACF, no code needed

search engines**Google** sitemap, hreflang and structured data from Rank Math

// server

### WordPress + teknovud theme

PHP templates*home, services, contact, catalog**built*

ACF groups*182 fields in 9 groups**built*

inc/performance.php*WebP, deferred CSS, fonts**built*

Tailwind 3*CSS purged per template**improved*

AJAX filter*web template catalog**improved*

ACF Pro + Polylang*fields and two languages**third-party*

build and review

Tailwind · PostCSS · npm Lighthouse · audit reports

bots**Cloudflare Turnstile** verifies contact form submissions

email**Fluent SMTP** form notifications reach their destination

cache**Page cache** caching plugin with Cloudflare in front

New Improved Existing

// method

## Measured, not assumed

### The cycle of each fix

Every performance change came from a report and went through the same measurement again. The work list was closed with eight fixes applied.

01**Measure** Lighthouse and auditors

02**Fix** one finding, one change

03**Measure again** and record the result

### Rules I left in the theme

**WebP images** with srcset, sizes and lazy loading

**Self-hosted fonts** WOFF2 with `font-display: swap` and preload

**Critical CSS inlined** and the rest deferred

**Requests with nonce** and sanitized inputs in the filter

**Forms with a double filter** Turnstile and honeypot against bots

// results

## The project in numbers

**182** ACF fields to edit everything without code

**100** in accessibility and in SEO on mobile, in production

**56 *KB*** less CSS in production, from 211 to 155

**2** languages, Spanish and English, with the same theme

Lighthouse measured on teknovud.com, in production, on mobile, from Chrome (private window), on October 19, 2026: performance 85 to 87, accessibility 100, best practices 100 and SEO 100. LCP 3.1 s, TBT 310 ms and CLS 0.009. The next thing I would tackle is blocking time (TBT).

WordPress PHP Tailwind CSS PostCSS JavaScript ACF Pro Polylang Rank Math Contact Form 7 Cloudflare Turnstile Lighthouse

// other cases

01 · store · Uruguay

### Online tickets for a water park

A sale that goes through four systems: payment gateway, electronic invoicing, QR tickets and gate control.

*acuamania.uy*

Home page of acuamania.uy, a ticket store for a water park

[Need something like this? → Custom WordPress theme from Figma](https://lazarosantana.dev/en/services/custom-wordpress-theme/)

[← all cases](https://lazarosantana.dev/en/#trabajo) case 4 of 4

// your project

## Want something like this for your business?

Tell me what you need. I reply within 24 hours and, if it is a fit, you get a fixed written proposal.

[Request a quote](https://lazarosantana.dev/en/contact/#form) [See services](https://lazarosantana.dev/en/services/)
