Font and layout · Copenhagen
Copenhagen: the type arrives late and the page jumps
On a studio site the typography is the work, and it is also the most common cause of a page rearranging itself under the reader's thumb.
The short answer
Cumulative layout shift is the vital that catches design-led sites, and web fonts cause most of it. A face that loads after first paint swaps in at a different metric, the text reflows, and the reader loses their place. The good threshold is 0.1, and it is reached by decisions made in the stylesheet rather than by buying a larger plan.
The hosting side of it is real but narrow: serve the fonts from the same origin as the page so there is no second DNS lookup and handshake, put them behind the LiteSpeed cache with long expiry, and keep the NVMe read out of the critical path. Everything else is font-display, preload and subsetting.
By the HostingFast team · Reviewed 12 August 2026
Free
Migration in, engineer-run
24/7
Human answers
Daily
Backup cadence
$0
To get started
A country that exports design as a discipline: furniture makers and architecture practices with global influence, a restaurant scene that changed how the rest of the world thinks about dining, and a working culture that ships serious work at bicycle pace.
The websites are correspondingly quiet and typographic, which produces a specific failure. This page covers how to measure the shift, why the fonts cause it, what self-hosting buys you, and where .dk and the certificate sit in the sequence.
Measure the shift, do not eyeball it
Layout shift is hard to see and easy to measure. Read the cumulative layout shift figure in the field data at the top of a PageSpeed Insights report, then reproduce it in the browser's performance panel with the layout shift regions overlay turned on. The panel will highlight the exact block that moved and the frame it moved in.
On a studio site the answer is almost always the same: a heading in a display face, rendered first in a fallback with different metrics, then re-rendered when the real file arrives. Images without width and height attributes are the other half of the list, and both are stylesheet-level fixes rather than infrastructure ones.
Fonts: what actually stops the jump
Three changes cover most of it. Preload the one or two faces used above the fold so the request starts early. Set font-display so the browser has a defined behaviour instead of an improvised one. And match the fallback stack's metrics to the real face as closely as the tooling allows, so that when the swap happens the line breaks do not move.
Subset ruthlessly while you are there. A Latin subset of a display face is a fraction of the full file, and no Danish studio site needs the Cyrillic range shipped to every visitor. Weight for weight, this is the cheapest speed work on a typographic layout.
Why self-hosting the fonts pays here
A font served from a third-party host costs a DNS lookup, a TCP handshake and a TLS negotiation before the file transfer even begins, and none of that is shared with the connection already open to your own site. Move the files onto the account and they arrive on the connection that is already warm, from NVMe storage, behind a cache that will hold them for as long as you tell it to.
It also removes a dependency you cannot fix at two in the morning. When a third-party font host is slow, your typography is slow, and there is nothing in your control panel that changes it. Self-hosted files sit in the same backup as everything else and restore from the panel in minutes.
.dk, TLS and the first connection
Danish commerce runs on .dk and reads it without deliberating. It registers alongside the hosting on a single account with one renewal date and DNS aimed correctly from the start, and the free SSL certificate issues as soon as the name points here and reissues before it can lapse.
That matters more than it sounds on a font-heavy page. Every additional hostname in the critical path is another handshake before rendering can settle, so a design that draws pages, images and type from one origin genuinely paints sooner than one scattered across four.
The parts of this a host can honestly claim
Fonts, images and markup served from one origin on NVMe storage behind a LiteSpeed cache, with free SSL issued automatically so nothing in the critical path waits on a certificate.
Plus somewhere to try the change first: staging copies, daily backups restored from your own panel, and no setup charge for any of it.
- One origin for type, images and markup
- Server-level caching with long expiry on static files
- Staging copies for testing a type change first
- .dk registered and renewed on the hosting account
Why HostingFast
Standard on every plan
One warm connection
Serving fonts from your own domain means the type arrives on a connection the browser has already opened rather than negotiating a new one.
Static files held properly
The LiteSpeed cache in the server holds subsetted font files with long expiry, so a returning reader pays for them once.
NVMe under the read
Disk speed decides how quickly an uncached asset is found and sent, so NVMe is standard on every tier rather than reserved for the top one.
Try it on a copy first
Staging copies let a typeface swap be measured against the live figures before any reader sees the page move.
Nothing to pay to begin
No setup charge on any plan, so testing the arrangement costs the tier and nothing beyond it.
Migration handled for you
Our engineers bring the site across free, keep the old one serving while they do, and wait for your approval before DNS moves.
Quick Start
From order to online
- 1
Get the shift figure
Field CLS from PageSpeed Insights, then reproduce it in the performance panel with layout shift regions on so you can see which block moves.
- 2
Bring the type in-house
Subset the faces, self-host them on the account, preload what is above the fold, and set a defined font-display behaviour.
- 3
Re-measure and keep the record
The same URL, the same tool, the numbers written down. Field data lags a change by weeks, so note the date you shipped it.
Built In
Loaded onto every plan
- Fonts, images and markup served from a single origin
- LiteSpeed caching inside the server rather than added by plugin
- Built-in WebP conversion for the imagery beside the type
- NVMe disks as standard, whichever tier you land on
- Staging copies for testing a typographic change first
- Daily backups with self-service restores from the panel
- Free SSL on every plan, reissued before it can lapse
- Zero setup charges, so trying a tier costs only the tier
- Mailboxes under your own name, included in the tier
- Human support on duty at every hour, on the awkward questions too
Frequently Asked
What people ask us most often
Our whole identity is one licensed display face. Does self-hosting break the licence?
That depends on the foundry, and it is worth reading before you move the files rather than afterwards. Most web licences permit self-hosting explicitly and many require it; a few tie you to the foundry's own delivery. If yours does, keep the third-party origin for that one face, self-host everything else, and preload the licensed file so the request at least starts early.
Is a layout shift really worth a redesign argument?
It is worth a stylesheet argument, not a redesign. The three fixes — preload, a defined swap behaviour, and a fallback whose metrics roughly match — usually take an afternoon and do not change a single design decision. What they change is whether the reader's eye has to find its place twice.
The site is mostly full-bleed photography. Where does that leave the type?
Competing for the same connection, which is the practical reason to fix both together. Convert the imagery to WebP at display dimensions so it stops crowding out the font request, give every image explicit width and height so its box is reserved before it arrives, and preload only the hero. Then measure, because on this kind of layout the two changes are hard to separate by eye.
Where do we test all this without touching the live site?
On a staging copy. Clone the site, make the type and image changes there, and run the same tests against the copy before pushing anything across. Daily backups sit behind that as the second net, restorable from the panel in minutes rather than through a queue, which is the difference between a bad Tuesday and a bad week.
Keep reading
Hosting in Denmark
Rates in DKK, which domain endings we can register there, and how the tax works out.
Web Hosting in Warsaw
Warsaw, where the same page-weight arithmetic meets a longer round trip.
Web Hosting in Istanbul
Istanbul, and what a two-language catalogue does to the same budget.
How to Test Your Website Speed
The walkthrough for running these measurements yourself, step by step.
VPS Hosting
KVM virtual servers with root access, if a studio outgrows shared limits.
Domain Names
Registering and pointing the .dk, on the same account as the hosting.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Stop the page moving.
One origin for type and images, server-level caching in front of both, and staging to prove the change on.
View VPS Hosting plans