The two are different kinds of thing. WordPress is a content management system: PHP and a database, an editor in the browser, themes for the look and a large catalogue of plugins for features. Next.js is a React framework: a developer writes the pages in code, and content comes from files in the repository or from a headless CMS connected to it.
That difference decides who can change what. On WordPress an editor can add a page, change a menu or install a form plugin without a developer, which is its main strength. On Next.js the editor changes content in whatever CMS the site is given, and anything about layout or features is a code change. That suits a team with a developer, and frustrates one without.
The second difference is upkeep. A WordPress site runs on a server that executes PHP on request, and its core, theme and plugins all need updating; each plugin is code from a different author with access to the whole site. A Next.js marketing site is often built ahead of time into static pages, so there is less running on the server to patch, but its dependencies still need updating and someone has to know how.
Speed is possible on both and guaranteed on neither. A light WordPress theme with caching can be fast; a Next.js site loaded with scripts can be slow. What Next.js gives is control: every script on the page is one somebody chose to add. We measure the result, not the framework.