The framework your website runs on. It builds every page in advance, before anyone asks for it — visitors don't wait while things get assembled in the background.
The visitor first sees a white screen, then your site piece by piece.
The page is there before their thumb leaves the screen.
- Every page has its own address
Folders in the project become addresses on the web. That's why Google finds each subpage separately.
- Pages are built in advance
Publishing produces finished HTML. The visitor doesn't wait for their device to assemble the page.
- Images are sized automatically
Each image is delivered at the size that device needs — a phone doesn't download the desktop version.
- Only the code that's needed
What doesn't appear on a page isn't loaded on that page.
- Visitor opens it
- Server builds the page
- Finished page
- Visible immediately
The decisive difference: the page is already finished when it reaches the visitor. It isn't assembled on their phone.
The framework around React. It builds every page at publish time instead of reassembling it on each request — what gets delivered is finished HTML. It also handles image sizes, addresses and keeping the two languages apart.
- Version
- 16
- Build
- ahead of time
- Images
- resized automatically
- Languages
- split by address
Building every page in advance so nothing loads late
Serving images automatically at the right size
Two languages without doing the work twice
For a single business-card page this is overkill. Plain HTML loads just as fast and needs less upkeep.
Google's PageSpeed measurement: 100 out of 100 for speed, 0.9 seconds until the largest content is visible. You can check it yourself — in the website check.