Pairing fonts without fetching them
Two typefaces work together when they agree on proportion and disagree on voice: similar x-height and width so the page feels coherent, different enough in structure that a heading is obviously a heading. Contrast that is too small reads as a mistake; contrast that is too large reads as two websites stitched together.
Each pairing here comes with the reason it works, not just the names. That reasoning is the part you can transfer to fonts that are not on this list.
The safest strategy
If you are unsure, take a serif and a sans from the same superfamily — DM Serif Display with DM Sans, IBM Plex Serif with IBM Plex Sans, Noto Serif with Noto Sans. They were drawn together, so their proportions already agree and the pairing cannot clash. Reach for a cross-family combination when you want a specific voice the superfamily does not have.
Previews use system fonts on purpose
This tool does not load anything from Google's font servers. Requesting a font file tells that server your IP address and which page you were on, which contradicts the point of a tool that promises nothing leaves your browser. The previews therefore use system fonts with comparable proportions to show the relationship between heading and body, and the copyable CSS gives you the real @import when you are ready to use it in your own project.
Loading them properly in production
An @import in CSS blocks rendering until the stylesheet resolves, which delays first paint. In production, self-host the two font files or use a preloaded <link>, request only the weights you actually use, and set font-display: swap so text is readable while the files arrive. Every additional weight is another request and another few tens of kilobytes.