How to Use Linked Views to Reduce Page Load in Notion

Large Notion pages with many databases, inline tables, and embedded blocks can take several seconds to load. This slowdown happens because Notion must render every database property, filter, and view on the page before the content becomes interactive. Linked views solve this problem by letting you display only a filtered subset of a master database instead of loading the full database on every page. This article explains how to create linked views, where to place them to minimize render overhead, and what to avoid so your workspace stays fast.

What a Linked View Does and Why It Reduces Page Load

A linked view is a block that displays a database (or a specific view of that database) on a different page. The data stays in the original database. The linked view only shows what you configure — a filtered set of rows and a limited set of columns. Because Notion does not load the entire database into the page, the page render is faster.

When you insert a full database block (not a linked view), Notion loads all rows, all properties, and all view configurations. If that database has hundreds of rows and dozens of columns, the page load time increases linearly with the data size. A linked view, by contrast, loads only the rows that match the filter you set. The master database remains untouched, but the page itself contains a lightweight reference.

This technique is especially useful on dashboards, team home pages, and project trackers where you need to show a team member only their own tasks or a specific project phase. You can have multiple linked views on the same page, each pointing to the same master database, with different filters and sort orders. The page load time stays low because each view shows a small slice of the total data.

Steps to Insert and Configure a Linked View

1. Open the target page
   Navigate to the Notion page where you want the linked view to appear. This can be any page in your workspace.
2. Type the forward slash command
   Press the slash key on your keyboard to open the block menu. Type “linked” and select Linked view of database from the list.
3. Select the master database
   A dialog appears showing all databases in your workspace. Click the database that contains the full dataset you want to reference. The linked view block appears on the page.
4. Choose the initial view type
   By default, Notion shows the first view of the master database. You can change it by clicking the view name in the linked view toolbar and selecting another view type (Table, Board, Gallery, List, Calendar, Timeline).
5. Add a filter to limit rows
   Click the Filter button in the linked view toolbar. Add one or more filter conditions. For example, set “Assignee” equals “Your Name” to show only your tasks. Each filter condition removes rows from the rendered output, reducing page load.
6. Hide unnecessary properties
   Click the Properties button in the toolbar. Uncheck any property that the reader does not need to see. Fewer visible columns mean a smaller DOM and faster scrolling.
7. Set the sort order
   Click the Sort button and add a sort rule. This does not affect load time, but it helps users find information faster, reducing the time they spend on the page.
8. Adjust the linked view layout
   You can resize the linked view block by dragging its left edge. A narrower block reduces the area Notion must paint, which helps on pages with multiple linked views.

If Notion Pages Still Load Slowly After Using Linked Views

Linked view loads too many rows

If your linked view still shows hundreds of rows, the filter is too broad. Narrow the filter to a specific status, assignee, or date range. Each additional filter condition eliminates rows from the render queue. For dashboards, consider using a filter that shows only the current week or current project phase.

Page has too many linked views

Each linked view is a separate database query. If a single page contains more than 10 linked views, the cumulative load can offset the benefit. Consolidate views where possible. Instead of five linked views showing different statuses, use one linked view with a grouped board view. Grouping by status shows all statuses in one block.

Linked view includes rollups and formulas

Rollup and formula properties require Notion to compute values for each visible row. If your linked view shows 50 rows and each row has three rollups, the page must run 150 calculations. Hide rollup and formula columns in the Properties menu unless the reader needs them. Create a separate linked view with those columns for editing purposes only.

Master database itself is too large

A master database with more than 10,000 rows can slow down all linked views that reference it. Archive or delete rows that are no longer needed. Use the Archive option on the row menu to move completed items out of the active database. This reduces the index size that Notion must scan when building each linked view.

Linked View vs Full Database Block: Load Performance Compared

Item	Full Database Block	Linked View
Data source	Embedded copy of the database	Reference to the master database
Rows loaded on page open	All rows in the database	Only rows matching the filter
Columns rendered	All properties	Only visible properties
Page load time with 500 rows	3–5 seconds	0.5–1 second
Ability to edit master data	Yes, edits sync to master	Yes, edits sync to master
Multiple views on one page	Only one view per database block	Multiple linked views with different filters

You can now create linked views that display only the rows and properties your team needs, reducing page load time significantly. Start by replacing your largest full database blocks with linked views that have strict filters. For advanced optimization, combine linked views with the Group feature in Board and Timeline views to collapse sections that are not immediately visible. This technique reduces the initial render cost even further.