HomeAds: real estate agency website

Overview

Industry: Proptech · hospitality

The scope: Redesign HomeAds’ navigation, filtering, and core interface; establish a new visual language across the product; and strengthen the experience to support user trust, engagement, and conversions.

Role: Product designer (end-to-end UX/UI, research, visual design)

Type: Client work · live

The context

HomeAds is a privately owned real estate agency website for finding properties to buy, rent, and sell, as well as accessing resources for buyers and sellers. An outdated interface and fragmented UX were holding the experience back.

The constraints

Property data comes directly from MLS®, making the product data-heavy and development-intensive. Given the client’s budget constraints, the scope was limited to improving the existing functionality rather than introducing new features.

The process

A four-phase process was used, adapted to the needs of the project:

  • Discovery: market, competitor, and user research
  • Definition: information architecture, functionality, and user flows
  • Prototyping: functional low-fidelity wireframes
  • Design: visual identity and high-fidelity wireframes

I. Discovery: audit and usability testing

I began by reviewing all assets my client had available, including the existing website and its analytics, to understand how the site was performing.

Based on my findings, I formulated testable hypotheses and challenged my client to navigate their own website through a think-aloud task.

The purpose was not to showcase the website’s shortcomings. Rather, it stemmed from my belief that visuals sometimes convey meaning more effectively than a purely verbal description.

Primary scenario: Send a viewing request for a 4-bedroom rental townhouse located anywhere in Barrie.

My client was unable to complete the scenario on their own website, validating the hypotheses. More importantly, this approach allowed my client to be part of the process and helped us identify the biggest problem and first priority: reworking the information architecture.

II. User interviews and information architecture

The preliminary audit and user testing gave me the shape of the problem, but not the texture of it. I interviewed four people who had recently bought a home or were looking to.

Hearing people describe their search, their best and worst experiences, where uncertainty sat, which digital tools they were already using, and how those tools let them down helped refine the pain points.

Information architecture came next. This was the part of the process where the amount of ambiguity carried into the design could be reduced. I mapped everything the site needed to support based on the audit, user testing, and research, and documented what each screen required, both in content and functionality. That inventory set the priorities: the top-level navigation, navigation dropdowns, filtering, and educational pages designed to build trust and provide reassurance throughout a high-stakes process.

Working in FigJam kept the client in the room throughout this process and surfaced questions that might otherwise have arrived much later.

The redesigned Innisfil Properties for Sale page on a desktop screen. Global navigation and a filter row sit above a split view: a scrolling grid of property cards on the left, each with a photo, price, street address, bed and bath counts and a wishlist heart, and a live map on the right showing clustered counts and individual prices for the same listings. Sitemap of the redesigned site. Eight global sections: Buy, Rent, Sell, Relocation Support, About, Wishlist, Get Alerts and Company. Buy and Rent each open onto four town listing pages and a Properties page with list and map views, filters and sorting, leading to a property page carrying about, details, wishlist and share actions; Buy adds the monthly payment calculator. Sell, Relocation Support and Get Alerts each lead to a request form and a request confirmation page. About holds About, Why Sell With Us and Buyer & Seller Guides. Wishlist opens as an overlay. Company holds Terms & Conditions and Cookie Policy. A legend distinguishes global pages, local pages, dropdown items and request confirmation pages.

Map of the towns the site covers.

Barrie Innisfil Essa Sutton Bradford East Gwillimbury New Tecumseth Newmarket Aurora

A site I’ve never heard of wants my name, email, and phone number before I’ve seen anything. I have to give up my information just to see all the photos. I don’t know who’s on the other end, whether they’re legitimate or whether they’ll just call me and push me towards a sale.

My partner and I are deciding together, so listings go back and forth constantly. Half of what I look at on my phone I lose track of by the time we sit down properly.

If a site is clumsy or the filters can’t narrow things down, I’m gone. How well it’s built says a lot about who’s behind it. I’m buying my first home, so I want to be able to rely on my agent.

I know the kind of place I want. What I don’t know is what I can actually afford, and I don’t want to work that out on three other websites while I’m trying to look at homes.

Navigation model and user pain points the structure was built around.

III. What changed, and why

Pain points surfaced during discovery are paired with their resolutions. The obvious improvements are assumed rather than called out. The focus here is on the decisions that went beyond the baseline features and directly addressed the uncovered problems.

Rent and Sale navigation

Rental properties were not directly accessible through the global navigation and could only be discovered by filtering properties for sale, making the rental discovery path unclear.

Resolved: Rent and Sale became distinct destinations in the global navigation, giving each market a direct entry point instead of requiring visitors to discover rentals through the Sale experience. For visitors already browsing, the property-type filter continues to provide a quick switch between markets, and its active state was clearly differentiated to preserve context.

The share feature

Choosing a property is a high-consideration decision that usually involves more than one person, but a listing could not be passed on to anyone from the site.

Resolved: An easy share option was introduced, allowing property listings to be shared by email or by copying the link to paste anywhere, making it easier to gather opinions and discuss potential homes.

Target size and component logic

Painfully small touch and click targets were one of the recurring issues identified across the interface. With 46% of traffic coming from smartphones, this was particularly concerning.

Resolved: Every interactive element was rebuilt to a 44px floor, including links and contextual menu items, not only buttons. Where controls were visually smaller, invisible hit areas extended the interactive target to 44px, allowing the same components to serve both touch and pointer interactions without maintaining separate desktop and mobile variants.

Filters

Redundant filters added clutter, while some categories lacked the options people actually needed. Unnecessary units and real-estate-specific terminology made the search harder to refine for anyone unfamiliar with the domain.

Resolved: Redundant filters were removed and surviving categories were renamed using buyer-facing language. High-use rental criteria, including parking and pet-friendly properties, were promoted to the main filter row rather than hidden in overflow. A distinct active state was also introduced so the current filter set can be understood at a glance.

The wishlist

The wishlist was not working on either mobile or desktop, making it difficult to keep track of liked listings and turning the process of remembering each property into a daunting task.

Resolved: The wishlist was restored across both platforms. Saved listings could be accessed immediately without sign-up, because asking a first-time visitor to register just to keep a shortlist creates friction, particularly on a site they do not yet trust. The wishlist was also extended to support a single viewing request for multiple saved listings.

Mortgage calculator

Property descriptions were too sparse to give prospective buyers enough information to evaluate a listing, while no tools were available to estimate what the property could cost them monthly.

Resolved: Comprehensive property descriptions and a mortgage calculator were introduced to help prospective buyers make more informed decisions, including estimating mortgage payments.

Surfacing New Listings sign-up

The “Subscribe to New Listings” CTA link was hidden among multiple dropdown menu items, drastically limiting its visibility.

Resolved: The subscription moved from a dropdown item to a fixed position in the top navigation. It is now in front of every visitor on every page, rather than only the ones who happened to open the right menu.

Bringing trust content into view

Important trust and educational content that introduced the business to prospective customers (About Us, buyer and seller guides, and more) was disconnected from the primary navigation. It was buried in the footer among a large number of secondary links.

Resolved: Material links were lifted into the top navigation. Breadcrumbs were introduced to maintain orientation.

The Innisfil Properties for Sale page on a laptop: navigation with Buy, Rent, Sell, Relocation Support, and About; a filter row with For Sale active; listing cards on the left and a map with prices and clusters on the right. Distinct paths for rent and sale. A clear path to both Rent and Sale markets runs through top navigation and filtering. Dedicated Rent and Sale navigation items provide direct entry points, while the active property-type filter is visually distinct to maintain context throughout the browsing experience.
A listing opened over the map view: the map with the property pinned, photo thumbnails, and the Request a Viewing form beside the agent’s contact details.
The listing page: a photo gallery, 2265 Arrington Way at $2,050,000, About the Property, and Property Details, beside the Request a Viewing form, with Share and View Map at the top.
The share menu: Email and Copy Link. Share control. A share control on the listing page offers two routes: send it by email, or copy the link and paste it wherever the conversation is already happening. The same menu after copying: Email and Link Copied! The confirmation after a viewing request: Your request has been received. We’ll be in touch soon to schedule the viewing.
Innisfil Properties For Sale on a phone in list view, with List, Map, and Sort & Filter at the top and listing cards each carrying a heart. Accessible click/ touch target sizes. Target sizes are designed around a 44px minimum. For example, a heart/ favourite button may have a 24×24px visible area while retaining a 44×44px hit area. The same interaction targets are used across desktop and mobile, avoiding unnecessary duplication of components in the design system. The same search in map view on a phone, with clusters and a price marker, and the selected listing’s card at the bottom. The listings page on a desktop with two listings saved, their hearts filled, and a Saved to Wishlist toast. The wishlist. The wishlist feature is fully functional across viewports. A bulk request-to-view action allows users to request viewings for multiple saved listings at once instead of submitting requests individually. The Saved Listings window open over the listings, noting that the list is kept on this device until the end of the session, with five saved homes. The listing page on a desktop: the photo gallery, the address and price, and the Request a Viewing form. Buyer decision tools. Property descriptions are expanded, and a mortgage calculator sits directly on the page. This allows the property itself and an estimated monthly payment to be considered together, without leaving the site.
The sort menu: Newest, Price Low to High, selected, and Price High to Low. The property type filter with House checked, and Condo, Bungalow, Semi-Detached, Townhouse, Duplex, Commercial, and Vacant Land / Lot unchecked. The price range filter: a slider, and minimum and maximum fields set to $250,000 and Unlimited. The bedrooms filter: Studio, 1, 2, 3, 4, and 5+, with 2 selected.
Innisfil Rentals on a desktop, with Parking and Pet-Friendly in the filter row beside the selected price and bedroom filters, rental cards on the left, and a map on the right. Streamlined filtering. Filtering is streamlined, with redundant options removed and categories clarified. For rentals, commonly used filters such as Pet-Friendly and Parking sit directly in the filter row, making key features immediately accessible. Selected and unselected filters are visually distinct, so the active set reads at a glance.
The Monthly Payment Calculator: property price, interest rate with 3-year and 5-year fixed presets, down payment with percentage presets, and amortization, giving a monthly payment of $7,461.
The map view on a phone, with the Saved to Wishlist toast over the selected listing. Saved Listings on a phone: four saved homes with filled hearts, and a Send a Request button at the bottom. The new listings alert form on a phone: Sign up for HomeAds new listings alerts to unlock the best of Simcoe County!, with first name, last name, email, and first choice area, and a Subscribe button. New listings subscription CTA. “Subscribe to New Listings” sits directly in the primary navigation as a prominent CTA, giving the subscription feature significantly greater visibility. The confirmation: Done! Thanks for signing up. You’ll be the first to know what’s new at HomeAds. The Why Choose HomeAds page: Guiding our clients through every step on their way to a new home, a video, and four reasons to choose HomeAds: guidance, excellent service, a local REALTOR®, and a personalized marketing plan. Informative/ educational pages. A clear path to educational and informational pages runs through the top navigation, with key links brought out of the footer. Breadcrumbs keep the route from the current page always visible. The Buyer & Seller Guides page: Get started. It’s easy., with the Buyer’s Handbook and the seller’s field guide, each with a download button.
The redesigned interface across desktop and mobile: search and listings, filtering, the wishlist, the mortgage calculator, new listing alerts, and buyer and seller guides.

IV. UI foundations

A set of foundations was defined to keep the experience consistent across screens, content, and interactions.

Grid. Four viewports carry the site. The largest has two variants: fixed for standard pages and fluid for screens that carry a map.

Typography. Urbanist was selected for its readability and scannability, with numerals that remain clear and visually balanced, which is particularly important for an experience centred around property prices, financial figures, and other numbers users need to scan quickly.

Component library. A design system was created, with components optimized for reuse across desktop and mobile to keep the component library lean. Most controls were built around the 44px minimum target that holds on desktop and mobile.

Type scale card, cropped by the panel edge. Headline Large is Urbanist Bold 30/32 at -0.6px on web and 22/28 at -0.4px on mobile; Headline Medium is Bold 20/28 and Headline Small Bold 17/26 on both; Label Large is Urbanist Semibold or Regular 17/24. Typography. Urbanist is used for how it holds up when scanned rather than read: open letterforms and numerals that stay even and legible at small sizes. This matters on a site where price, lot size, and monthly payment are among the most frequently read pieces of information.

lg-1128px-12 column-fixed

Twelve column fixed grid at the 1128px viewport. Layout breakpoints. HomeAds utilizes both fixed and fluid grids, allowing screen real estate to be maximized across complex desktop layouts, including those that involve maps.

md-600px-8 column-fixed and fluid

Eight column grid at the 600px viewport, fixed and fluid.

sm-360px-4 column-fluid

Four column fluid grid at the 360px viewport.

lg-1128px-12 column-fluid (screens with maps)

Twelve column fluid grid at the 1128px viewport, used on the screens that carry a map. Price range slider in two states: both handles at the ends, and the lower handle dragged inward. Design system. A design system establishes a consistent foundation across the product. Components are designed for reuse across desktop and mobile, reducing duplication and keeping the overall component set lean. Minimum price field in three states: empty at zero, focused while typing $9,000, and filled at $900,000,000. Listing card: photo with a wishlist heart, then $959,900, 2265 Arrington Way, Innisfil, Ontario, 1 bed and 1 bath. Compact listing card used in the wishlist, with a thumbnail, the same listing details and a close control. Segmented control with List selected and Map unselected. A single segmented control item, selected and unselected. Map zoom control in three states. Map pin parts: a label callout, a price chip reading $940,000, a cluster marker showing 10, and a single point marker. Menu row with a checkbox in four states: unchecked, unchecked on a hovered row, checked, and checked on a hovered row. Menu row with a radio button in four states: disabled, unselected on a hovered row, selected, and selected on a hovered row.
The foundations: the type scale, the four grids, and component samples.

V. Wireframes

Here are some UI enhancements that go beyond the case study shorthand and aren’t self-explanatory.

Headline hierarchy

Heading rank is built into the design system, not set page by page. Each page carries one <h1>, and every structural heading under it is an <h2>. Ranks are never skipped, so an <h1> never runs straight into an <h3>.

Input fields

Three recurring input field issues:

  • Required fields had no indicator, so the first signal that something was missing was an error message. Nielsen’s fifth heuristic argues that better design should prevent errors in the first place.
  • Placeholders were being used as labels and disappeared on focus, taking their instructions with them.
  • Placeholder text lacked sufficient contrast, making the guidance harder to read before it disappeared.

Required fields are now identified upfront, labels remain visible above fields, and placeholders are reserved for examples or additional guidance. The message field keeps a placeholder because it carries an example, and at 4.5:1 it clears contrast while still reading as quieter than the label.

Forms

All forms on the HomeAds website felt overwhelming and required users to provide a significant amount of personal information, making completion feel like a commitment. This could create uncertainty about what would happen to their data, including concerns about spam or receiving unwanted promotional emails. The form container itself was also too wide. Longer saccades and more frequent eye fixations make information harder to scan and process, particularly when a form contains a lot of fields.

The forms were simplified in collaboration with the client. Nonessential fields were removed, leaving only the information necessary to complete the task. The narrower container also reduced the visual distance between fields, making the form easier to scan and reducing the amount of information users had to process at once.

Telling BrandRed from StatusRed

Red serves two roles in the interface: it is the HomeAds brand colour and the semantic colour for errors. Because redefining established status-colour semantic meanings is never a good idea, the two reds needed to be visually distinct without changing what red communicates as a status.

BrandRed and StatusRed were therefore separated through lightness and saturation rather than hue: StatusRed is darker and less saturated, but stays within two degrees of BrandRed’s hue. Using the CIE76 algorithm, the two measure ΔE 32 apart. A difference of around 2 is already noticeable at a glance, so an error is never mistaken for branding, yet both still read as red.

Links and microcopy

Links without a default underline need a non-colour indicator on hover, so colour is not the only way to communicate an interaction. Link text was also rewritten to describe its destination rather than relying on generic labels such as “Read more” or “Download now.” More descriptive link text gives everyone clearer context about where a link leads.

Property details modal with heading ranks called out. The address is H1; Request a Viewing, About the Property, Property Details and Monthly Payment Calculator are each H2. Headline hierarchy. One h1 per page, h2 for everything structural beneath it, and no skipped ranks. In this example the street takes the H1 style and is the h1; the price takes label-large and is a paragraph. Both styles share the same values, so they look identical, but only one is a heading. A hand holding a phone showing the Innisfil properties list, with the list and map toggle, sort and filter, and two listing cards each carrying a wishlist heart. Target size and placement. The target is the whole property card, yet the heart holds its own 44px area, so saving a listing never opens it by mistake. Where space allows, controls sit on the right within easy thumb reach: the heart is at the lower right of the photo rather than the top left. New listings alert form with an eye-tracking path drawn over it, running label to label down two columns from First Name to the Subscribe button: 10 eye fixations, shorter saccades, 4 text input fields, and 6 drop boxes. Forms. The forms are simplified and nonessential fields removed. The form container itself is narrowed: the original form required 16 eye fixations and longer saccades, compared with 10 fixations and shorter saccades in the revised version. Request a Viewing form with three points called out: the note that an asterisk indicates a required field, the Name label and its asterisk, and the placeholder inside the message field. Input fields. Required fields are now identified upfront, labels remain visible above fields, and placeholders are reserved for examples or additional guidance. The message field keeps a placeholder because it carries an example, and at 4.5:1 it clears contrast while still reading as quieter than the label. Colour swatch: BrandRed, hex E72206. Telling BrandRed from StatusRed. Red is both the brand colour and the error colour. StatusRed is darker and less saturated than BrandRed but keeps the same hue, so both still read as red. CIE76 puts them ΔE 32 apart; a difference of around 2 is already visible at a glance. Colour swatch: StatusRed, hex 920000. Request a Viewing form in an error state. Under the empty Name field an inline message reads “Name is required” in StatusRed, beside an icon, while the Send a Request button stays BrandRed. Buyer and seller guides page. A side navigation lists sale and rental areas with the current link underlined, and the page offers the Buyer’s Handbook with a Download Buyer’s Guide button. Link microcopy. Links present a non-colour indicator (an underline) on mouse hover. Link microcopy is descriptive rather than generic, replacing labels such as “Read more” or “Download now” with text that identifies the destination.
Heading ranks on the property page, touch target size and placement on mobile, input field redesign and a shorter scan path in opt-in forms, and the perceived difference between system-defined red and Brand Red.

Impact

The redesign was followed by a period of significant growth for HomeAds. In the year following the launch, the business grew 60% year over year, marking a sharp change from the scale of the business before the redesign.

The new experience gave the business a clearer way to present its services and expertise as it grew. What began as an effort to resolve an outdated and fragmented user experience became part of a much larger shift.

The homepage on a desktop: Your REALTOR® in Beautiful Simcoe County, the agent card for Daria Morgendorffer, and a map of the Simcoe County towns. The property page in the map view: the listing pinned on the map, then $2,050,000, 2265 Arrington Way, About the Property, Property Details, Monthly Payment Calculator, and Request a Viewing. The property page on a phone: the photo gallery, the price and address, 7 bath and 4 bed, About the Property, and Request a Viewing. The property page on a tablet: the photo gallery with thumbnails beside the Request a Viewing form, above the address and price.
Search results on a desktop: Innisfil Properties for Sale, with filters, a grid of listing cards, and a map showing prices and clusters for the same listings. The homepage on a phone: the agent card for Daria Morgendorffer over a map with Barrie, East Gwillimbury, Alliston, and Newmarket.
The homepage on desktop; the property page on tablet, mobile, and in the map view; search results on desktop; the homepage on mobile.