A performance budget in CI
LCP, INP, CLS and bundle size checked on every pull request. A regression fails the build; it does not get discovered in production three weeks later.
Service 04
Web frontends that stay fast
Marketing sites, dashboards and customer portals built for Core Web Vitals, accessibility and the person maintaining it next year.
Softrear builds web frontends — marketing sites, customer portals and internal dashboards — with a performance budget enforced in CI, WCAG 2.2 AA compliance, and server rendering by default so the content is there without JavaScript.
Who this is for
- Your site fails Core Web Vitals and your competitors outrank you on it.
- Your dashboard is a 3MB bundle that takes eight seconds on site Wi-Fi.
- Your marketing team cannot ship a page without a developer.
What you get
Deliverables, not adjectives.
Server-rendered by default
Content in the HTML, JavaScript only where interaction genuinely requires it. It is faster, it is more accessible, and AI crawlers can actually read it.
Accessibility to WCAG 2.2 AA
Automated checks plus a real assistive-technology pass. Automated tools catch about a third of what matters.
A component library your team can use
Documented, typed, tested, with the states drawn — not a pile of one-off components.
Analytics that answer questions
Funnel events defined before the build, so the redesign argument next year is settled by data rather than opinion.
How it runs
- Set the budget and the target devices before the first component
- Build the content model, then components, then effects — in that order
- Ship behind preview deploys, one per pull request
- Baseline the vitals at launch and re-check quarterly
Tools & standards
We choose per project and write down why. A stack chosen because it is what the last team knew is a stack nobody can defend at review.
Questions we get asked
Which framework do you use?
Astro for content-led sites, because it ships almost no JavaScript. Next.js when there is a real application behind the login. We pick per project and we write down why.
Can our marketers edit it?
Yes, if you want a CMS. We keep the content model separate from the components from day one, so adding Sanity, Payload or Storyblok later is a wiring job rather than a rewrite.
The rest of the stack
01
Product design
Research, flows, a design system your engineers can actually build against — not a Figma file that dies at handover.
02Mobile
Flutter, React Native and native iOS/Android — shipped through the stores, instrumented, and supported after release.
03Backend & APIs
Domain modelling, event architecture, contract-tested APIs, and the unglamorous migration off the system you cannot turn off.
05Cloud & DevOps
Infrastructure as code, SLOs that mean something, a real on-call rotation, and a quarterly review of what it all costs.
06Managed support
SLA-backed support for systems we built and systems we inherited, with the metrics published to you monthly.
Tell us what’s stuck.
A senior engineer reads every one of these. If we’re not the right fit we’ll say so, and point you at someone who is.
Start the conversation
No spam, no drip sequence. A senior engineer replies within one business day.