From News to Navigation: A UX Review of the qs88 User Journey Around Fulham's Stadium Plans
You click a headline about Fulham's stadium redevelopment, expecting a quick update. Instead, you land on a homepage that buries the article under pop-ups, vague menus, and unclear next steps. The information you wanted is there—somewhere—but the path to it feels like a detour. This friction is exactly where most platforms lose users. The following review walks through the complete user journey on qs88 using the Fulham announcement as a case study, examining what works, what disrupts, and whether the experience justifies the time you invest.
Five Findings from the UX Audit
- Entry point clarity is inconsistent. A direct link to the Fulham article sometimes lands on a category page rather than the story itself, adding an extra click.
- Registration is optional for reading but enforced for key actions. You can browse news without an account, but features like commenting, saving articles, or receiving alerts require sign-up—creating a split experience.
- Mobile responsiveness handles the Fulham article well, but menu collapse and font sizing on smaller screens still feel slightly cramped for heavy text sections.
- Support access is two clicks away, yet it does not appear in the main navigation; users must scroll to the footer or use a help widget that loads separately.
- Content discoverability after the article relies on a generic "related posts" block that does not reference Fulham or stadium topics, reducing re-engagement.
Detailed User Journey Analysis
Access: Arriving with a Specific Intent
A user searching for "Fulham stadium redevelopment plans" may arrive via search engine or a direct link from a sports news aggregator
🔗 Xem thêm:
hướng dẫn sử dụng QS88