Manchester United Audit

Observed Behavior: When customizing a kit with player name and number in the megastore, the live preview pane renders correctly on Chrome and Firefox but displays a blank white rectangle on Safari (macOS and iOS) and all WebKit-based browsers.

Technical Root Cause: The preview component uses the CSS backdrop-filter property combined with mix-blend-mode: multiply to composite the name/number text onto the kit image. Safari’s rendering engine handles the mix-blend-mode calculation differently when applied inside a backdrop-filter context, resulting in a transparent composite.

Business Impact: iOS Safari represents approximately 35% of the megastore’s mobile traffic. Users on these devices cannot preview their customization before purchase, leading to either abandonment of the customization (reducing average order value by the £15-20 personalization premium) or incorrect orders that generate returns.

Remediation Path: Replace the CSS blend mode compositing with a <canvas> element that programmatically draws the name/number overlay onto the kit image. This provides consistent rendering across all browser engines and enables higher-fidelity previews (font kerning, arc text for name curvature).

Observed Behavior: MUTV video playback on cellular connections (throttled to 3G or slow 4G profiles) buffers indefinitely rather than downscaling to a lower quality tier. The player shows a perpetual loading spinner without offering a manual quality selector or error message.

Technical Root Cause: The HLS manifest serves only three quality tiers (1080p, 720p, 480p) with the lowest tier requiring 2.5 Mbps sustained throughput. On connections below this threshold, the ABR algorithm cycles between requesting 480p segments and stalling, never downscaling to a 240p or audio-only fallback.

Business Impact: A significant portion of MUTV’s international subscriber base accesses content from regions with variable mobile connectivity (Southeast Asia, Africa, parts of South America). Buffering failures on these connections drive cancellations and prevent trial-to-paid conversion.

Remediation Path: Add a 240p (800 Kbps) tier and an audio-only tier to the HLS manifest. Implement a fallback strategy where 3 consecutive buffer underruns trigger an automatic downscale. Expose a manual quality selector in the player UI.

Observed Behavior: When a season ticket holder attempts to transfer a matchday ticket to a friend who does not have a manutd.com account, the transfer form accepts the recipient’s email but the confirmation email is never delivered. The sender sees a “Transfer Complete” confirmation, but the recipient receives nothing.

Technical Root Cause: The ticket transfer API requires the recipient to have an existing account. When the recipient email is not found in the user database, the API returns a 200 status with a "pending_account_creation" flag in the response body. The frontend does not read this flag and displays the generic success state.

Business Impact: Failed ticket transfers for high-demand matches generate customer support contacts and last-minute gate complications. Season ticket holders who repeatedly experience failed transfers are less likely to renew, citing inability to share tickets with family and friends.

Remediation Path: Handle the pending_account_creation response state explicitly in the frontend. Display a message informing the sender that the recipient needs to create an account, and trigger an invitation email to the recipient with a deep link to register and claim their ticket.

Observed Behavior: The interactive Old Trafford seating chart renders as an inline SVG with approximately 75,000 DOM nodes (one per seat). Scrolling and zooming the chart on mobile devices drops the frame rate below 10fps, and pinch-to-zoom gestures lag by 300-500ms.

Technical Root Cause: Each seat is rendered as an individual <circle> SVG element with inline event handlers (onmouseover, onclick). The massive DOM node count causes the browser’s compositor to thrash during scroll and zoom operations.

Business Impact: Mobile users attempting to select seats experience a sluggish, unresponsive interface that feels broken. Combined with the overall mobile ticket purchase flow, this contributes to the 3.2x conversion rate gap between desktop and mobile ticket buyers.

Remediation Path: Replace the individual SVG elements with an HTML5 Canvas renderer that draws seats programmatically and uses hit-testing for interaction. Alternatively, implement a WebGL-based map renderer (e.g., Pixi.js) that handles 75K+ elements at 60fps. Use spatial indexing to only render visible seats during zoom operations.

Observed Behavior: The megastore kit personalization process requires navigating through 6 sequential screens: (1) select kit type, (2) select size, (3) choose player or custom, (4) enter custom name, (5) select badge/patches, (6) review. Tapping the browser’s back button exits the personalization flow entirely rather than returning to the previous step, losing all selections.

Technical Root Cause: The personalization flow uses client-side state that is not synchronized with the browser’s history API. Each “step” is a re-render of the same route rather than a distinct URL or history entry.

Business Impact: Users who make errors on step 4 or 5 must restart the entire personalization from scratch. The 6-step flow creates compound friction that is reflected in the 52% abandonment rate between “Start Personalization” and “Add to Cart.”

Remediation Path: Consolidate personalization into a single-page interface with an accordion or tabbed layout. Persist selections in URL query parameters or sessionStorage so browser back navigation and page refresh retain progress. Reduce the flow to 3 steps maximum: (1) Kit + Size, (2) Personalization, (3) Review.

Observed Behavior: The MUTV content library presents all videos (match highlights, full replays, behind-the-scenes, press conferences, academy content, legends content) in a single chronological feed. There are no genre filters, no series grouping, and no distinction between free and subscriber-only content until the user clicks play.

Technical Root Cause: The content management system tags videos with only two metadata fields: publish_date and content_type (free/premium). No taxonomy exists for competition, format (highlights vs full match), team (first team vs academy), or series.

Business Impact: MUTV subscribers who want to find specific content (e.g., all Champions League highlights, or the “Inside Old Trafford” behind-the-scenes series) must scroll through an undifferentiated feed. This directly reduces engagement time per session and increases churn among subscribers who feel the content library is thin — when in reality it is deep but poorly surfaced.

Remediation Path: Implement a content taxonomy with filters for: Competition (Premier League, Champions League, FA Cup, Friendlies), Format (Full Match, Highlights, Behind the Scenes, Press Conference), Team (First Team, Women’s, Academy, Legends). Add editorial “collections” or “shelves” similar to Netflix-style content rows on the MUTV homepage.

Observed Behavior: On mobile, the primary hamburger menu opens a full-screen overlay with 8 top-level categories. “Tickets & Hospitality” and “Store” — the two highest-commercial-intent destinations — are listed 5th and 6th, below “News,” “Matches,” “Players,” and “Videos.” Reaching the ticket purchase page requires: (1) tap hamburger, (2) tap “Tickets & Hospitality,” (3) tap “Buy Tickets.”

Technical Root Cause: The mobile menu mirrors the desktop navigation hierarchy verbatim, where “Tickets” and “Store” are prominent in a top-level horizontal nav bar. The translation to a vertical mobile menu buries commercial actions below editorial content.

Business Impact: Mobile users with high purchase intent (arriving from matchday emails, social media ticket announcements, or search) face unnecessary friction reaching the ticket and store pages, reducing mobile conversion rates relative to desktop.

Remediation Path: Add persistent bottom-bar quick-access icons for “Tickets” and “Store” on mobile, similar to the app navigation pattern. Alternatively, reorder the hamburger menu to lead with commercial actions, or add a promotional banner above the menu that deep-links to the current on-sale.

Observed Behavior: Users can filter the fixture list by competition (Premier League, Champions League, etc.) and home/away status. However, clicking into a specific match detail page and then pressing back resets all filters, returning the user to the unfiltered full fixture list.

Technical Root Cause: The filter state is stored in a React useState hook that resets when the component unmounts during route navigation. The filter values are not reflected in the URL query parameters.

Business Impact: Fans looking for specific fixtures (e.g., all remaining home Premier League matches for planning season ticket attendance) must repeatedly re-apply filters after viewing each match detail, creating repetitive friction that discourages engagement with the fixture calendar.

Remediation Path: Serialize filter state into URL query parameters (e.g., ?competition=premier-league&venue=home). Read filter state from the URL on mount to restore filters after back navigation. This also enables shareable filtered views via URL copying.

Observed Behavior: Funnel analytics show that 38% of users who reach the name/number entry step of kit customization abandon without completing. The step requires free-text input for custom names with a 12-character limit, but does not suggest popular player names or offer a “select from squad” shortcut.

Technical Root Cause: The name entry step is designed as a blank text input with character validation only. There is no typeahead, no popular suggestions, and no visual feedback showing how the name will appear on the kit until the next review step.

Business Impact: Users who want a player kit (the most common customization) must manually type the player name correctly — including accented characters for international players — rather than selecting from a list. This creates both decision friction (“How do I spell Højlund?”) and error anxiety (“What if it’s wrong?”).

Remediation Path: Replace the blank text input with a searchable player selector showing the current squad with shirt numbers. Retain the custom text option as a secondary tab for fans who want personal names. Show a real-time preview of the text rendering on the kit image as the user types.

Observed Behavior: The MUTV landing page leads with a 45-second auto-playing hero video that occupies 100vh. The subscription CTA (“Start Free Trial”) appears below the fold, requiring users to scroll past the full video before seeing any pricing information or trial offer.

Technical Root Cause: The landing page template prioritizes cinematic brand presentation over conversion. The hero section has no CTA overlay, and the video does not include a call-to-action end card.

Business Impact: Users arriving from paid acquisition campaigns (social ads, search ads) are ready to evaluate MUTV but are forced to wait through or scroll past brand content before reaching the conversion point. Landing page bounce rate is 58%, well above benchmark for streaming subscription pages.

Remediation Path: Overlay a persistent “Start Free Trial — 7 Days Free” CTA button on the hero video. Add a sticky bottom bar on mobile with the trial CTA that remains visible during scroll. Include pricing and trial terms above the fold alongside the hero content.

Observed Behavior: When an unauthenticated user adds items to their megastore cart and leaves the site, returning later shows an empty cart. Cart persistence and abandonment recovery emails are only available for logged-in users.

Technical Root Cause: The cart is stored server-side and keyed to the user’s authentication session. Guest carts are stored in a server-side session cookie that expires after 30 minutes. No client-side cart persistence exists.

Business Impact: Over 70% of megastore browsing sessions are unauthenticated. These users lose their cart contents after brief interruptions (e.g., checking a text message, switching apps on mobile), requiring them to re-find and re-add items. Cart abandonment recovery emails — one of the highest-ROI retention tools — cannot reach these users.

Remediation Path: Persist guest carts in localStorage with a 7-day expiry, syncing to the server-side cart upon authentication. Implement an email capture prompt (“Save your cart — enter your email”) during the add-to-cart flow for guest users, enabling abandonment recovery campaigns.

Observed Behavior: Fans purchasing individual match tickets at non-member prices see no prompt about the financial benefits of membership (ticket discounts, priority access, megastore discounts) during the checkout flow. The membership value proposition is only presented on the dedicated membership landing page.

Technical Root Cause: The ticket checkout and membership systems are operated by separate vendors. No API integration exists to calculate and display potential membership savings at the point of ticket purchase.

Business Impact: The ticket checkout represents the highest-intent moment for membership conversion — the fan is actively spending money with the club. Comparable football clubs that surface membership upsells during checkout report 5-8% conversion rates on the offer.

Remediation Path: Inject a contextual upsell module at the order review step showing: “Official Members save £8 on this ticket + get 10% off in the megastore. Join for £35/year — pays for itself in 5 matches.” Calculate actual savings based on the current ticket price.

Observed Behavior: Match reports prior to the 2022 site redesign are accessible only through an AJAX-powered archive search that requires JavaScript execution. Google has not indexed any match reports from before August 2022. Searching “Manchester United vs Liverpool 2019 result” returns Wikipedia and BBC Sport but not manutd.com.

Technical Root Cause: The legacy archive uses an infinite-scroll interface powered by client-side API calls. The server renders an empty container div; all content is injected via JavaScript after the initial page load. No server-rendered HTML exists for these pages.

Business Impact: Historical match reports represent a massive corpus of evergreen content that drives significant organic search volume. The club’s own authoritative match content for 10+ years of Premier League history is invisible to search engines, ceding this traffic entirely to third-party sports media.

Remediation Path: Generate static HTML pages for all legacy match reports using the existing API data. Implement pagination with <a> tag navigation (no infinite scroll) for the archive index. Submit the re-rendered archive to Google Search Console via sitemap for bulk re-crawling.

Observed Behavior: Individual player profile pages (e.g., /en/players-and-staff/detail/marcus-rashford) load a branded layout server-side but render all statistical data (appearances, goals, assists, season-by-season breakdown) via client-side JavaScript after page load.

Technical Root Cause: Player stats are fetched from an Opta API using a useEffect hook that executes only in the browser. The server-rendered HTML contains the player’s name and photo but no statistical content.

Business Impact: Player name + stats queries (e.g., “Rashford goals this season,” “Bruno Fernandes assists Premier League”) represent high-volume search terms. Google indexes these pages as containing only the player name and photo, ranking them below stats aggregators like Premier League’s own site, FBref, and WhoScored.

Remediation Path: Server-side render the initial stats payload by fetching Opta data at request time (with appropriate caching headers). Inject Person and Athlete schema markup with statistical properties. Implement ISR (Incremental Static Regeneration) to cache stats pages with a 1-hour revalidation window.

Observed Behavior: Megastore product pages (kits, training wear, accessories) do not include Product JSON-LD schema. Google Shopping results for “Manchester United home kit 2025/26” display competitor retailers (Adidas.com, JD Sports, Sports Direct) with rich product snippets while the official store’s listing appears as a plain blue link.

Technical Root Cause: The megastore platform does not inject structured data. The product detail page template includes basic WebPage schema but no commerce-specific markup.

Business Impact: Product schema enables rich results with price, availability, and review ratings in Google Search and Shopping. Without it, the official store competes at a visual disadvantage against third-party retailers selling the same products — often at lower margins for the club.

Remediation Path: Inject Product JSON-LD on all megastore product pages with name, description, image, sku, brand (Manchester United), offers (with price, priceCurrency, availability), and aggregate Review data where available.

Observed Behavior: The Old Trafford stadium tour page exists in English, Chinese, and Japanese editions, but the Chinese and Japanese pages contain identical English body copy with only the navigation and footer translated. Google Search Console flags these as duplicate content pages.

Technical Root Cause: The tour landing page content was created in English and published across all language editions without being sent through the translation workflow. The CMS allows publishing untranslated content blocks as a fallback behavior.

Business Impact: Google may demote or deindex the untranslated language editions, or worse, treat them as duplicate content that harms the canonical English page’s rankings. Chinese and Japanese fans encountering English-only content on a language-specific URL have a poor experience and reduced conversion likelihood.

Remediation Path: Prioritize full translation of the tour landing page into Chinese and Japanese — these are the club’s largest international stadium tour markets. Until translations are complete, implement hreflang tags that exclude the untranslated editions, and serve a 302 redirect from the untranslated URLs to the English canonical.