Comparison Website UX Redesign: CDNfinder Case Study
The problem: CDNfinder listed 35 CDN providers on one crowded page, the purchase form was long, the page loaded slowly, and almost nobody clicked the provider cards below the first screen.
The fix: Analytics and session recordings before any layout, then a homepage that works like a tool (filters first, short cards, vector graphics) and a separate quote page for the providers whose prices cannot be public.
In short: A comparison website UX redesign starts with data, not layout. Our audit found a page that took more than 12 seconds to load and heatmaps showing that nobody scrolled to the provider cards, and the client sent a new offer on the day the contract closed.
- Client
- Bart Pluskota
- Site
- cdnfinder.com
- Dates
- Mar 14 to May 9, 2018
- Budget
- Premium and beyond
- Spent
- $11,900
- Client rating
- ★★★★★ 5.0: “You Get much more than what you pay for!”

This is a comparison website UX redesign case study from March to May 2018. We worked for Bart Pluskota, who ran CDNfinder at Zerouno, on the visual design, the illustrations and the landing pages of a platform where companies discover, compare and buy CDN services. Bart’s own developers built it, and we coached them on the design files.
Comparison Website Audit First: A Slow Page, a Long Form and Two Missing Tools
Our first message was a list of questions, not a mockup. Does the purchase page really need that many form fields? Why does the page download so slowly? We also said the page was too crowded for the 8 to 15 seconds a casual visitor gives it. Bart’s answer on the form was practical: the fields were compulsory because the purchase flow ran on WHMCS, and customizing it would cost them the system’s updates.
He wanted more purchases of CDN plans, more requests for CDN assessments, and information that was easier to read. The contract allowed up to 10 hours a week. Our first estimate was 20 hours or more, about $2,000 at today’s $100 an hour, and a few months before A/B tests would say anything, longer with little traffic. With small traffic we suggested bold tests: three buttons for two weeks, one button for the next two.
Before drawing anything we asked for two tools, Hotjar and Google Analytics access. Our reason, in the chat: “those are my eyes, without them we have just ideas, not data”.
Comparison Website Heatmap Findings: Nobody Scrolled to the Provider Cards
Within hours the data was uncomfortable. Direct traffic was poor quality. Organic visitors bounced, and so did returning visitors, which pointed at the page and its message and not at the traffic source. After only 39 recorded events (a small sample, and we said so) the heatmap already showed that nobody clicked the cards below the first screen. A week later the pattern held: nearly all interactions happened in the first screen, a few at the footer, and almost nobody touched Compare.
