Impeccable vs Fudge for website design feedback
Use Fudge when you have a website and want to decide what to improve. Use Impeccable when you are working in the codebase and want an agent to design, edit, or
Should I use Impeccable or Fudge to improve my website?
Use Fudge when you have a website and want to decide what to improve. Use Impeccable when you are working in the codebase and want an agent to design, edit, or check the interface.
There is real overlap. Both can critique an interface, work with coding agents, and help establish a design direction. The useful distinction is where each one starts and what it gives you next.
| Fudge | Impeccable | |
|---|---|---|
| Starts with | A public URL, screenshot, or idea | A codebase or running development site |
| Main job | Reviews the website, compares it with relevant sites, and helps you decide what to change | Gives a coding agent design commands, source-editing workflows, and checks for common interface problems |
| Website references | Searches real websites and brings the selected examples into the conversation | Can inspect a page and use the project files and design documents already available to the agent |
| Result | A scored review, visual evidence, references, and an implementation prompt | Code changes, interface variants, and deterministic checks inside the development workflow |
| Design foundation | Helps you work out a direction from references, then can create a project design guide | Can create PRODUCT.md and DESIGN.md files for the project |
| After changes | Rechecks the live website and compares it with the earlier review | Runs its critique, audit, and detector checks against the changed interface |
| Price | Free review, then Pro at $29/month or Studio at $99/month | The core project is open source under Apache 2.0; its site also describes additional Pro material |
If the question is “What is wrong with this page, and what should it look like instead?”, start in Fudge. If the question is “Can my coding agent make this interface better?”, start in Impeccable. A practical workflow is to review the live site in Fudge, take the implementation prompt into Impeccable or another coding agent, then bring the updated URL back to Fudge for a recheck.
What that looks like in Fudge
Here is a review of mectrics.app, a landing page for a macOS menu-bar system monitor. The desktop capture shows the whole page. I also checked the live page at a 390-pixel mobile viewport before scoring the mobile experience.
Why the score is 8 out of 10
The page does the difficult work well. It has a clear product, a memorable visual character, real interface evidence, and a strong mobile opening. The remaining problems are specific enough to fix without redesigning the site.
The two accessibility problems are the most objective. The pink #f43b5d eyebrow on #ebe6df measures 3.00:1. The muted #706b66 body copy on the same background measures 4.25:1. Darkening those colors to roughly #c52245 and #6b6661 raises both above 4.5:1 while keeping the existing palette intact.
References for the changes
Foundation decision
Keep the current design system. The typography, warm neutral palette, product imagery, and mobile behavior already belong together. A new design guide would slow this work down. Make the five page changes first, then recheck the result.
First change
Fix the repeated low-contrast text styles. One color-token change improves every eyebrow and section paragraph before any layout work begins.
Implementation prompt
Impeccable’s design workflow can help a coding agent carry out and check those changes in the project. Fudge’s role is to establish the outside view: what the live page communicates, which changes matter, what comparable sites can teach you, and whether the result improved when it is published.
If this review covers your website and something is wrong, outdated, or should be removed, email [simdi@withfudge.com](mailto:simdi@withfudge.com).