Web interfaces that load fast and work for everyone
We build the part of a system that people see and use in a browser. That includes server-rendered sites, single-page apps, progressive web apps and web components. Each one is measured for speed, accessibility and search visibility before it goes live.
What we build
-
Server-rendered sites (SSR)
News portals, webshops and company sites where the page arrives ready from the server. This is the fastest route to content and the easiest for search engines.
-
Single-page apps (SPA)
Admin tools and dashboards where a user works for hours and the screen should react at once.
-
Progressive web apps (PWA)
Web apps that can be installed on a phone's home screen and keep working on a weak connection.
-
Web components
Self-contained interface elements that work in any page or framework. The animated illustrations on our own home page are one such component.
Work
-
Lasi.lv
A responsive news portal with search, ad serving and sitemaps for Google and Google News.
Read the case study: Lasi.lv -
E-klase
Interface design and front end for a daily education news portal.
Read the case study: E-klase -
Sils
A webshop with filters by technical parameters, product comparison and a three-step checkout.
Read the case study: Sils
Choosing the approach
The right technique depends on what the page is for. Content that has to be found and read quickly is rendered on the server with Twig, with small scripts added where the page needs to react. A tool that people work in all day can be a single-page app in React.
We choose the simplest solution that does the job. Less script means a faster page and lower maintenance costs.
Speed is measured
We set a budget for page weight and loading time before the build starts and check it with Lighthouse on a phone profile, where pages are slowest.
The usual gains come from images in modern formats and several sizes, fonts that do not block the first paint, scripts loaded only where they are used, and a CDN in front of the site.
Accessible to everyone
An interface has to work with a keyboard, a screen reader and at any zoom level. We check text contrast against the WCAG thresholds, give every control a name, and respect the reduced-motion setting of the visitor's device.
We check accessibility during the build, when fixes can still be made quickly.
Ready for search engines
A page is built so that search engines and AI models can read it. It has clean headings, a title and description, structured data, a sitemap, and language versions linked to each other.
Related services
A front end starts with design and depends on the back end behind it.
Is your site slow, or hard to use on a phone?
Send us the address, and we will tell you what we would fix first.