Websites & Frontend Systems

We build company websites in Danish, English and Ukrainian that load fast and pass every request on to the systems you already use.

Many small-business websites in Denmark are built once and then left alone: one language, a contact form that ends in an inbox nobody watches, and pages that search engines read as half empty because the text is painted in by JavaScript. We build them the other way round. Crawlers get real text in the HTML, every language has its own address, and a form hands the lead straight to your CRM, booking or automation.

Our own site is the reference: lynbro.dk is a static Node build in three languages, prerendered at build time, served with a strict Content Security Policy, and its contact form and AI chat run through our own n8n. If you only need a simple page you edit yourself, our product imin.dk is a website builder made for that.

What we build

Landing pages for one offer

A landing page has one job: turn a visitor from an ad, a post or a QR code into a request. We build it as one fast page with one form, no menu that leads people away, and a thank-you state you can count in GA4 or in cookie-free statistics. The form posts to a webhook, so the lead reaches your CRM or a Telegram chat within seconds instead of waiting in a mailbox. A lesson from msdf.dk: nearly every request came through one dedicated quote page, not through the forms on thousands of product pages, so that is where the effort goes.

Company websites with more than a brochure

A company site of five to thirty pages: services, cases, team, jobs, legal pages and a contact path that works on a phone. We fix the structure before the design, with one page per service you actually sell, so Google never sees ten pages that say the same thing. Privacy, cookie and terms pages exist in every language the site has. Analytics tags load only after consent, while server logs and form protection keep working regardless. lynbro.dk runs exactly like this: legal pages, careers, a price calculator and a blog in Danish, English and Ukrainian.

Multilingual sites

Danish, English and Ukrainian, or any other set, each on its own URL with hreflang, the translated text present in the HTML from the build, and dates, prices and numbers written the local way. Made for Danish firms with foreign customers and for Ukrainian-speaking businesses in Denmark.

Learn more →

Redesign of an existing site

A redesign starts by measuring what the old site does: Lighthouse score, page weight, Core Web Vitals, which pages bring visitors and which URLs must keep their address. For Oksana Kolesnyk Beauty Studio (oksana.dk), a WordPress site with a slider and an online booking plugin, the homepage went from a Lighthouse score of 34 to 68 and from 3.9 to 2.0 MB. Layout shift fell from 0.57 and 0.90 to zero, and a server page cache cut time to first byte from 1.0 to 0.15 seconds. Changed URLs get 301 redirects, so rankings follow the content.

Webshops

Online stores, checkout and payments have their own page under e-commerce: /en/services/ecommerce/. On a company website we add the smaller pieces, such as a price calculator, a paid booking or a Stripe payment link, without turning the site into a shop.

Learn more →

WordPress and CMS

WordPress when your team wants to edit pages themselves: a block theme, a short plugin list, and our own plugins from plugins.lynbro.dk where the usual ones are heavy or send visitor data elsewhere. Upgrades of large plugins are tried on a staging copy before they touch the live site.

Learn more →

Next.js and headless

Headless makes sense when the same content appears in several places or the site has outgrown a theme. We choose between a static build, a React app on an API and Next.js by how often your content changes, who edits it and how many pages there are.

Learn more →

SEO built into the build

We do not sell SEO as a monthly retainer; we build sites that search engines can read from the first day. That means text in the HTML rather than injected by scripts, hreflang between language versions, one canonical address per page, a sitemap that lists every language, JSON-LD for the organisation, breadcrumbs and FAQs, and an llms.txt for AI assistants. On lynbro.dk the Danish URLs once showed English text to crawlers, because translation ran in the browser; a prerender step in the build corrected every page in one pass. On msdf.dk a missing sitemap index was traced to an nginx rule.

What we have built in this area

lynbro.dk

Our own site: a static Node build that generates every page in English, Danish and Ukrainian, writes the translations into the HTML and ships with CSP and security headers. Contact form and AI chat run through our n8n behind Cloudflare Turnstile. Once the same web font stopped loading seven times and the cookie banner moved to an inline script, production LCP fell from 1,196 to 624 ms.

Møbler Samling / MSDF

A furniture-assembly service in Greater Copenhagen. On WordPress and WooCommerce we filled 7,510 pages, each a piece of furniture with a fixed assembly price, and removed the cart: every page carries a prefilled request form that goes to e-mail and an n8n webhook. Removing a bandwidth limit in the server configuration took first contentful paint from 12 to 2.2 seconds.

Oksana Kolesnyk Beauty Studio

A permanent make-up studio. We redesigned the oksana.dk WordPress site, made the homepage twice as light and keep it running: plugin upgrades are rehearsed on staging, and the reviews and social-feed plugins that are now part of our plugin suite ran on this site first.

andrii.dk

The founder's site on WordPress multisite with a block theme: fifteen pages, five each in Ukrainian, English and Danish. A script extracts only the text nodes for translation, so the markup cannot break, and caches every string, so a rerun translates only what has changed.

Tools we use for websites

Static sites: a Node build script, plain HTML, CSS and JavaScript, and Three.js where motion earns its weight. CMS sites: WordPress with a block theme, Polylang for languages and WooCommerce where products or prices live. Forms and chat run through n8n behind Cloudflare Turnstile. We host on our own nginx servers with page cache and security headers, and test with Playwright and Lighthouse at 375, 768 and 1280 px.

Prices

Landing page
from 2,000 DKK
Website up to 10 pages
from 6,000 DKK
Technical audit of an existing site
from 3,000 DKK
Hourly rate for changes
500 DKK/hour
Project support after launch
600 DKK/month

All prices are ex. VAT. The price depends on the number of pages and languages, how much text we write versus you supply, and which systems the forms must feed; you get a fixed quote after a free scoping talk booked through the contact form.

How a website project runs

1

Content and URL map

We list every page the site needs, its language versions and the old addresses that must redirect. One page per service you sell, nothing that repeats another page. You approve the map before any design work starts.

2

Design on real text

We design with your actual Danish and English copy, never placeholder text, because long Danish compound words and Cyrillic headings break narrow layouts. The phone view at 375 px is checked first, then tablet and desktop.

3

Build and connect

Pages, forms, booking or CRM links, consent banner, structured data and sitemaps. Every form is tested end to end: the request must arrive where you work, not just show a green message on screen.

4

Launch and follow up

We switch DNS, add 301 redirects for old addresses, submit sitemaps to Search Console and watch crawl errors and speed for the first weeks. Ongoing updates are available as project support.

Frequently Asked Questions

Do I have to supply the texts in all three languages?

No. You can give us Danish and we translate, or we write from a short briefing. Machine translation is used only for the first draft; every page is read through by a person before launch, and the words you use with customers stay the way you use them. Ukrainian is checked by our founder, who is a native speaker.

Can you move my old site without losing Google rankings?

Yes, if the move is planned. We crawl the old site, keep every address that has visitors or links, and redirect the rest with 301s to the nearest new page. Titles and descriptions move with the content, and after launch we follow Search Console for 404s and pages Google drops, fixing them as they appear.

WordPress or a static site?

It depends on who edits and how often. If your team changes pages every week, WordPress with a block theme is the sensible choice. If changes are rare and speed and security matter most, a static build is cheaper to host and has nothing to log into on the public server; we then make the changes for you at the hourly rate.

Can the site take bookings or payments?

Yes. A booking widget can be embedded on any page, either from our own product bkg.dk or a booking flow we build to order, and a Stripe payment link or checkout can be added for deposits or single products. Full webshops are described under e-commerce.

What happens after launch?

You can edit content yourself, order changes at the hourly rate, or take project support at 600 DKK a month, which covers updates, backups, uptime checks and small fixes. On WordPress sites, plugin and core updates are tried on a staging copy first.

⚡

Get an Instant Price Estimate

Use our interactive calculator to get an approximate price for your project in 2 minutes.

⚡ Calculate Price

Ready to Cross the Bridge?

Let's build your lightning bridge to digital transformation. From first consultation to live deployment — we move fast.

Get Started Today