    Learning & community 

Launch day fills the classroom. Keep the lights on.

Logged-in studentsVideo lessonsLaunch spikes

Jump to the prompt The Membership & LMS playbook

The speed brief

Who arrives

A student who paid, mid-lesson, expecting it to work

What they want

The lesson, the progress bar, the next module

How long you get

None. They already bought — now it just has to be good.

5–15ms cached what xSpeed serves instead of PHP

The story

When Elena opens enrolment twice a year, two things spike at once: the public sales page (thousands of visitors from her launch emails) and the student area (every new student logging in to start lesson one the same evening).

They are opposite problems. The sales page is identical for everyone — pure caching. The lesson pages are personal — progress bars, completions, access checks — and can’t be page-cached at all. Her old setup treated both the same way and failed at both.

Split correctly — sales pages prewarmed static, student area on Redis with REST caching — both spikes now land softly. Launch day is loud in Slack and quiet in the error logs.

When speed decides the outcome

Three beats. Everything xSpeed Cache does on this page is aimed at the gap between the second and the third.

The launch

Everyone enrols in the same 48 hours, and the server finds out live.

The lesson

Logged-in pages skip most caches, so students get the slow version.

The refund

A course that feels broken gets refunded, however good the content is.

What a site like this actually needs

Not a redesign — three properties the site has to have before anything else matters.

A sales page that absorbs the launch list

Thousands of identical page views in an hour: prewarmed static HTML.

Fast lessons for logged-in students

Progress and access checks served from memory, not the database.

Video without the drag

Lesson embeds load on demand, not all at once.

The xSpeed features doing the work

Each one is a real setting with a real guide — nothing here is a marketing abstraction.

Page cache + prewarming

Sales and curriculum pages stay permanently warm for launch traffic.

Read the guide

Redis object cache

Access checks and progress queries served from memory for every logged-in student.

Read the guide

REST API cache

The LMS plugin’s own data traffic stops hammering the database.

Read the guide

The exact prompt

Connect your site via xSpeed MCP or xSpeed Hub, then paste this into Claude or ChatGPT. It is written for this business, not a generic template.

COPY & PASTE

My course launch opens Tuesday. Using xSpeed, prewarm the sales and curriculum pages, exclude everything behind login from the page cache, connect Redis for the student area, enable REST API caching, and set heartbeat control so idle dashboards don’t drain the server. Show me queries-per-page for a lesson page before and after.

What happens: The launch list hits static pages; the new students hit a memory-backed classroom. Both feel instant.

Questions from Online course creators

Because page caching only covers logged-out pages. Students need the object cache: with Redis or Memcached, the repeated access and progress queries that make lessons slow come from memory instead — typically cutting database work per page by an order of magnitude.

No. Personalised pages are excluded from the page cache by login cookie; the object cache stores query results, never rendered personal pages. Each student’s view is always their own.

Keep reading

The full playbook

xSpeed for Membership & LMS

Object caching for the logged-in side, full-page speed for the public side, and precise rules for the line between them.

Next in Learning & community →

Communities & forums

A busy community is the goal — and the load.

Nonprofits & churches Schools & universities Recruitment & staffing Job boards & directories

Fast, for Online course creators.

Install xSpeed Cache free, connect your AI, and paste the prompt above.

Try xSpeed Cache ⚡ View pricing