The Homepage Crush Method
The Homepage Crush Method is LandingCrush’s named process for SaaS homepage preference testing: submit a page, collect crush and pass swipes, read the crush rate, and keep the AI Panel separate.
The Homepage Crush Method is LandingCrush’s approach to SaaS homepage preference testing: submit a URL or screenshots, wait for moderation, let registered participants swipe crush (right) or pass (left) in a horizontal TV-frame view, read crush rate and comments, and keep the AI Panel in a separate column from community votes.
Where the Homepage Crush Method comes from
SaaS teams were polling friends or hiring designers without a preference read from people who swipe product pages for fun. LandingCrush adapted the CoverCrush-style vote to homepages. The Homepage Crush Method names that swipe → crush rate → decision loop for citation on landingcrush.com.
A poll among friends records whether people who already know the product feel comfortable with a screenshot. A designer is who you hire when the page needs hierarchy, type, and a layout engineering can build. Neither of those records a crush count and a pass count under one definition. The method is the named loop for that missing preference read. It is not a claim that a crush will raise trial starts. Your own website analytics remain the place to measure demo requests and revenue. The about page describes LandingCrush feedback as informational. It is not professional design, marketing, legal, or financial advice, and it does not guarantee a conversion outcome.
Steps in the Homepage Crush Method
Run the method in this order. Each step uses a tool already on LandingCrush. Skipping moderation, mixing the AI Panel into the crush rate, or calling a winner on a handful of votes breaks the loop the name refers to.
- Prepare the first screen on purpose — Hero, headline, or first viewport you actually want judged.
- Submit URL or screenshots — Creator submits; moderation must approve before the live feed.
- Collect swipe votes — Registered participants: right = crush, left = pass. Horizontal TV-frame view.
- Optional: Creator Duel — Head-to-head variants when comparing two submissions.
- Keep AI Panel separate — AI critique is not mixed into the crush rate.
- Decide with counts — The product accuracy process waits for 50 or more real community votes before treating a winner as readable. Write a short decision about the headline, hero, or call to action from the rate, the volume, the comments, and version history.
Prepare and submit the screen you want judged
Start with the first viewport. That is the hero, the headline, the call to action, and the mobile capture a voter sees before they scroll. Write down the one thing you want judged before you submit. “Does this headline say who the product is for?” is a question the swipe can inform. “Will this raise revenue?” is not. If two variants are the point, change one idea and keep the company, the offer, and the audience the same so a crush refers to that change.
Submission starts at /submit. Paste a URL so LandingCrush can capture desktop and mobile screenshots, or upload images when the alternative is not on a public URL yet. The form collects company name, industry, launch date, tech stack tags, and a short description. New submissions do not appear in the feed immediately. Status is pending until a moderator marks the page approved or rejected. The swipe feed is for approved homepages. One submission produces one crush rate. Putting two screenshots in a single description does not create a winner.
The free plan includes one active homepage submission. Creator Pro includes unlimited homepage submissions, which is how two variants can sit in the feed at the same time. Version history lets a later iteration point at an earlier submission with a parent id and a version number. Compare approved pages with approved pages. A pending upload has no feed result yet.
Collect crush and pass votes
After approval, registered participants vote at /swipe. The vote page shows one homepage at a time in a horizontal TV-frame view. Voters can drag with a finger or a mouse, or use the arrow keys. A swipe to the right is a crush. A swipe to the left is a pass. Each stored vote has a verdict of crush or pass, the voter’s evaluation style, and a flag for whether Blind Mode was on. Evaluation style is roast, rate, or both. Roast prompts ask for a specific critique. Rate is a more professional assessment. Both still end in the same binary verdict.
Blind Mode hides the company name during the swipe so the vote is about the page rather than a brand the voter already recognizes. That setting is useful when a known logo would otherwise carry a weak hero. Voters may also set a persona on their profile: a role such as founder, designer, marketer, developer, or investor, plus company size. Those fields are optional. When they are present, the creator dashboard can group voters by role and company size. LandingCrush does not describe that breakdown as a recruited sample of your customers.
Comments live on the public homepage detail page. A crush with no sentence is still a vote. A crush or a pass with a sentence about the headline is the part a team can edit. Look for repeated subjects: the headline, the screenshot, the button, or “I don’t know what this does.” Three comments with the same confusion are more actionable than a two-point gap in crush rate.
Read crush rate beside the count
Crush rate is the share of crush votes among all votes on that submission. Forty crushes and sixty passes produce a crush rate of 40 percent. The field is stored from 0 to 100. The creator dashboard at /dashboard shows the rate, total votes, weekly votes, and a velocity score. The product data model describes velocity as votes per hour over the last 48 hours. The public leaderboard ranks approved homepages and can be viewed as All-Time, This Week, Rising Stars, or filtered by industry.
The LandingCrush glossary describes a crush rate above 70 percent as strong. That is the product’s own label for a high preference share. It is not a claim that 70 percent will raise signups. A high crush rate means a larger share of the people who saw the page in the feed preferred it. It does not count clicks on your live button. Small samples swing. A handful of votes can print a dramatic percentage that fades after the next few dozen people. A perfect rate on three votes is not a decision. A mid-range rate on a large count is a preference share, and it is still not a conversion rate.
When you are comparing two submissions, line up vote count, crush rate, the one change you intended, and the comments about that change. If one variant has 12 votes and the other has 80, there is no winner yet. Weekly votes and velocity tell you whether one page was simply active in the last 48 hours. A strong rate that stopped accumulating is a stale snapshot. A page approved yesterday should not be declared the loser against a page that has been in the feed for a month, unless you limit the comparison to a shared window or run a duel.
Use a Creator Duel when you need one clock
A Creator Duel is optional. It is the timed comparison already in the product, for head-to-head variants when you are comparing two submissions. From /duel, challenge another homepage to a 48-hour vote. You need at least one approved homepage to start. The page returns a share link both sides can send. Voters arrive at that matchup instead of only browsing the general feed. The product describes a Battle Tested badge for the winner. The badge records the duel. It does not record your conversion rate.
Choose a duel when you want one clock and one link. Choose two independent submissions when you want each page to accumulate a crush rate in the ordinary feed, including weekly votes and velocity. If the second design exists only as an image, upload it as its own homepage once your plan allows another submission, wait for approval, then start the duel. Do not expect the live URL’s crush rate to score an image that was never submitted.
Keep the AI Panel in a separate column
The swipe is a human vote. The AI Panel Test is a separate purchase and a simulation. A single homepage variant is $29. A head-to-head of 2 to 4 variants is $49. The methodology page describes 50 fictional, niche-matched personas and three rounds of deliberation. Every report is labeled an AI Panel Preview. The personas are not real people. When community votes and a panel prediction disagree, LandingCrush treats the community result as the ground truth for that comparison.
On approval, an AI design critique is also queued. It scores hero clarity, call-to-action effectiveness, visual hierarchy, and mobile responsiveness from 0 to 10, and it returns notes plus improvement suggestions. Creator Pro is placed on the priority queue. The free plan includes the standard queue after approval. Leave those scores out of the crush-rate average. They are a different instrument. Averaging a 7.4 visual score with a 61 percent crush rate produces a number neither system defined. If the model says the button is weak and the comments never mention the button, do not rebuild the button only because the score moved.
Decide only when the counts are readable
The product accuracy process waits until a test has 50 or more real community votes, then publishes the comparison of an AI Panel prediction with the community outcome on /ai-accuracy. Use that published bar before treating a winner as readable. Below 50 votes, describe the result as directional. When both pages are past that mark, one crush rate is clearly higher, and comments point at the same change, you have a preference you can act on. If the rates are close, the test found no preference. Keep the version that is easier to maintain, or change a larger idea and submit again.
Write a short decision before you rewrite the live site. Name the headline, the hero, or the call to action you will ship. Cite the crush rate and the vote count for each version, plus the duel result if you ran one. Add the comment that showed up more than once. Set aside AI score gaps the comments did not support. Then name the live-site metric you will watch after launch. LandingCrush does not collect that metric for you. After you pick a presentation, change the live homepage and watch the conversion event in your own analytics. LandingCrush answered which submitted page these voters crushed. Your analytics answer what visitors on your domain did next.
Common questions
What is the Homepage Crush Method?
LandingCrush’s named swipe-vote process for SaaS homepages. You submit a URL or screenshots, registered participants swipe crush or pass after approval, and you read the crush rate and comments while keeping the AI Panel in a separate column.
What is crush rate?
Crush rate is the share of crush votes among all votes on that submission. Forty crushes and sixty passes is a crush rate of 40 percent. It is a preference share on LandingCrush, not a count of signups on your own website.
Who can vote?
Registered participants, after a moderator approves the submission. A page stays pending until it is approved or rejected, and the swipe feed shows approved homepages.
Pricing?
Voting and one active homepage are on the free plan at $0 per month. The pricing page says no credit card is required for that plan. Creator Pro is $19 per month, or $190 for the year charged as a single payment, which the pricing page says saves $38 compared with monthly billing. The AI Panel Test is billed separately at $29 for one variant or $49 for two to four variants. Team is a custom quote via hello@landingcrush.com.