05
Challenge
Salon customers compare treatments, prices, practitioner information, availability and aftercare before booking. Important details are often spread across booking systems and social posts, while image-heavy pages can become slow and inaccessible.
06
Objectives
The concept is planned around the needs of new treatment customers, returning clients, gift purchasers.
- Organise treatments around customer needs
- Keep prices and duration maintainable
- Connect to the confirmed booking process
- Use genuine, permissioned imagery and reviews
07
Research
Discovery would review booking behaviour, common treatment questions, cancellation wording, patch-test or consultation requirements where applicable, update ownership and accessibility needs.
No commissioned interviews, analytics review or client discovery took place. A real project would validate these assumptions with the business, its customers, existing content and operational constraints.
08
Competitor analysis
The concept responds to common issues such as social-only service lists, outdated prices, unlabelled imagery, unclear practitioner responsibility and booking widgets that dominate the entire mobile experience.
This is a pattern review rather than a named competitor audit. No competitor performance, traffic or commercial result has been inferred.
09
Planning
Planning separates the information required before contact from details that can be collected later. The first release would prioritise the smallest useful journey and document ownership for content, enquiries and third-party services.
- Treatment catalogue
- Booking-provider handoff
- Price and duration management
- Team profiles
- Gift-card links
- Policy and preparation content
10
Information architecture
The proposed structure gives each major visitor task a stable, descriptive destination instead of hiding important details in one long page.
- Home
- Treatments by category
- Treatment detail
- Meet the verified team
- Book an appointment
- Policies and preparation
- Visit the salon
11
Wireframes
Wireframes would connect each treatment to price, duration, preparation, suitability wording and the correct booking action without making medical claims.
The page structure is content-ready; detailed wireframes would be produced and reviewed during a commissioned discovery and design phase.
12
Design approach
The concept uses an editorial, welcoming visual system with supplied salon and treatment photography rather than generated practitioner or client images.
The design direction would remain subordinate to readability, clear actions and verified trust information.
13
Development approach
A production build would use reusable page sections, structured content and progressive enhancement. The final platform would be selected only after reviewing editing needs, integrations, budget, hosting and ongoing support.
- Treatment catalogue
- Booking-provider handoff
- Price and duration management
- Team profiles
- Gift-card links
- Policy and preparation content
14
Security implementation
The concept identifies reasonable controls to review, not a promise that a future website would be completely secure.
- Avoid collecting unnecessary health details in marketing forms
- Review booking-provider privacy and access
- Protect staff accounts
- Keep marketing consent separate
15
SEO implementation
The proposed search foundations focus on useful, indexable information and accurate local or service context. Rankings and traffic cannot be guaranteed.
- Unique treatment explanations
- Accurate salon location and hours
- Natural links between treatments and preparation guidance
- Verified review content only
16
Accessibility
A commissioned build would target WCAG 2.2 AA good practice and include keyboard, screen-reader, contrast, zoom and form-error checks.
- Text alternatives for meaningful treatment imagery
- Readable price and duration information
- Clear booking focus states
- No information conveyed by pastel colour alone
17
Mobile optimisation
The mobile layout keeps treatment comparison and booking clear while preventing third-party widgets from obscuring content or controls.
18
Performance optimisation
Performance would be measured against the implemented website rather than estimated from the concept.
- Responsive salon photography
- Limited gallery payload
- Deferred booking scripts
- Optimised font and animation use
19
Technologies used
No production technology stack has been selected or implemented for this demonstration. The labels below describe possible delivery directions, not technologies already used for a client.
- Booking integration
- Treatment catalogue
- Content-managed website
20
Integrations
Any integration would require provider documentation, privacy review, failure handling and confirmation of ongoing charges before implementation.
- Salon booking provider — planned, not selected
- Gift-card provider where genuinely used
- Email signup with separate optional consent
21
Before and after
There is no genuine before-and-after comparison because this is not a redesign of a real client website. A future commissioned project could document the original experience with permission and compare only evidence that can be verified.
No before-and-after imagery or measurements are presented.
22
Outcomes
No commercial, ranking, conversion, accessibility or performance outcome is available. The outcome at this stage is a transparent, content-ready planning structure that can support a future brief.
Results are not yet available because the concept has not been commissioned or launched.
23
Lessons learned
A beauty website can feel distinctive without sacrificing price clarity, accessibility or honest treatment information. Booking convenience should not erase the underlying service content.
24
Next steps
If developed for a real organisation, the concept would begin with discovery and verification rather than moving directly into visual production.
- Confirm treatment catalogue and update owner
- Review booking-provider capabilities
- Collect genuine imagery and permissions
- Validate policy and preparation wording
26 · Call to action
Build around the real requirement
Share your users, content, integrations and constraints. AHANIX will review the project manually before recommending scope or making a quotation.