A page can begin with a readable document and working links. Scripts can then add search, filtering, saved preferences, or other conveniences. This gives the experience a useful foundation when an enhancement is unavailable.

The important work is choosing which actions belong in that foundation. Reading a public article rarely needs a complicated startup sequence. A specialized editor may have different requirements and should explain them clearly.

Try the page under an ordinary limitation, such as a blocked script or a slow resource. Check whether the reader can still understand the content and reach the next page. A thoughtful baseline makes the richer version easier to depend on.

Imagine a practical setting.

Imagine an article whose title, paragraphs, and links are already present before interactive controls begin working. The first version still supports a complete read.

Before the next experiment.

The first useful part of a page deserves attention. A visitor should be able to understand its purpose while the rest of the experience becomes ready.
A few starting points
  1. Name the page’s essential task.
  2. Keep its basic navigation usable.
  3. Test an unavailable enhancement.

Follow a related question

Match appearance with behavior.

Consistency where it helps learning

Name the question the prototype should answer.

A prototype for the uncertain part

Keep learning

Related background to continue exploring this subject.

MDN: learn web development MDN: how the web works
Explore a possibility