xsolla.com's homepage is 6.7 MB of HTML. 5.4 MB of it is one preloaded data block with all 859 content blocks of the 64 pages built in the same site builder, while the homepage displays 12; every audience page under /for/ repeats it at 6.5 to 6.8 MB. On a mobile lab test the homepage scores 31, with the main content appearing after 18 seconds; real Chrome users see interactions lag (INP 219 ms, "needs improvement"), and site-wide load time has grown 32% in six months. Xsolla is hiring a Senior Digital Experience Manager to keep publishing "fast and reliable" and the site "where developers, partners and customers first meet Xsolla", and the heaviest pages are exactly the new brand, movie and game audience pages that Ads & Rewards is about to send buyers to.
First action
Measure the preloaded data size on the homepage and three /for/ pages and agree a page budget.
How to measure it
Homepage INP and site-wide LCP (Chrome UX Report p75)
- Now
- –
- Target
- INP under 200 ms, LCP under 2.5 s
- By
- 90 days
Steps
Measure
Data block, HTML and transfer size for the top 20 pages.
Senior Digital Experience Manager 2 days
Scope the fix
Per-page preload and current-locale strings.
Site Builder product team 1 week
Build
Load other pages' blocks on navigation only.
Site Builder product team 2 weeks
Lazy-load
Below-the-fold modules and images.
Site Builder product team 1 week
Set a budget
HTML size and Core Web Vitals per template.
Senior Digital Experience Manager 2 days
Add a release check
PageSpeed in the publishing workflow.
DevOps 1 week
Re-measure
Lab and real-user data.
Senior Digital Experience Manager 4 weeks
Share with Site Builder customers
Release note on faster web shops.
Product Marketing 1 day
Why it works
Change the builder output so each page preloads only its own blocks (plus shared navigation) and fetches others when a visitor navigates; ship only the current locale's strings instead of 1.1 MB of all localization; lazy-load below-the-fold modules and images. Set a page budget (for example under 500 KB of HTML) and a Core Web Vitals check in the publishing workflow so new pages cannot regress. Measure before and after with PageSpeed and Chrome UX Report data.
Smaller pages render and respond faster, especially on the mid-range phones common in Xsolla's growth regions, which lifts engagement, meeting bookings and search visibility. Because the pages run on Xsolla's own Site Builder, the same fix speeds up every studio web shop built on it.
Ready to use
ChecklistPage weight budget
[ ] HTML under 500 KB per page [ ] Preload only this page's blocks and shared navigation [ ] Only the current locale's strings [ ] Below-the-fold modules lazy-loaded [ ] Images sized and lazy-loaded [ ] PageSpeed mobile check before publish [ ] Monthly Chrome UX Report review (LCP, INP, CLS)
Risks and how to handle them
Navigation between builder pages gets slower
Prefetch likely next pages on hover.
Search engines see less content
Keep each page's own content server-rendered.
Evidence
- Your websiteHomepage source (checked October 21, 2026): 6.7 MB of HTML (about 1 MB compressed). 5.4 MB of it is one preloaded data block holding 859 content blocks for all 64 pages built in the same site builder, while the homepage itself shows 12 of them; a further 1.1 MB is localization strings. The 46 audience and use-case pages under /for/ are each 6.5 to 6.8 MB; pages on the other templates (Xsolla Ads, Rewards, Events, Blog) are 260 to 460 KB. The builder pages load their modules from Xsolla's own Site Builder.Source
- PageSpeedGoogle PageSpeed, mobile lab test of the homepage: performance 31, Largest Contentful Paint 18.3 s, First Contentful Paint 11.7 s, Total Blocking Time 1,150 ms, 5,470 KiB transferred. Real Chrome users on the homepage: LCP 2.2 s (good) but Interaction to Next Paint 219 ms (needs improvement), rated "average"; across the whole site, p75 LCP is 2.9 s and 32% slower over six months.Source
- HiringSenior Digital Experience Manager (Remote USA, posted October 9, 2026): "xsolla.com and its subsites are where developers, partners and customers first meet Xsolla"; the role owns "keeping publishing fast and reliable", acts "as operational lead for the CMS and publishing systems behind xsolla.com", must "Keep templates, metadata, SEO implementation and UX standards consistent", and owns "meeting-booking experiences, lead capture and routing, and Pardot and Salesforce integrations (current tooling includes Chili Piper)". Success: "Website engagement and effectiveness improve over time."Source
- HiringDirector of Marketing, Xsolla Advertising & Rewards (Los Angeles, posted September 29, 2026): go-to-market across "Xsolla Ads, Rewards, Xsolla Choice, and Xsolla ID+ and Backpack"; "Build the new narrative, messaging, and marketing plan required to support Xsolla Ads' expansion into brand and agency sales"; make "Web3, on-chain attribution, and zero-party data, legible and compelling to non-technical buyers"; write "web and landing-page copy" and "demand stories for both gaming and non-gaming customer profiles". A Supply Account Manager for Ads & Rewards grows publisher integrations of the Offerwall.Source
- Your websiteTitles and descriptions: 24 of the 34 audience-by-goal pages under /for/ in the sitemap, including brands, consumer brands, movies, mobile and web3 games, carry the homepage title "Launch, monetize, and scale with Xsolla tools and services" and a generic description; one listed page (/for/classic-games/retention) returns 404. Xsolla Ads, Rewards and the Event Hub share the description "Launch, monetize, and scale with Xsolla tools and services | Xsolla", and the Xsolla Ads page has no H1 heading.Source