Cydrion needed a website from scratch. Not a redesign — a birth. A new company entering the ISP support space with no existing brand, no existing trust, and a technical audience that would judge them instantly.
The typical design process would start with mood boards, brand workshops, and messaging frameworks. We started with a number: 0.6 seconds.
Why Performance Is a Brand Decision
Here's something most designers won't tell you: for a technical audience, load time IS trust.
An ISP support company's website that takes 4 seconds to load is making a statement — whether they mean to or not. It says "we don't prioritize what matters." A CTO evaluating a vendor doesn't consciously think "this site is fast, therefore they're competent." But they feel it.
Performance isn't a technical requirement you slap on at the end. It's a design constraint you start with.
The Stack Decision
Every design decision for Cydrion was filtered through one question: does this help or hurt performance?
- Custom iconography instead of an icon library — No Font Awesome import. No loading 2,000 icons when we need 12. Custom SVG icons, inlined, optimized.
- Responsive-first, mobile-priority — Not "design desktop, then adapt for mobile." Mobile was the baseline. Everything added on desktop was earned.
- Minimal JavaScript — No heavy animation libraries. No unnecessary dependencies. If it could be done in CSS, it was done in CSS.
- Next.js with static generation — Pre-rendered pages served as static HTML. The server doesn't lift a finger on the first visit.
- Image optimization — Every image was sized, compressed, and lazy-loaded. The hero image was WebP with AVIF fallback.
None of these are exotic. They're just decisions that get made when performance is a first-class constraint instead of an afterthought.
The Accessibility Dividend
The same constraints that produce fast sites also produce accessible ones. When you strip away unnecessary JavaScript and heavy frameworks, screen readers have an easier time. When you write semantic HTML with proper heading hierarchies, everyone benefits.
Cydrion scored 92% on accessibility on launch. Not because we ran an audit at the end — because accessible markup was baked into the component design from day one.
The "bonus" is that accessibility correlates with SEO, and SEO correlates with conversions. A site that works for everyone also ranks higher and converts better. The accessibility work wasn't charity. It was good product design.
What 0.6 Seconds Actually Feels Like
A 0.6-second load time means:
- The page is interactive before the user finishes reaching for their mouse
- No loading spinners. No skeleton screens. No "just a moment."
- Mobile users on 4G get the same experience as desktop users on fiber
- Google's Core Web Vitals are green across the board
It means the website doesn't get in the way of the message. And for a company whose business is making ISPs more reliable, that's exactly the right message to send.
The Lesson
I've worked on projects where performance optimization was a phase. "We'll make it fast in QA." It never works. Performance isn't something you bolt on. It's something you design for.
Cydrion's 0.6-second load time wasn't an achievement of engineering. It was a design decision. We chose to prioritize speed because for their audience, speed was the most honest design statement we could make.
Design isn't just what it looks like. It's how fast it loads.