WebsitesFast enough to rank.Clear enough to convert.
A Drasyo build is static-first: pages are generated ahead of time and served as HTML, so they load fast, work without JavaScript, and give crawlers and answer engines something to read on the first request rather than after a fetch.
Why it matters
Static-first builds ship as HTML: they load in under a second, work without JavaScript, and give engines something to read on the first request.
Structure before surface
Which pages exist and which question each answers is decided before a line of production code. Surface on a broken structure is wasted work.
Performance as a release gate
A build does not ship if it regresses Core Web Vitals. Speed is measured before launch, not noted as future work.
Motion added last, always optional
Every headline, paragraph and link is plain HTML. The atmosphere is layered on for devices that can carry it and switched off for anyone who asks.
The trade we make
Fast and findable usually costs visual ambition, because the effects that impress are the ones that block rendering. We separate the two: content and layout ship as HTML and CSS, and the atmosphere is layered on afterwards from a chunk that loads when the browser is idle.
The result is a site that is fully readable before the interesting part arrives, and identical in substance if the interesting part never arrives at all.
See pricing for how engagements are scoped and what the tiers include.
How we do it
How the work runs.
- Define
- Design
- Build
- Verify
- Publish
- Compound
Define
Which pages exist, what each one is for, and which query it should answer.
Design
Type, colour and layout resolved before a line of production code.
Build
Static routes, real HTML, motion added last and always optional.
Verify
Speed, contrast, keyboard access and structured data checked as gates, not hopes.
Built with
What this service is made of.
Interface
TypeScript
One language from the database call to the button, with the types checked at the boundary between them.
Astro
Ships HTML by default and JavaScript only where a component asks for it. This site is built with it.
Delivery
GitHub Actions
Tests, type checks and the performance and accessibility gates run on every push, not before a launch.
Cloudflare
Edge caching, DNS and protection in front of everything we host.
This service in practice
Case studies
Websites — fast, findable, designed FAQs
Still have questions?The ones we get asked.
Why static instead of a CMS-driven site?
Static pages are faster, cheaper to host, harder to break, and cannot fail to render because a database was slow. Content still lives in editable files with validated fields, so publishing does not require a developer — it just does not require a server at request time either.
Can the site still have heavy animation?
Yes, and it should be optional. On our own site every headline, paragraph and link is plain HTML that renders with the motion layer switched off entirely. Animation is added on top, gated on device capability and disabled for anyone who has asked for reduced motion.
What does 'Core Web Vitals as a gate' mean in practice?
It means a build does not ship if it regresses the metrics, rather than the metrics being measured after launch and noted as future work. In practice the biggest wins are self-hosted subset fonts, images with explicit dimensions, and not blocking first paint on anything decorative.
Start with websites?
Tell us what you are trying to grow. We reply with what we would change first.