This interview is with Devin Pfromm, Founder at Spirra Digital.

Devin Pfromm, Founder, Spirra Digital

Can you introduce yourself and tell us about your current role in web design and SEO services? What specific areas of expertise have you developed that set you apart in this field?

I’m a front-end developer and technical SEO specialist with over a decade in web development. I run Spirra Digital, a Webflow-based agency focused on strategic SEO and conversion-driven design. My core expertise is combining semantic SEO with high-performing Webflow builds, where I structure pages to align with how search engines process entities, intent, and topical relevance.

Unlike many designers or SEO practitioners, I bridge both worlds: writing clean, conversion-focused code while applying deep technical SEO and patent-level search insights. I routinely analyze Google and Bing search-related patents and have used that to help clients surpass 95,000+ monthly organic visits. My approach is data-driven, performance-focused, and built to turn websites into long-term growth assets rather than just digital brochures.

How did you get started in web design and optimization? Was there a particular moment or project early in your career that shaped the direction you’ve taken with responsive design and site maintenance?

I got started in web development over 11 years ago after being introduced to programming. It quickly became a passion. I spent late nights studying, experimenting with layouts, and testing performance improvements.

One early project that shaped my direction was a small website I built for a local business here in Grand Rapids, Michigan. After improving the structure, page speed, and mobile responsiveness, I saw immediate gains in rankings and conversions. That moment made it clear that effective design isn’t just visual, it’s also about many other technical implementations that are easy to overlook.

Since then, I’ve focused on responsive development, technical maintenance, and SEO-backed design strategy. Today, every site we build is optimized for both user experience and search performance, ensuring it not only looks great but also drives measurable business results.

When you take on a new web design project, how do you balance aesthetic appeal with technical performance and SEO requirements? Can you walk us through a recent example where you had to make trade-offs?

We start every web design project by first locking in the sitemap, defining page types, and completing content documentation. Once we know exactly which pages are needed, what each page must communicate, and how users should navigate the site, then we move into layout and design.

Our process isn’t design-first, it’s performance-first. We’ve seen clients rank and convert extremely well, even with an outdated design (their words). If a site is fast, accessible, well-structured, and strategically built with CRO principles, design becomes an enhancement rather than the primary focal point.

A recent example was a full redesign for a manufacturing company based in Grand Rapids. They wanted a high-impact visual approach with full-width imagery, motion effects, and embedded video. The initial concept looked impressive, but early testing showed a significant reduction in loading speed and Core Web Vitals performance. To correct this, we reduced image file sizes from roughly 20–30 megabytes down to around 150–350 kilobytes. We kept the same aspect ratios and visual layout, but accepted a slight decrease in sharpness to improve load times. We also scaled back heavier visual effects in the initial viewport to prevent delays in rendering. After these adjustments, the site loaded 45% faster and achieved a near-perfect PageSpeed score. While the visuals were marginally less intense than originally planned, the trade-off resulted in a substantially better user experience and stronger SEO performance.

Responsive design is now expected rather than optional. What’s one common mistake you see businesses making with their mobile experience, and what’s your go-to solution for fixing it?

A major issue on mobile is oversized imagery. It’s extremely common to see 1+ MB image files used throughout a site. They may look great on desktop, but on mobile, they add several seconds of unnecessary load time, which directly harms engagement, Core Web Vitals, and rankings. This is one of the most consistent issues I find across nearly every new project.

The simplest fix is to download the images and run them through a Python script that recursively minimizes and converts them to WebP. In most cases, WebP should be the default image format. It provides nearly identical visual quality at a fraction of the weight.

Maintenance packages often get overlooked until something breaks. How do you structure your maintenance offerings to be proactive rather than reactive, and what specific tasks do you prioritize monthly?

Most businesses view maintenance as a repair service, but we structure our care packages primarily for prevention. We treat maintenance the same way we treat optimization, ongoing refinement rather than occasional cleanup. Each month, we review core performance metrics, security status, SEO signals, and form accuracy, and we update anything that shows even early signs of issues. If a page begins loading a second slower than it did last month, or if a key CTA stops performing as well, we adjust before it becomes a problem.

We also monitor platform changes, browser changes, test conversion paths, and check for any vulnerabilities or indexing issues. With our care packages, we’re paid to keep things running smoothly, so waiting until something breaks to touch the project doesn’t make any sense to us. If you maintain a site the way you maintain rankings or conversions (continuously instead of reactively), it remains stable, competitive, and capable of producing results without interruption.

Site optimization can mean different things to different people – speed, conversions, or search visibility. When a client says their site ‘isn’t performing well,’ what’s your diagnostic process to identify the real bottleneck?

First, I clarify what “isn’t performing” means to them, because behind that statement, there’s always a measurable issue, whether it’s a drop in leads, a decline in rankings, or a rise in bounce rate. Once the problem is defined, I run an audit centered around the issue. If rankings are the issue, I conduct an SEO audit. If the problem is page load or errors, I run a technical audit. If conversions are low despite stable traffic and page speed, I review the messaging, layout, and user flow.

The process adapts to the problem. I don’t apply the same checklist to every site. Performance issues are almost always rooted in different causes, so diagnosis has to be specific before solutions can be effective.

You’ve mentioned using tools like GA, Hotjar, and Search Console together. For someone building their first comprehensive site optimization workflow, which metrics should they monitor first and why?

For most users, the focus should be on three metrics: traffic, engagement, and conversion rates. If traffic is stable but engagement drops, it signals an experience or messaging issue. If engagement is strong but conversions are weak, the friction is happening near the point of action. If traffic itself is declining, the problem is rooted in visibility rather than usability.

Once those baseline signals are clear, then tools like GA, Hotjar, and Search Console become incredibly useful, because they show why those numbers are shifting.

Many businesses launch a beautifully designed website and then wonder why it doesn’t rank. At what stage of the web design process do you integrate SEO considerations, and what foundational elements can’t be added as an afterthought?

I integrate SEO before design even begins. You can’t confidently design a site until core SEO decisions are made.

We start with keyword research to identify required pages and define their URLs. Once that’s clear, we lock in the sitemap and determine which page types are needed so wireframes can be structured properly. We then finalize content documentation, including internal linking strategy, before any design work starts.

When design begins, we already know page hierarchy, purpose, and how users and search engines should navigate the site. That gives the design team clarity instead of forcing them to retrofit structure later.

Some elements of SEO, like URL structure, semantic hierarchy, and internal linking, cannot be effectively added after the fact. It’s far more efficient to design around SEO than to optimize a design that was never built to rank.

Looking at the evolution from traditional SEO to AEO and AI-driven search experiences, how are you adapting your web design and optimization approach today to prepare client websites for tomorrow’s search landscape?

I’ve adapted by shifting SEO from keyword targeting to entity and intent targeting. AI-driven search rewards clarity, context, and authority, so we build pages that answer problems directly rather than just match query terms.

Structurally, this means using semantic HTML, reinforcing subject–attribute–object relationships or ‘triples’, and writing content that clearly establishes entities, their attributes, and their relevance to the topic. We no longer optimize copy for density, but we do optimize it for clarity of meaning. Every key page is designed to signal expertise, supported by author-level credibility, structured data, clean internal linking, and topical depth.

From a design perspective, we focus on making information easier to parse. Sections are structured to support conversational and summarization-based retrieval. Rather than building long, decorative layouts, we design with scannability and information hierarchy that aligns with how LLMs interpret relevance. We also prioritize site architectures that allow for expansion of related content clusters, since entity-based models favor depth of coverage over keyword density.

Thanks for sharing your knowledge and expertise. Is there anything else you’d like to add?

The only thing I’d add is that websites should be treated as ongoing assets, not one-time builds. The brands that win long-term are the ones that keep refining structure, content, and performance based on how users and search evolve. If the site is viewed as something you launch and then leave alone, it will inevitably fall behind.