Case Studies: Web Performance, Email Security, and AI Search
These are the technical projects, written up in full — the starting condition, the work performed, and what it measured afterward.
Each one names the method rather than the result alone, because the method is the part that transfers to another business. Where a number appears, it is a number we measured and can show. Where we could not measure something, we say so.
Looking for the visual work instead? The portfolio shows the finished sites.
The Case Studies
Reliance — Client Case Study
A ground-up architectural rebuild. Reliance came to us on a legacy WordPress environment with a 34% mobile performance baseline and portfolio imagery the platform could not deliver efficiently.
We migrated the site to Duda on AWS, eliminating a large collection of third-party plugins, then optimized LCP and CLS directly, rebuilt the page structure with semantic HTML and JSON-LD, and re-engineered the mobile experience around how contractor searches actually begin.
34% → 90+
mobile performance score
96
Core Web Vitals pass rate
Duda / AWS
scalable platform architecture
DNS Cleanup and Email Authentication — Technical Case Study
When major email providers began enforcing strict sender requirements in 2024, legitimate business email — quotes, invoices, client communication — started being quarantined and rejected.
This is the standardized process we use to audit a domain's DNS and build its authentication layer: removing obsolete and conflicting records, consolidating SPF within DNS lookup limits, deploying DKIM, and implementing DMARC with alignment for third-party senders. It runs the same way whether the client is on Google Workspace, Microsoft 365, Zoho, or a third-party CRM.
SPF, DKIM & DMARC
authentication verified
Platform agnostic
implementation
Brand and domain reputation
protected against spoofing
Selected Work — Portfolio
The case studies above document what was engineered and what it measured. The portfolio shows the finished sites.
Only measured numbers.
Every figure on these pages comes from a tool output or a document we can produce. We do not publish estimated improvements, projected results, or industry averages presented as our own.
The method is named
A result without a method is a claim. Each study states what was actually done, in enough detail that another engineer could evaluate it.
The limits are stated
Where a result depends on conditions outside our control — testing environment, network, third-party services — the write-up says so rather than implying a guarantee.
Frequently Asked Questions
What is the difference between your case studies and your portfolio?
The portfolio shows finished websites — design, layout, and the visual result. The case studies document the engineering behind a project: the starting condition, the technical work performed, and what changed as a result. A site can appear in both.
Do you guarantee the same results on my project?
No. Performance results depend on the existing site, the platform, the hosting environment, third-party services, and testing conditions. The case studies describe what was measured on specific projects under specific conditions. What transfers between projects is the method, not the number.
Can I talk to the clients in these case studies?
Reference conversations can be arranged for serious projects, with the client's agreement. The technical case studies document our internal process and our own entity data rather than a specific client engagement.
Want This Documented for Your Business?
Every case study here started with an audit — a measurement of where things actually stood before any work began. We will run that first step for you at no cost: site speed, Core Web Vitals, SEO structure, and what answer engines can currently find about your business.
Call 407-720-8540 or get in touch. Future Site Designs has been building websites in Orlando and across Central Florida since 1998.
