Why does Notion lag when I write a long chapter?

Why a long page drags

Notion builds a page out of blocks, and every paragraph is one. A six-thousand-word chapter is a few hundred of them, and Notion tracks each one separately. Add an inline database of characters, a couple of embeds, and synced blocks from a notes page, and writers report the cursor trailing behind their typing toward the bottom of the page.

What helps in Notion

1. Break the chapter into subpages. Add an empty subpage for a scene, select the scene's blocks, open the block menu (the ⋮⋮ handle), and choose Move to to send them into it. Scenes make natural pieces. The same menu's Turn into can also make a single block into a page.
2. Take databases off the writing page. Keep the character or timeline database on its own page and link to it. A writing page with only prose on it is the lightest page Notion has.
3. Swap heavy embeds for links. A video, a map, or a board embedded mid-chapter loads every time the page does.
4. Compare the app and the browser. If one lags and the other does not, stay with the quick one. In a browser, try a private window to rule out grammar and writing extensions.

Splitting has the usual price. The chapter no longer reads straight through on one page, and a word count now means adding up subpages.

In Tabularia

A chapter here is a level of the manuscript rather than a page of blocks, and the canvas lays out only what you can see, so the layout work does not grow with the chapter. Tabularia's layout benchmark shows how it holds as length grows. Each chapter and scene carries its own word count in the Outline, and reference material goes in Sheets beside the page instead of in it.

To move, choose Export from the page's ••• menu in Notion and pick Markdown & CSV with subpages included. Unzip the download, open Import folder as new manuscript, and pick the unzipped folder. The page hierarchy becomes chapters and scenes, and pictures are placed where the text referred to them. Read the imported Outline against Notion before you stop using the original.

Where Tabularia does not follow Notion: it is a manuscript, not a workspace. There are no database views or wiki pages, and no live co-editing. Sheets hold reference records about the story's people and places, and they are not a database you can query.