The Problem
The core issue wasn’t the amount of media — it was how the system was built.
Specific problems:
- No control over frontend bloat
- Inefficient asset loading
- Weak internal linking and content structure
- No clear system for organizing projects, designs, and documentation
Incremental fixes wouldn’t be enough. The foundation itself needed to change.
Constraints
- Preserve a large volume of existing media
- Dramatically improve performance without reducing visual quality
- Support complex internal linking between projects, systems, and designs
- Enable gated content for visitors downloading system-specific documentation
- Be maintainable long-term without performance degradation
Our Approach
We recommended a full rebuild, prioritizing performance, structure, and long-term control.
Key decisions included:
- Rebuilding the site from scratch using Oxygen Builder for a lightweight, controlled frontend
- Designing a clean post architecture to logically connect designs, systems, and content
- Implementing strong internal linking to improve navigation and discoverability
- Treating performance as a first-class requirement, not an afterthought
What We Delivered
- A complete rebuild on a lightweight frontend architecture
- Structured post types and taxonomies to connect related designs and systems
- Gated content flows to capture visitor information for documentation downloads
- Advanced media handling using Amazon S3 and CloudFront
- Fine-grained performance optimization across assets, caching, and delivery
- All media volume was retained — without compromising speed.
Outcome
The rebuilt system delivered a measurable turnaround:
- Average page load times reduced from ~10 seconds to under 1 second
- Seamless browsing experience despite heavy media usage
- Clear, structured internal navigation across projects and content
- A stable, maintainable platform aligned with the brand’s quality
- The website became an asset again — not a liability.
The Situation
Kaprel reached out after their previous development team abandoned the project mid-way.
The existing website was technically unstable and difficult to use.
Key issues included:
- Extremely slow page loads, often 15–20 seconds per page
- Poor user experience due to inconsistent structure and interactions
- Heavy media usage without performance controls
- Bloated build with little architectural clarity
- The site failed to represent the quality of Kaprel’s work and was actively hurting engagement.
Why This Worked
- Willingness to rebuild instead of patching a broken foundation
- Control over frontend bloat and asset delivery
- Treating content architecture and performance as system-level concerns
- Senior ownership from audit through execution
Engagement Model
Rescue & Rebuild
Focus
Performance Engineering, UX, Infrastructure
Client
Kaprel Partitions (UAE)
Facing a Similar Situation?
If you’re dealing with an unstable or underperforming build, a technical review can help clarify whether it’s salvageable — or needs a clean restart.
No obligation. We’ll identify risks and priorities — even if we don’t work together.