feat · 14c33054builtA 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.
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.

Teknovud, a custom software and business solutions company
Base theme from 2021 built by the original team; the Figma redesign is by a designer
Turning the design into code since January 2026, and auditing the theme
Spanish and English with Polylang, one theme, two sites
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.
Home, three services, contact, collaboration models and catalog, with the same spacing and the same effects as the design.
Every section has its fields in the admin. The team changes texts and images without touching code.
Spanish and English with the same templates. Menus, texts and settings fields are translated with Polylang.
The accessibility report found 24 issues, 6 of them critical, and the best-practices audit flagged 13 failures.
Six steps, from the designer's design to the audited site. Scroll down and follow them in order.
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.
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.
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.
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.
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.
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.
top-level fields of the exported groups
July 2026 reports; October Lighthouse in production
savings estimated by PageSpeed when applying each fix
Six cases taken from my commits on this project. Each card carries the commit that fixed it.
feat · 14c33054builtTailwind compiled without purging left 9,722 dead lines. The production build purges per template and the file drops to 155 KB.
revert · 0bf3ad5eimprovedI 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 · 41b56cf8improvedA 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 · 5ec37324improvedPageSpeed flagged a JavaScript-forced reflow, the main image without priority and a font without preload. All three were fixed in one commit.
fix · e51cd3eaimprovedThe 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 · a198a21ebuiltWeb 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.
Where a visit goes
Every performance change came from a report and went through the same measurement again. The work list was closed with eight fixes applied.
font-display: swap and preloadLighthouse 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).
Tell me what you need. I reply within 24 hours and, if it is a fit, you get a fixed written proposal.