Developers

Search

What is Traffic-aware Pre-Rendering (TPR)?

Framer sites use Traffic-aware Pre-Rendering (TPR), which makes large sites build & optimize in seconds. TPR scales infinitely without impact on performance.

How TPR works

  • We optimize each page on first visit and cache the result until the next publish.

  • We pre-render and optimize your most-visited pages on publish based on live traffic data so your most clicked pages are always served optimized, and you’ll know about any issues right away.

  • A small share of visits (typically < 1%) may see an unoptimized version if a page hasn’t been visited since the last publish. If a website has 10,000 pages, 90% of traffic usually goes to 5 to 20 pages, so this won’t affect aggregated performance scores or SEO.

  • Warnings and errors are also generated on visit. If an error could significantly impact a page, we’ll email you. These cases are rare.

  • Crawlers that rely on static, optimized content (i.e., don’t run JavaScript) fall back to the latest available optimized version, never the unoptimized one.

Updated status labels

How TPR works

  • We optimize each page on first visit and cache the result until the next publish.

  • We pre-render and optimize your most-visited pages on publish based on live traffic data so your most clicked pages are always served optimized, and you’ll know about any issues right away.

  • A small share of visits (typically < 1%) may see an unoptimized version if a page hasn’t been visited since the last publish. If a website has 10,000 pages, 90% of traffic usually goes to 5 to 20 pages, so this won’t affect aggregated performance scores or SEO.

  • Warnings and errors are also generated on visit. If an error could significantly impact a page, we’ll email you. These cases are rare.

  • Crawlers that rely on static, optimized content (i.e., don’t run JavaScript) fall back to the latest available optimized version, never the unoptimized one.

Updated status labels

FAQ

  • How does dynamic optimization work in Framer?

    Each page is optimized on the first visit and the result is cached until the next publish. A small share of visits (typically less than 1%) may see an unoptimized version if a page hasn’t been visited since the last publish, but this won’t affect aggregated performance scores or SEO.

  • Will crawlers or SEO be affected if a page is served unoptimized?

    No, crawlers that rely on static, optimized content fall back to the latest available optimized version and never see the unoptimized one. This ensures that SEO and aggregated performance scores are not affected.

  • What do the new status labels 'Pre-Optimizing' and 'Ready' mean?

    'Pre-Optimizing' (previously 'Optimizing') means Framer is preparing dynamic optimization and optimizing top pages. 'Ready' (previously 'Optimized') means top pages are optimized and the rest are ready for dynamic optimization.

  • What is the advantage of Traffic-aware Pre-Rendering?

    With TPR, popular pages automatically get pre-rendered right on publish based on live traffic data of your site. This means your most important pages are always optimized first, which improves Core Web Vitals like LCP and how fast the site becomes interactive.

Updated

Related articles

Access your robots.txt file

Address optimization warnings in your project

Are multiple H1 tags in Framer a problem?

Fixing uncrawlable overlay content

Guide to Lighthouse scores