When your Notion workspace feels sluggish, certain pages may be responsible for the slowdown. Large databases, excessive blocks, and complex formulas can increase page load time. This article explains how to use Notion’s built-in workspace audit log and page analytics to find the slowest pages. You will learn to pinpoint high-block-count pages and reduce their impact on performance.
Key Takeaways: Finding and Fixing Slow Pages in Notion
- Settings & Members > Workspace > Audit log: View a list of actions like page creation and edits to identify pages with the most changes.
- Page analytics (right sidebar): Check the block count for any page to see if it exceeds 1,000 blocks.
- Database properties > Formula columns: Complex formulas with many nested functions can cause slow load times for database views.
Why Some Notion Pages Load Slowly
Notion pages load content as you scroll. This lazy-loading method keeps initial load time short for most pages. However, pages with many blocks, large embedded files, or complex database views force Notion to process more data in the background. The most common cause of slow pages is a high block count. A block is any element in Notion: a text paragraph, an image, a database row, or a to-do item. When a page has more than 1,000 blocks, the browser struggles to render all elements quickly. Another cause is database views with many linked records or formula columns that recalculate every time the view opens. Notion’s workspace audit log does not directly show page load time, but it lists every action taken in the workspace. By analyzing the audit log, you can find pages that receive the most edits and have the highest chance of being overloaded.
Block Count and Page Performance
Each block in a Notion page adds to the total DOM size in the browser. Pages with 2,000 or more blocks often take 3 to 5 seconds to load. Pages with 5,000 or more blocks can take over 10 seconds. The block count includes all sub-pages, database entries, and inline databases. A single database with 500 rows counts as 500 blocks. If each row has its own page, each row page adds additional blocks.
Database Formula Impact
Formula columns in databases recalculate every time the database view loads or a property changes. Formulas that use nested if statements, date calculations, or rollups from other databases can increase load time by 1 to 2 seconds per formula column. Databases with more than 10 formula columns are especially affected.
Steps to Identify Slow Pages Using Workspace Audit
The workspace audit log records every action performed by members. You can use this log to find pages that have the most activity. Pages with many edits are more likely to be large and slow. Follow these steps to access the audit log and filter for high-activity pages.
- Open Workspace Settings
Click Settings & Members in the left sidebar. This opens the workspace settings panel. - Navigate to Audit Log
In the settings panel, click Workspace in the left menu. Then click Audit log. The audit log shows a list of actions sorted by date, with the most recent action first. - Filter by Action Type
Click the Filter button at the top of the audit log. Select Page created or Page edited to focus on page-related actions. This removes noise from other actions like member invite or integration changes. - Sort by Date Range
Use the date range filter to look at the last 7 days or 30 days. A page that appears many times in a short period is likely being actively edited and may have grown large. - Note the Page Names
Scroll through the filtered list and write down the page names that appear most frequently. You can click on any action to see the page title and the user who performed it. - Open Each Candidate Page
Open each page you noted. Wait for the page to fully load. If the page takes more than 3 seconds to load, it is a candidate for optimization. - Check Block Count in Page Analytics
While on the page, click the Show page analytics button in the top-right corner of the page. It looks like a small graph icon. A panel opens on the right side showing the total block count. If the block count is above 1,000, the page is likely causing slowdowns.
If Notion Still Has Slow Pages After the Audit
After identifying slow pages, you can take steps to reduce their block count. Some pages may still load slowly even after you reduce blocks. The following issues and solutions address common remaining problems.
Database View Still Loads Slowly After Reducing Rows
If a database view still takes more than 5 seconds to load, check the number of linked databases. Each linked database view loads all records from the source database. To fix this, create a filtered view that shows only the records you need. For example, create a view that filters by a date range or a specific property.
Page Analytics Shows Block Count but Page Still Feels Slow
A page may have a moderate block count but still feel slow because of embedded content. Large images, PDF files, or videos embedded directly in the page increase load time. Replace embedded files with links. Right-click the embedded file and select Copy link. Then delete the embedded block and paste the link as text.
Audit Log Does Not Show Enough Detail
The audit log shows page names but not block counts. To get a more complete picture, use the page analytics feature for every page you suspect is slow. You can also export the workspace data as a CSV and analyze block counts offline. Go to Settings & Members > Workspace > Export all workspace content. Choose Markdown & CSV format. The export includes a CSV file with page metadata, but block count is not directly included. Instead, you can estimate page size by checking the exported file size.
Audit Log vs Page Analytics: What Each Shows
| Feature | Audit Log | Page Analytics |
|---|---|---|
| Data shown | List of actions (create, edit, delete) with timestamps and user names | Block count, word count, and last edited date for a single page |
| Best use | Find pages with the most recent activity or highest edit frequency | Check exact block count to confirm if a page is overloaded |
| Access method | Settings & Members > Workspace > Audit log | Click the graph icon in the top-right corner of any page |
| Exportable | Yes, as CSV | No |
| Limitation | Does not show block count or page size | Only works on pages you have permission to open |
Using both tools together gives you a complete picture. Start with the audit log to find high-activity pages, then use page analytics to confirm which ones are large. This two-step method helps you focus on the pages that need optimization most.
You can now identify slow pages in your Notion workspace using the audit log and page analytics. Start by filtering the audit log for page edits and note the most active pages. Then check the block count for each candidate page using the page analytics button. For pages with more than 1,000 blocks, reduce block count by moving content to sub-pages or linking files instead of embedding them. As an advanced tip, consider using the Export workspace feature to download a CSV of the audit log and sort by action count in Excel or Google Sheets to find the most edited pages instantly.