Data. A Pages Router page receives props from getStaticProps or getServerSideProps. In app/, page.js is a Server Component by default and awaits its data itself (the data-functions question has the mapping).
Client JavaScript. The migration guide says it plainly: pages in pages/ are Client Components. Every module a page imports ships to the browser and runs again during hydration, even one that only formats markup. In app/, a Server Component's code stays on the server; the browser gets its rendered output in the RSC payload, and only 'use client' modules ship and hydrate. On Next.js 16.4.5 (Turbopack), the same product page, rendered with a 117 KB lookup table:
pages/: 8 scripts, 154,824 bytes gzipped, 41,136 of them the chunk holding the table.app/: 7 scripts, 138,639 bytes, no table.
Without that chunk the Pages version would have been smaller: the App Router runtime costs more than the Pages runtime, and the HTML grew from 718 to 1,970 bytes gzipped because it carries the RSC payload. The saving comes from what you keep on the server. next build on 16.4.5 printed no per-route size column, so measure the HTML's script tags.
Layouts. _app wraps every page and keeps its state across client navigations; a layout component rendered inside each page remounts. A nested layout.js stays mounted for every route under it. Measured: a counter at 2 stayed at 2 in app/a/layout.js, and dropped to 0 in a per-page layout.
Router and head. useRouter from next/router doesn't work in app/; next/navigation has useRouter, usePathname, useSearchParams and useParams. next/head is replaced by the Metadata API.