Start
On this page

How to improve Notion website speed

Focus on the page content you control and measure the public URL visitors actually use.

Updated September 7, 2026 · Layzr

A native Notion Site and a website published through a third-party Notion wrapper can have different performance problems. First identify which one you use. On a native Notion Site, start with the content and embeds you can edit; server configuration and the application's JavaScript delivery are managed by the platform.

Do not troubleshoot the editor's loading time as though it were the public website. Open the published URL while signed out, on the device a visitor would use.

1. Establish a public-page baseline

  1. Copy the live public URL, including the custom domain if that is what visitors use. Confirm it opens without a Notion login.
  2. Open Layzr, sign in, paste the public URL, choose General audit and select Mobile or Desktop. Run the audit and record the available LCP and CLS metrics from Scores alongside the device and URL.
  3. Test a short text page from the same site as a comparison. If both are equally slow, the problem may extend beyond the content of the longer page.
  4. Open the slow page on a phone. Observe what appears late: the cover, an embedded video, a database view or the page as a whole.

2. Test images and embedded content

Make a duplicate test page before removing content from an important live page. Change one thing at a time, publish the test and compare it under similar conditions. Your first experiment should target an element you saw loading late, rather than an arbitrary image-size rule.

  • Replace a large animated cover with a still image and compare the loading metric.
  • Replace an embedded video, map or presentation with a descriptive link when visitors do not need to interact with it on the page.
  • Move secondary galleries or long reference material to a linked subpage if doing so makes the first page easier to use.
  • Test whether a simpler database presentation improves the visitor's experience. Keep the information needed to complete the task visible.

3. Separate content from the publishing service

If you use a third-party publishing service, check that service's documentation for custom scripts, fonts, caching and analytics. Test optional scripts one at a time. Advice about a WordPress cache plugin or editing a Next.js server does not apply to a native Notion Site.

If the simple comparison page remains slow too, record the test time, region and reports before contacting the relevant platform. Keep an alternate lightweight page available for a critical campaign if you cannot resolve the issue within your publishing controls.

4. Keep the page useful after simplifying it

Repeat the public mobile test, open every important link and confirm the page is still published. Check that visitors can understand the offer without opening several subpages. Removing essential explanation to raise a score can make the site less useful.

Performance and search visibility are separate checks. Notion has publishing and search discoverability settings; confirm the intended page is public and eligible for discovery. If it already gets impressions, use the Search Console diagnosis guide before assuming that speed explains the missing clicks.

Documentation

Check the page beyond loading speed

Review whether the headline, layout and next action make sense to a first-time visitor.

Use the landing page audit checklist