WordPress / CMS
WordPress sites your team can edit, built lean, plus plugins we write ourselves when the usual ones are too heavy.
LynBro Plugins
WordPress plugins made for Danish sites: cookie consent, Danish address autofill for WooCommerce, anti-spam, SMTP mail, cache, security and more. Several are free on wordpress.org.
Most WordPress problems we are called in for are not caused by WordPress itself but by what has been piled on top of it: a page builder, a slider, three plugins that each load their own scripts, a security plugin with a pirated licence activator, and nobody left who knows which of them can safely go. The site gets slow, logins get locked, and every update becomes a gamble that someone puts off.
We build WordPress sites on a block theme with as few plugins as possible, WooCommerce when you sell, and Polylang when you need languages. Where an existing plugin is heavy, sends visitor data to third parties or costs a licence per site, we use our own. LynBro Plugins at plugins.lynbro.dk is our studio for WordPress plugins made for Danish sites: cookie consent, Danish address autofill, anti-spam, SMTP mail, caching, security headers, login protection and more, translated into Danish and Ukrainian. Several are published on wordpress.org after passing its manual review.
Before deciding what to build, we scanned the WordPress sites on our own servers: 16 installations running 161 different plugins. Every one of them paid for spam protection in some form, so anti-spam came first. On one renovation company's site all third-party plugins have since been replaced by ours. On one client site we found that the deliberately obscure admin username was exposed through the author archive and the users endpoint of the REST API; the site had received 125,572 login attempts from 1,820 IP addresses in three months, and the same hole was open on 11 other sites. A small must-use plugin closed it on all of them.
WordPress itself is free; what you pay for is hosting, any premium plugins and upkeep. A website with up to 10 pages starts from 6,000 DKK, and ongoing updates, backups and monitoring are available as project support at 600 DKK a month. Larger plugin upgrades are rehearsed on a staging copy before they reach the live site.
WordPress is the wrong tool for a single campaign page, where a landing page or our own builder imin.dk is faster, and for software with heavy business logic, such as booking with deposits and shared resources. That is better written as an application and embedded in the site.
Key Features
Block themes, short plugin list
Full-site editing with the core block editor; page builders only if your site already depends on one. Each plugin has to justify its weight and its data flows.
Our own plugins
Cookie consent, Danish address autofill, anti-spam with Turnstile, SMTP, cache, security headers, login protection and forms from plugins.lynbro.dk, run through Plugin Check before every release.
WooCommerce
Products, prices and request forms. When thousands of products change, the update runs as a batch on the server, so the site stays responsive and product URLs never move.
Languages with Polylang
Each language on its own URL with unique slugs, and translations linked to each other, so hreflang points to the matching page rather than the language's front page.
Security hardening
No user enumeration, a hidden login address, firewall rules, security headers that also cover static files, and file editing from the admin panel switched off.
Speed work
Server page cache, scripts loaded only on pages that use them, reserved space for sliders and widgets, and preloaded fonts and hero images to stop layout shift.
Why Choose This Service
The block editor handles text, images and new pages; we are only needed when structure or code changes.
A short plugin list means faster pages, fewer updates and fewer doors for attackers to try.
Our own plugins run on our own sites too, so a fix we make reaches every site we look after.
Several of our plugins are free on wordpress.org and replace per-domain licences for things like cookie consent and address autofill.
How We Deliver
Our proven process ensures quality at every step
Plugin and theme audit
For an existing site we list every plugin, what it loads and what data it sends out, and mark what can go. For a new site the plugin list is agreed before building.
Staging copy
All work happens on a staging copy with your real content. Upgrades of large plugins, such as booking or shop plugins, are tried there first with a backup ready to restore.
Build and harden
Theme, templates, content migration, Polylang or WooCommerce setup, then security: login protection, user enumeration closed, security headers and file permissions checked.
Measure and launch
Lighthouse and Core Web Vitals before and after, 301 redirects for every changed address, then go live and keep an eye on errors, uptime and form deliveries.
Frequently Asked Questions
Can you take over a WordPress site someone else built?
Yes. We start with a copy on staging, list plugins, theme, custom code and user accounts, and check for known vulnerabilities and leftovers such as old admin users or pirated licences. You get a short report of what we would keep, replace or remove, and nothing changes on the live site until you have agreed.
Do your own plugins lock us in?
No. Plugins on wordpress.org are released under the GPL, so the code is open and stays usable even if we stop working together. Settings are stored in the normal WordPress options, and switching to another plugin later is a configuration job, not a rebuild of the site.
Elementor or the block editor?
For new sites we use the block editor and a block theme: fewer scripts, no extra licence, and the editing experience is built into WordPress. If your site already runs on Elementor and works, we do not rebuild it for the sake of it; we keep it fast and make sure its widgets reserve their space while loading.
Is WordPress secure enough for a business site?
Yes, when it is kept up to date and the usual gaps are closed: user enumeration, guessable login addresses, outdated plugins and editable files. Security plugins can also cause trouble; we have seen a captcha plugin stop issuing tokens and lock both the owner and the editor out, which is why login protection gets a tested fallback.
Can you build a plugin just for us?
Yes. A private plugin is the right place for custom functions that would otherwise end up in the theme or in a code-snippet plugin, where they disappear at the next theme change. We write it to the same standard as our public plugins, with a settings page if needed, and charge by the hour or as a fixed price.
Ready to Cross the Bridge?
Let's build your lightning bridge to digital transformation. From first consultation to live deployment — we move fast.