Problems show up early
Setup issues are caught before any real content, design or visitors depend on them.
Before the real content goes up, a small test page proves the whole path works, from the code to the server to the visitor's screen. If you can read this, it was built on GitHub and is running on the studio's server.
A test page is small on purpose. When something goes wrong, there is only one thing to look at: the setup itself.
Setup issues are caught before any real content, design or visitors depend on them.
With a single page, any failure clearly points to the setup, not to the site's content.
The first publish is low risk, so every step can be checked calmly.
Once the test page works, every later change builds on something proven.
The test page travels the same road the real site will take later.
A small, plain page is added to the site's code.
The code is packaged automatically, the same way the real site will be.
The packaged site is started on the server that will host the real one.
If the page appears, every step in between has worked.
A setup test page takes very little effort and saves guesswork later. It is the quiet first step behind a reliable website.