FC Spartak

UX concept for the official website homepage: from a news showcase to a consistent fan journey.

UX audit Homepage Scenario-based structure Sports / Football
UX concept for the FC Spartak homepage
Role
UX/UI designer
Format
UX concept without access to internal analytics
Focus
Homepage, navigation, fan scenarios

About the project

The project is dedicated to a UX concept for the official FC Spartak homepage. I focused only on the homepage and rebuilt its structure around key user scenarios.

The goal was not a visual update for its own sake, but a change in the page logic: the main match, calendar, team form, news, stadium services, and entry points into the club ecosystem should work as a consistent fan journey.

Employer brief

The work was created in response to a specific employer request: I needed to show my vision for the FC Spartak homepage and propose a stronger composition from a UX/UI perspective.

The brief included mandatory elements that could not be removed: a four-block statistics section, match calendar, last 15 matches, Fan Zone, the official FC Spartak newsletter, and news.

So the task was not to invent the page from scratch, but to keep the required set of blocks and arrange them into a clearer user scenario.

Current page

The current homepage contains many useful sections: matches, calendar, news, video, shop, league table, and app. But they are perceived as a set of independent showcases.

The user gets a lot of content, but the navigation scenario through the page is not always clear: after the match promo, they quickly move into news, advertising banners, video, and shop, while fan service tasks and the club structure become less visible.

Current spartak.com homepage — part 1 Current spartak.com homepage — part 2 Current spartak.com homepage — part 3 Current spartak.com homepage — part 4 Current spartak.com homepage — part 5

Current spartak.com homepage

The current homepage contains a lot of content, but the blocks compete with each other and do not always form a single user scenario.

Current spartak.com homepage

What was important to improve

Scenario prioritization

The homepage should not start with a set of sections, but with the most important event for the fan — the upcoming match.

Connection between match and calendar

The next match should be connected to the schedule, match center, and ticket purchase, instead of existing as a separate promo banner.

Sports context

After the calendar, it is important for the user to quickly understand the team’s form: recent results, streak, goals, home and away matches.

Service tasks

Fans need quick access to tickets, stadium map, visit rules, directions, tours, and additional services.

User scenarios

A football club homepage should cover several different scenarios: learn about the next match, view the calendar, evaluate the team’s form, read news, prepare for a stadium visit, and navigate to other club teams.

That is why the new structure was built not as a content feed, but as a route from the main event to the user’s next actions.

Next match

When is the game? Against whom? Where? At what time? Can I buy a ticket?

Calendar

What matches are next? Which are home, which are away? Where can I open the match center?

Team form

How is the team playing now? How many wins, draws, and losses?

News

What happened at the club? What interviews, media, and official updates are available?

Stadium visit

How do I get there? Where is the entrance? Is Fan ID required? What are the visit rules?

Club teams

First team, women’s team, youth team, Spartak-2, academy.

New page logic

I rebuilt the homepage not as a news showcase, but as a fan journey: from the upcoming match and ticket purchase to the calendar, team form, news, stadium services, and club structure.

This order reduces cognitive load: the user moves through a meaningful sequence instead of jumping between unrelated promo blocks.

01Main match
02Calendar
03Team form
04News
05For fans
06Club teams

New homepage

In the new concept, the hero screen, calendar, statistics, news, and service sections work as one scenario. The page consistently answers the questions: what match is coming up, what is next, what form the team is in, what is happening at the club, and how to prepare for a stadium visit.

New UX concept for the FC Spartak homepage — top part New UX concept for the FC Spartak homepage — bottom part

Main match

The hero screen works as a promo for the upcoming match. The user immediately sees the teams, date, time, competition, stadium, and the main action — buying a ticket.

Instead of an abstract promo block, the hero screen solves a specific task: quickly answering “when is the next match and what can I do next?”.

Before current homepage
Before — hero screen
After new concept
After — hero screen

Calendar

The calendar continues the scenario after the main match. The highlighted next-match card connects the promo with the schedule, while the other cards provide a quick overview of upcoming games.

This way, the calendar does not compete with the hero screen, but helps the user understand what comes next.

Before calendar in the general feed
Before — calendar
After match → calendar connection
After — calendar

Team form

After the calendar, the user receives sports context: recent results, number of wins, draws and losses, goal difference, home and away matches.

The block is not framed as betting analytics and does not encourage risky actions. It is presented neutrally — as team form statistics and recent results.

Last 15 matches and team form block

The calendar answers “what comes next”, while the recent matches answer “what form the team is bringing into these games”.

News

News remains an important part of the homepage, but in the new structure it comes after the match, calendar, and team form.

This lets the user first resolve the basic sports questions, and only then move on to content: news, interviews, media, and club materials.

Before news appears too early
Before — news
After after the sports context
After — news

For fans

A separate block brings together practical scenarios that are often hidden in the menu or footer: tickets, route, stadium map, visit rules, tours, and VIP services.

This makes the homepage not only informational, but also service-oriented: if the user is going to a match, they do not need to search for basic information deep inside the site.

Service block for fans

Club teams

The homepage adds a clear entry point into different parts of the club: first team, women’s team, youth team, Spartak-2, and academy.

This helps present the club more broadly and gives users quick access to the team they need without searching through the menu.

Club teams block

Navigation

The menu was rebuilt according to section priority. The most frequent and commercially important scenarios — tickets, season tickets, matches, shop, and team — were moved into the top navigation.

This reduces dependence on the footer and helps users find key sections faster. Navigation should reflect real user scenarios rather than the organization’s internal structure.

Before / after

BeforeAfter
The homepage is perceived as a long content showcase.The homepage is structured as a consistent fan journey.
Many news items, videos, banners, and promo blocks compete for attention.First the match, calendar, and sports context; then news and services.
Service scenarios are less visible and spread across the menu or footer.A separate “For fans” block with quick entry points has been added.
Club teams do not have a strong visual entry point from the homepage.A “Club teams” block has been added: first team, women’s team, youth team, Spartak-2, and academy.
The menu is less clear in terms of user priorities.Navigation has been rebuilt around key user scenarios.

Why the new structure is stronger

1. Answers the main question faster

The user immediately sees the upcoming match, date, time, opponent, and ticket purchase button.

2. Continues the sports scenario

After the promo, the user sees the calendar and team form, not scattered promo blocks.

3. Reduces cognitive load

Blocks are arranged in a meaningful sequence: from match to context, then to news and services.

4. Makes services more accessible

Tickets, route, visit rules, and stadium map become visible on the homepage.

5. Expands the image of the club

A separate teams block presents Spartak as a club system: first team, women’s team, youth team, reserve team, and academy.

Limitations

The project was created as a UX concept without access to the club’s internal analytics. The conclusions are based on heuristic evaluation, scenario analysis, and comparison of the current homepage structure with the new concept.

To validate the hypotheses, web analytics data would be required: CTR on ticket purchase, match center transitions, calendar clicks, page scroll depth, and use of service sections.

Metrics for testing hypotheses

Tickets

CTR on the “Buy ticket” button and transitions from the hero and calendar.

Match center

Transitions to the match center from upcoming-game cards.

Calendar

Clicks on match cards and transitions to the full calendar.

For fans

Use of the “How to get there”, “Stadium map”, and “Visit rules” sections.

Teams

Transitions to the women’s team, youth team, Spartak-2, and academy.

Depth

Scroll to lower blocks, page depth, and page engagement.

Result

In the new concept, the homepage stops being just a showcase of news and promo materials. It becomes a consistent fan route: from the upcoming match and ticket purchase to the calendar, team form, news, stadium services, and club structure.

This approach makes the homepage clearer, more scenario-driven, and more useful for different types of users: fans, viewers, stadium visitors, subscribers, and those interested in the entire club system.

Made on
Tilda