Shdane Group
A logistics site, redesigned, rebranded, and made fully accessible
A North Carolina warehousing and logistics site, taken from a plain white design to an industrial redesign, a rebrand, a hosting move, and full prerendering, reaching 100 for mobile accessibility and SEO.


Before · July 2026, before the redesign (commit d1567c0) · After · Live site, September 2026


| Metric | Before | After |
|---|---|---|
| Mobile accessibility | 94 | 100 |
| Mobile SEO | 92 | 100 |
| Mobile performance | 96 | 97 |
| Pages in sitemap | 4 | 10 |
| Pages served | Rendered per request | Prerendered |
Shdane Group is our own platform: a North Carolina warehousing, distribution, and fulfillment business. We show it here as in-house work, not as a client result.
Starting point
In mid-July 2026 the site had a plain white design: light grey backgrounds, dark slate buttons, and the original red emblem logo, with nothing that said “warehouse” at a glance. Under the surface every page was rendered on each request with caching turned off, so the page description reached browsers late, inside the page body instead of the head. Lighthouse flagged low-contrast small text and headings that skipped levels. The sitemap listed four pages.
What we changed
Between July and September 2026 we:
- redesigned every page in an industrial style: navy and orange, thick borders, sharp corners, and a self-hosted Space Grotesk display font;
- added five service landing pages (warehousing, distribution, order fulfillment, inventory management, and confidential logistics), each with a quote call to action;
- replaced the logo with a new warehouse mark and wordmark, and updated the favicon to match;
- prerendered every page so it can be cached at the edge, and made the request proxy stateless;
- moved hosting from Vercel to Netlify;
- rewrote the contact form to be much lighter, moved its mail to Refresh, and added Cloudflare Turnstile against spam;
- published a
security.txtfile and a vulnerability disclosure policy; - raised the contrast of small labels and fixed the heading order on every page.
Outcome
- Lighthouse (mobile): accessibility 94 → 100, SEO 92 → 100, best practices 100 after. Performance held steady (96 → 97) while the redesign added a display font and heavier visuals.
- Search surface: the sitemap grew from 4 pages to 10, including the five new service pages and the security policy page.
- Delivery: every page except one text endpoint is now prerendered and cacheable, instead of being generated on each request.
How we measured
Both versions were built from the repository and served locally with next start on the same
machine, with no production credentials. Each server sat behind the same small local proxy that
marks requests as HTTPS, so the older version’s HTTP-to-HTTPS redirect did not block the pages or
robots.txt. Lighthouse scores are the median of three mobile runs of Lighthouse 12.6.1 for each
version, on 27 September 2026. The “before” is commit d1567c0 (17 July 2026), the last commit
before the redesign; the “after” is the current main branch (8e29d1b). Page counts come from
each build’s sitemap.xml. We leave out the “before” best-practices score because its only
failures came from hosting-specific analytics scripts that cannot load outside the original host.