A coastal cliff drawn in thin white facets above the sea, with a small red sun on the horizon. AI-generated image
Engineering

We Rebuilt ilscipio.com From Scratch with Kronk and Hugo

By Paul Piper 3 min read

Our company website ran on WordPress with the Divi theme for years. It worked. Pages loaded, the contact form sent emails, the blog had posts. But every time I opened PageSpeed Insights the numbers made me wince, starting with a page weight that had no business being that large for what was mostly text and a few images.

So we tore it down and rebuilt it with Kronk CMS running Hugo underneath.

Why Kronk and Hugo

I wanted a static site. No database, no PHP, no plugin updates, no security patches for a CMS I use as a glorified text editor. Hugo builds the entire site in under two seconds. The result is plain HTML, CSS and a bit of JavaScript. Caddy serves it. There is nothing to hack because there is nothing running.

But Hugo by itself is a build tool, not a content management system. It does not know about SEO constraints, accessibility rules, or how to keep an AI coding agent from breaking your site while editing templates. That is what Kronk adds. kronk init detected the Hugo project, set up guardrail files that Claude Code loads automatically, and gave us quality checks for title lengths, heading structure, alt text, contrast, and a dozen other things that are easy to get wrong across a whole site.

The migration itself started with kronk migrate wordpress. It pulled the XML export, stripped the Divi shortcodes, converted to Markdown, and mapped the image paths. Some pages needed manual cleanup where Divi had wrapped every paragraph in three nested divs for no reason anyone could explain, but the bulk of the conversion was automated.

The other reason was bilingual support. Our site runs in German and English. WordPress handled this with a translation plugin that added overhead to every page load and broke in creative ways every few months. Hugo has built-in multilingual support. Two content directories, one config file, done.

This blog runs on the same Hugo instance, managed through Kronk. Markdown files in a content directory, a reading-progress bar, related posts at the bottom, social cards generated at build time. Writing a post means creating a .md file and pushing to the production branch. No WordPress editor, no browser, no login. Kronk’s guardrails catch SEO and accessibility issues before the push. The source is version-controlled, every change has a commit message, and I can diff two versions of a page the same way I diff code.

URLs and redirects

Most pages kept their paths. The old dated blog URLs and 42 renamed pages got 84 permanent server redirects. I spent more time on URL parity than on the actual design. Getting a redirect wrong means a dead link in someone’s bookmark or a search result that goes nowhere. Not worth the risk.

What I underestimated

The contact form. WordPress has Contact Form 7. Hugo has nothing, because it is a static site generator. I ended up writing a small endpoint that receives the form POST, validates a Cloudflare Turnstile token, and sends the email. It works, but it took longer than expected because I had to handle spam protection from scratch instead of installing a plugin.

The cookie consent banner took too long as well. The old site used a WordPress plugin. The new site uses a lightweight consent layer that gates GTM behind an explicit opt-in. Getting the timing right so that analytics loads only after consent but the page does not flash or shift took several iterations.

The numbers

  • CLS: the new Hugo site measured 0.81 on the homepage at first. A performance pass with critical CSS per page type brought it to 0.
  • Page weight: cut roughly in half. Mostly from removing jQuery, Divi’s framework JavaScript, and converting images to WebP through Hugo’s asset pipeline.
  • Time to first byte: far lower than the 400-600ms we saw with WordPress hitting MySQL, running PHP and assembling the page, because Caddy serves a static file from disk.

If your site is mostly content, not a web application and not an e-commerce store, just pages and a blog, Kronk is worth a look.

ilscipio.com