Most small sites know where they lose people. Visitors leave the cart at shipping, the mobile menu frustrates them, an important page is hard to find. What is missing is a plan. UX Improvement Ideas turns the problems you have noticed into practical UX improvement ideas, ranked so you know what to fix first.
For each problem the tool gives the most likely causes, based on established usability principles, flags the ones that are only hypotheses and proposes two or three specific fixes. All fixes go into one table with what to change, why it should help, the effort and how to measure the result.
It never promises a conversion uplift or quotes statistics. The tool belongs to the Website copy family and pairs with the Website Design Brief when a fix turns into a redesign.
What you get
- A diagnosis of each problem, with causes marked as hypotheses when they need checking
- Two or three specific fixes per problem
- One priority table ranked by impact against effort, rated low, medium or high
- Three quick wins that can ship in a day
- A validation plan using analytics, session recordings or a test with five users
What you fill in
- Website or app, and what it does required
-
The name and the type of site or app. A shop, a booking app and a portfolio need very different fixes.
- Problems you have noticed required
-
Describe what users do or complain about, plus any data you have, such as bounce rate or drop-off points.
How to use it, step by step
-
Name the site and what it does
For example Verde Casa, online shop for eco cleaning products. The type of site changes the likely causes and fixes.
-
Describe what users do
List behaviors and complaints one per line, such as carts abandoned at shipping or a page few people find, with any numbers from analytics.
-
Choose the language and generate
The response comes in four sections, Diagnosis, Priority fixes, Quick wins and How to validate.
-
Work down the table
Ship the quick wins first, then the priority fixes, measuring each one as suggested before starting the next.
Example, input and output
Input
- website_name
- Verde Casa, online shop for eco cleaning products
- current_issues
- Many visitors abandon their cart when they see the shipping costs. The mobile menu is hard to use. Few people find the refills page.
Output
**Carts abandoned at shipping.** The cost first appears at checkout and feels like a surprise (hypothesis to verify).
**Mobile menu hard to use.** Small tap areas or too many first-level items (hypothesis to verify).
**Refills page rarely found.** It is missing from the main menu and product pages.
## Priority fixes
| Fix | Why | Effort | Measure |
|---|---|---|---|
| Show shipping cost on product and cart pages | Removes the surprise | Low | Cart-to-checkout rate |
| Add Refills to the main menu | Puts it on existing paths | Low | Refills page visits |
| Fewer mobile menu items, larger taps | Fewer missed taps | Medium | Session recordings |
## Quick wins
1. Shipping cost under Add to cart
2. Refills link in the footer
3. More spacing in the mobile menu
## How to validate
Find the abandonment step in analytics and ask five customers to find the refills page while you watch.
Illustrative example written by the editorial team.
Tips for better results
- Write one problem per line. Mixed problems get mixed fixes.
- Add numbers, even rough ones.
- Say who the users are. First-time mobile visitors and returning customers stumble on different things.
Who uses it, and for what
Small shop without a designer
Turn customer emails and analytics drop-offs into a short list of fixes your developer can estimate.
Agency preparing an audit
Use the priority table as the skeleton of a client report, then add your own screenshots and data.
Product manager
Paste issues from support tickets and get fixes already rated by effort for sprint planning.
Founder of a new app
Get hypotheses and a five-user test plan before paying for research.
Limits and good practice
- The tool cannot open your site or read your analytics. It works only from your description.
- Expected impact is a relative ranking, not a forecast. Accessibility needs a dedicated audit.
- Each diagnosis uses credits from your plan, so list every known problem in one run instead of one run per problem. See pricing or create an account.
Frequently asked questions
Can the tool look at my website?
No. It cannot visit pages or read analytics. It works only from the site description and the problems you write, so a precise description of what users actually do, with numbers where you have them, leads to a sharper diagnosis and more useful fixes.
How are the fixes prioritized?
All fixes go into one table ranked by expected impact against effort, rated low, medium or high. Each row says what to change, why it should help and how to measure the result, so you start with cheap changes that matter most.
Will it say how much conversion will improve?
No. The tool is told not to promise uplifts or cite statistics, because without your data any number would be invented. It tells you how to measure each fix instead, so the result comes from your own analytics after the change is live.
What is a test with five users?
A short session where five people try a task on your site while you watch, such as finding a page or completing checkout. The tool suggests it as an inexpensive way to confirm a cause before you invest in a fix.
Does it work for apps as well as websites?
Yes. Describe the app and what it does in the first field and the problems in the second. The same diagnosis, priority table, quick wins and validation plan apply to onboarding, navigation, search or checkout inside a mobile or web app.
Try it in your workspace
Start free, no credit card needed. When you need more, one suite grows with you, from Lite to Agency.
Sign in or create a free account, the tool opens in your workspace.