Fix Notion Public Page Loading Slowly From Specific Geographic Regions

You have a Notion public page that loads fast for you but takes more than 10 seconds to open for visitors in Europe, Asia, or South America. This delay happens because Notion uses content delivery network (CDN) nodes that are not optimally distributed for all global regions. This article explains why geographic distance causes slow load times and provides three concrete fixes you can apply today.

Why Notion Public Pages Load Slowly From Distant Regions

Notion stores all page data on servers located in the United States (US East and US West regions) and in the European Union (Frankfurt, Germany). When a visitor in Southeast Asia or South America requests a public page, the data must travel thousands of miles across undersea cables and multiple internet exchange points. Each network hop adds 30 to 150 milliseconds of latency. After six or more hops, the total delay can exceed 2 seconds just for the initial connection.

Additionally, Notion uses a single CDN provider (Fastly) that has 60+ points of presence worldwide. However, Notion’s public page serving architecture does not cache the full page content at the edge by default. Only static assets such as JavaScript bundles and CSS files are cached. The page’s actual text and database content is fetched live from Notion’s origin servers for every request. This means a visitor in Australia must wait for a roundtrip to a US East server every time they reload the page.

The problem is compounded when the page contains embedded content from third-party services such as Google Docs, YouTube, or Miro. Each embed triggers its own DNS lookup and connection to a server that may be even farther away. The combination of uncached page content, large images, and remote embeds can push load time past 10 seconds for users in regions far from Notion’s data centers.

Steps to Reduce Public Page Load Time for Global Visitors

The following three methods address different parts of the slow-loading pipeline. Apply them in order for the best results.

Method 1: Use a Third-Party Global CDN Proxy

A reverse proxy CDN like Cloudflare can cache the entire Notion public page and serve it from 200+ edge locations. This bypasses Notion’s origin server for most requests.

1. Create a Cloudflare account
   Go to cloudflare.com and sign up for a free plan. The free tier includes a global CDN with caching and SSL termination.
2. Add your custom domain to Cloudflare
   Enter your domain name (for example, docs.example.com) in the Cloudflare dashboard. Cloudflare scans existing DNS records.
3. Configure a CNAME record pointing to Notion’s public page
   In Cloudflare DNS settings, create a CNAME record. Set the name to the subdomain you want to use. Set the target to the Notion public page URL, for example, yourworkspace.notion.site. Enable the orange cloud icon to proxy traffic through Cloudflare.
4. Enable caching rules for the Notion page path
   Go to Rules > Page Rules. Create a rule for docs.example.com/. Set Cache Level to Standard and Edge Cache TTL to 4 hours. This tells Cloudflare to cache the full page HTML and serve it from the nearest edge node.
5. Update your Notion public page sharing link
   Replace the default Notion link with your custom domain. In Notion, open the page, click Share, and copy the public link. Use a URL redirect or a custom link service to point visitors to your Cloudflare domain.

Method 2: Optimize Page Content for Faster Loading

Reducing the size of page assets helps regardless of CDN placement. Follow these steps for every public page.

1. Compress all images before uploading
   Use an image compression tool like TinyPNG or Squoosh to reduce JPEG and PNG files to under 200 KB. In Notion, drag the compressed image onto the page instead of the original.
2. Remove or replace heavy embeds
   Embedded Google Docs, Figma files, and Loom videos add significant load time. Replace them with static screenshots or links that open in a new tab. Right-click the embed block and select Delete.
3. Limit database views to 50 rows or fewer
   If your public page contains a linked database, set a filter that limits results to 50 items. Large database views force the page to download all row data before rendering.
4. Remove unused blocks and empty sections
   Scroll through the page and delete any empty toggle blocks, dividers, or callout boxes. Each block adds to the DOM size and processing time.

Method 3: Enable Notion Enterprise CDN Caching

Notion Enterprise plans include an option to cache public pages at the CDN edge for up to 24 hours. This feature is not available on Free, Plus, or Business plans.

1. Contact your Notion account manager
   Request activation of the Edge Cache feature for your workspace. Provide the specific public page URLs that need improvement.
2. Verify the cache header in browser DevTools
   After activation, open Chrome DevTools on the public page. Go to the Network tab and reload the page. Look for the Cache-Control header. A value of public, max-age=86400 confirms edge caching is active.
3. Test from multiple geographic locations
   Use a tool like Pingdom Website Speed Test or GTmetrix to test the page from servers in London, Tokyo, and Sao Paulo. Compare the load time before and after enabling edge caching.

If Notion Public Pages Still Load Slowly After the Main Fix

Cloudflare Caching Does Not Serve Fresh Content

When you update a Notion public page, Cloudflare may still serve the old cached version for up to 4 hours. To fix this, go to Cloudflare dashboard, select Caching > Purge Everything. This clears the cache for your entire domain. Visitors will see the latest version on the next request. For ongoing updates, set the Edge Cache TTL to 30 minutes instead of 4 hours.

Third-Party Embeds Still Cause Delays in Asia-Pacific Regions

Embedded YouTube videos and Google Maps widgets often load from servers that are blocked or throttled in certain countries. Replace these embeds with static images that link to the original content. Right-click the embed block, select Duplicate, then delete the original embed. Upload a screenshot and add a hyperlink to the external resource.

Notion Public Page Shows Blank White Screen for Mobile Users

Some mobile networks in developing regions use aggressive caching proxies that break Notion’s JavaScript. Instruct mobile visitors to open the page in Chrome or Safari with Private Browsing mode enabled. Alternatively, use a tool like AMP (Accelerated Mobile Pages) to create a simplified version of the page. Notion does not natively support AMP, so you must use a third-party service like Cloudflare AMP Real URL.

Notion Public Page Loading Options Compared

Item	Default Notion Public Page	With Cloudflare Proxy
Global edge locations	60+ (Fastly, static assets only)	200+ (Cloudflare, full page cached)
Page content caching	No (fetched live from origin)	Yes (configurable TTL)
Load time from Asia (median)	8–12 seconds	1.5–3 seconds
Setup complexity	None	15 minutes (DNS + page rules)
Custom domain support	No	Yes

Notion’s built-in sharing works for local or US-based audiences. The Cloudflare proxy method is essential for teams with a global user base.

You can now reduce Notion public page load time for visitors in Europe, Asia, Africa, and South America by setting up a Cloudflare reverse proxy or by enabling Notion Enterprise edge caching. Start by compressing all images and removing heavy embeds — this alone can cut load time by 40 percent. For the best global performance, combine Cloudflare caching with a cache purge schedule after each page update. Test your page from at least three continents using Pingdom to confirm the improvement.