The Results page shows if your test worked. For each variation (one version being tested: the control, or a challenger) you see how it did on your metrics. You also see how sure A vs B is, and if anything needs a look.
The Bayesian engine is A vs B's default. Instead of a p-value (the classic number for how likely a result is by chance), it gives a chance that your variation beats control. This section explains every number on the page, and how to use it well.
The Results page: every number here is explained somewhere in this section.
With A vs B's default engine, checking early (also called peeking) will not raise your false-positive rate the way old-style testing does. That said, checking too soon is still risky: a big result after a few hundred visitors is often just noise, not a real win.
A good rule of thumb: check in once or twice a week to make sure the test is healthy. Wait to decide until the test has run at least one full business cycle (usually one or two weeks) and gathered enough visitors.