导航|地址|刷新
developers.cloudflare.com



--- description: Optimize your website performance with Cloudflare Speed tools and settings. title: Speed image: https://developers.cloudflare.com/og-docs.png --- [Skip to content](#main-content) > Documentation Index > Fetch the complete documentation index at: https://developers.cloudflare.com/speed/llms.txt > Use this file to discover all available pages before exploring further. # Speed Last updated Jun 15, 2026|Copy as Markdown|[View as Markdown](https://developers.cloudflare.com/speed/index.md)|[Agent setup](https://developers.cloudflare.com/agent-setup/) Improve the performance of your website or web application. Available on all plans Speed allows you to assess the performance of your website and get recommendations of Cloudflare products to enhance the website performance. --- ## Features [Observatory](https://developers.cloudflare.com/speed/observatory/) Use Observatory to conduct tests with both synthetic and real user data to identify potential website performance enhancements. Use Observatory [Origin Analytics](https://developers.cloudflare.com/speed/origin-analytics/) See how your origin server responds to Cloudflare. Identify slow endpoints, monitor response times, and diagnose errors. Use Origin Analytics [Settings](https://developers.cloudflare.com/speed/optimization/) Get recommendations of Cloudflare products and settings to improve your website’s performance. Use Settings [Aggregated Internet Measurement](https://developers.cloudflare.com/speed/aim/) Understand your Internet quality to identify scenarios that your Internet connection is good or bad for. Use Aggregated Internet Measurement --- ## Related products [Cache rules](https://developers.cloudflare.com/cache/how-to/cache-rules/) Customize the cache properties of your HTTP requests. [Cloudflare Web Analytics](https://developers.cloudflare.com/web-analytics/) Understand the performance of your webpages as experienced by your site visitors. [Cloudflare Image Resizing](https://developers.cloudflare.com/images/optimization/transformations/overview/) Transform images on Cloudflare's edge platform: resize, adjust quality, and convert images to WebP or AVIF format on demand. [Early Hints](https://developers.cloudflare.com/cache/advanced-configuration/early-hints/) Take advantage of "server think time" to asynchronously send instructions to the browser to begin loading resources while the origin server is compiling the full response. --- ## More resources ### [Quotas](https://developers.cloudflare.com/speed/observatory/run-speed-test/#quotas) Learn about the quota limits for the number of tests you can run per month. ### [Community Forum](https://community.cloudflare.com/c/website-application-performance/88) Engage with other users and explore more resources on Cloudflare support forum. Was this helpful? YesNo ## On this page [Docs](https://developers.cloudflare.com/) ```json {"@context":"https://schema.org","@type":"WebPage","@id":"https://developers.cloudflare.com/speed/#page","headline":"Speed · Cloudflare Speed docs","description":"Optimize your website performance with Cloudflare Speed tools and settings.","url":"https://developers.cloudflare.com/speed/","inLanguage":"en","image":"https://developers.cloudflare.com/og-docs.png","dateModified":"2026-06-15","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}} ``` --- --- description: Test and monitor your website performance with Cloudflare Observatory. title: Observatory (beta) image: https://developers.cloudflare.com/og-docs.png --- [Skip to content](#main-content) > Documentation Index > Fetch the complete documentation index at: https://developers.cloudflare.com/speed/llms.txt > Use this file to discover all available pages before exploring further. # Observatory (beta) Last updated Jun 15, 2026|Copy as Markdown|[View as Markdown](https://developers.cloudflare.com/speed/observatory/index.md)|[Agent setup](https://developers.cloudflare.com/agent-setup/) Observatory uses synthetic tests and real user data from browsers to assess the performance of your website. These data sources produce metrics that provide different types of insights into your website’s performance. Cloudflare then uses the analysis run by Observatory to recommend optimizations with the tools that best suit your performance issues. ## Synthetic tests As its name suggests, synthetic testing uses servers to simulate the conditions that a user might encounter when accessing your website. This has the advantage of being consistent, as the conditions are easily replicated each time the test is run. It also allows you to have an analysis of how a code change might affect the overall performance of your website, as well as test any URL you want. However, due to its synthetic nature, it cannot replicate the breadth and diversity of different conditions that real users will experience. Observatory provides two different types of synthetic tests: ### Browser test The browser test loads the requested page in a headless browser and runs Google Lighthouse on it. This reports key performance metrics and provides light suggestions for improvement. ### Network test The network test is focused on giving a detailed breakdown of the network and back-end performance of an endpoint. For more information on metrics collected, refer to [Network monitoring metrics](https://developers.cloudflare.com/speed/observatory/test-results/#network-monitoring-metrics). ### Network comparison test You can also compare network tests in Observatory by selecting any two completed tests. The results for each test are displayed side by side as histograms, allowing you to easily visualize and compare the full distribution of data points across both tests. ## Real user monitoring (RUM) Real user monitoring (also known as RUM), on the other hand, captures real metrics from real users accessing a website. This provides information that synthetic tests cannot capture, as users might access your website from different parts of the world, with different network conditions, ISPs, browsers and computer hardware. However, RUM data is only applied to your own website. Real user data also includes two user interaction metrics that synthetic tests do not offer - [First Input Delay (FID) ↗](https://web.dev/fid/) and [Interaction to Next Paint (INP) ↗](https://web.dev/inp/). Free customers have RUM enabled automatically, with EU traffic excluded, and can switch it off if they prefer. Customers on other plans may enable RUM as needed. [Run test](https://developers.cloudflare.com/speed/observatory/run-speed-test/) Was this helpful? YesNo ## On this page [Docs](https://developers.cloudflare.com/) ```json {"@context":"https://schema.org","@type":"WebPage","@id":"https://developers.cloudflare.com/speed/observatory/#page","headline":"Observatory (beta) · Cloudflare Speed docs","description":"Test and monitor your website performance with Cloudflare Observatory.","url":"https://developers.cloudflare.com/speed/observatory/","inLanguage":"en","image":"https://developers.cloudflare.com/og-docs.png","dateModified":"2026-06-15","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}} ``` --- --- description: View speed test history and performance trends in the Observatory dashboard. title: Observatory dashboard image: https://developers.cloudflare.com/og-docs.png --- [Skip to content](#main-content) > Documentation Index > Fetch the complete documentation index at: https://developers.cloudflare.com/speed/llms.txt > Use this file to discover all available pages before exploring further. # Observatory dashboard Last updated Apr 16, 2026|Copy as Markdown|[View as Markdown](https://developers.cloudflare.com/speed/observatory/dashboard/index.md)|[Agent setup](https://developers.cloudflare.com/agent-setup/) The Observatory overview dashboard provides a single view of your zone's performance over the past seven days. It combines synthetic monitoring, real user data, and Cloudflare's analysis to help you quickly identify performance bottlenecks and receive actionable recommendations. ## Suggestions The **Suggestions** panel highlights tailored optimizations you can make to improve performance. Examples include: * Reduce Largest Contentful Paint (LCP) with Polish. * Reduce Time to First Byte (TTFB) with Argo Smart Routing. These recommendations will vary based on your site's observed performance. Selecting a suggestion expands it to show more detail: * **Why you're seeing this**: Explains the performance issue detected. * **What you can do**: Lists recommended actions you can take. ## Core Web Vitals The dashboard integrates **Core Web Vitals**, showing values at the 75th percentile (p75). These metrics reflect real user experiences: * **Largest Contentful Paint (LCP)**: How quickly the main content of a page becomes visible. * **Interaction to Next Paint (INP)**: How responsive the site is to user interactions. * **Cumulative Layout Shift (CLS)**: How visually stable the page layout is. If insufficient real user data is available, metrics may show as **No data**. ## Network Performance The **Network Performance** section shows timing data that can help pinpoint where latency occurs. * **Time to First Byte (TTFB)**: Measures the time between the initial request and the first byte of the response. * **Time to Last Byte (TTLB) Breakdown**: Provides a breakdown of response phases: * DNS resolution time * TCP connection time * Request processing time at the server * Response transfer time This breakdown helps identify whether delays are caused by DNS, connection setup, server processing, or response delivery. ## HTTP Traffic The **HTTP Traffic** section shows how traffic is handled between Cloudflare and your origin server: * **Served by**: Percentage of requests served from Cloudflare versus from your origin. * **4xx errors**: Client errors, broken down by Cloudflare edge versus origin. * **5xx errors**: Server errors, broken down by Cloudflare edge versus origin. This view helps distinguish between Cloudflare-side issues and origin-side issues. ## Synthetic Monitoring The **Synthetic Monitoring** table shows automated test results for your site. Each row includes: * **URL tested** * **Last test run** * **Repeats** (if scheduled multiple times) * **Score** (Pass/Fail) Synthetic monitoring allows you to proactively test site availability and performance under consistent conditions, complementing real user monitoring (RUM). ## Using the dashboard Use the Speed Overview dashboard to: * Review **Suggestions** for actionable optimizations. * Track **Core Web Vitals** to ensure a good user experience. * Analyze **Network Performance** to identify latency bottlenecks. * Diagnose errors with **HTTP Traffic** insights. * Confirm site reliability using **Synthetic Monitoring** results. Was this helpful? YesNo ## On this page [Docs](https://developers.cloudflare.com/) ```json {"@context":"https://schema.org","@type":"TechArticle","@id":"https://developers.cloudflare.com/speed/observatory/dashboard/#page","headline":"Observatory dashboard · Cloudflare Speed docs","description":"View speed test history and performance trends in the Observatory dashboard.","url":"https://developers.cloudflare.com/speed/observatory/dashboard/","inLanguage":"en","image":"https://developers.cloudflare.com/og-docs.png","dateModified":"2026-04-16","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}} ``` --- --- description: Find answers to common questions about Cloudflare Observatory. title: FAQ image: https://developers.cloudflare.com/og-docs.png --- [Skip to content](#main-content) > Documentation Index > Fetch the complete documentation index at: https://developers.cloudflare.com/speed/llms.txt > Use this file to discover all available pages before exploring further. # FAQ Last updated Apr 16, 2026|Copy as Markdown|[View as Markdown](https://developers.cloudflare.com/speed/observatory/faq/index.md)|[Agent setup](https://developers.cloudflare.com/agent-setup/) Below you will find answers to our most commonly asked questions. If you cannot find the answer you are looking for, refer to the [community page ↗](https://community.cloudflare.com/c/website-application-performance/88) to explore more resources. ## How long does it take for a test to load? It can vary from about 25 seconds to over a minute. If you leave your speed tab open, your test is still going to run. You can leave and return and still see your test results. ## Are query parameters or anchors supported in tested URLs? No. At the moment, any query parameter or anchor appended to the tested URL are dropped. For example, using the `https://example.com/blog/?utm_medium=social#title` URL, the Observatory will discard the `?utm_medium=social` query parameter as well as the `#title` anchor. The tested URL will actually be `https://example.com/blog/`. ## I get a `403` response when rerunning the website analysis? Check your WAF custom rules to make sure that you are not blocking traffic from Observatory to request your site. Note For **IPv6** Cloudflare Observatory tests originate from **ASN 15169** or **ASN 132892** and are generated with the following user agents: * Mozilla/5.0 (Linux; Android 11; Moto G Power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 * Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 For **IPv4** Cloudflare Observatory tests originate from **ASN 396982** and are generated with the following user agents: * Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36 CloudflareObservatory/1.0 * Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0 ## Why might users not see any Real User Monitoring (RUM) data on the map in Observatory? There are several reasons why users might not see any Real User Monitoring (RUM) data on the map in Observatory: * Time Required for RUM Data Population: Populating the RUM database takes some time. It means that newly enabled RUM might not have immediate data available, and users may need to wait for some time before RUM data starts appearing on the map. * Progressive Sampling: RUM data is progressively sampled, which means that not all requests are captured. Some requests may pass through the sampling period, resulting in incomplete or missing data points on the map. * Adblockers Impact on RUM Data: RUM data collection relies on third-party JavaScript executing on the real-user browser. However, adblockers or similar browser extensions can block this script, preventing the collection of RUM data, and thereby affecting the completeness of the analytics presented on the map. * The RUM feature needs to be enabled and configured in your environment. If it has not been turned on, or if configuration is incomplete, RUM data may not appear. ## What are the potential reasons for discrepancies between RUM analytics and traffic analytics in Observatory? Differences between Real User Monitoring (RUM) analytics and traffic analytics in Observatory can occur due to the following reasons: * Adblockers Impact on RUM Data: Similar to the previous point, RUM data collection can be thwarted by adblockers, leading to missed data. Since traffic analytics typically rely on server-side data collection, they may not be as affected by adblockers as RUM. * Progressive Sampling in RUM: RUM data is collected through progressive sampling, which means that not all user requests are captured. This sampling method could result in slight variations in analytics when compared to traditional traffic analytics that record every server request. ## How do I disable Real User Monitoring (RUM) if it has been enabled from the Observatory test result page? Enabling RUM creates a Web Analytics configuration entry for the hostname at the account level. If you wish to disable RUM, follow these steps: 1. In the Cloudflare dashboard, go to the **Web Analytics** page. [Go to **Web analytics** ↗](https://dash.cloudflare.com/?to=/:account/web-analytics) 2. Select **Manage Site** for the hostname for which you wish to disable RUM. 3. Select **Delete**. Was this helpful? YesNo ## On this page [Docs](https://developers.cloudflare.com/) ```json {"@context":"https://schema.org","@type":"TechArticle","@id":"https://developers.cloudflare.com/speed/observatory/faq/#page","headline":"FAQ · Cloudflare Speed docs","description":"Find answers to common questions about Cloudflare Observatory.","url":"https://developers.cloudflare.com/speed/observatory/faq/","inLanguage":"en","image":"https://developers.cloudflare.com/og-docs.png","dateModified":"2026-04-16","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}} ``` --- --- description: Collect real user performance metrics with the RUM beacon. title: RUM beacon for Web Analytics image: https://developers.cloudflare.com/og-docs.png --- [Skip to content](#main-content) > Documentation Index > Fetch the complete documentation index at: https://developers.cloudflare.com/speed/llms.txt > Use this file to discover all available pages before exploring further. # RUM beacon for Web Analytics Last updated Jun 30, 2026|Copy as Markdown|[View as Markdown](https://developers.cloudflare.com/speed/observatory/rum-beacon/index.md)|[Agent setup](https://developers.cloudflare.com/agent-setup/) The RUM beacon is a JavaScript snippet that runs when a Cloudflare customer enables RUM through [Web Analytics](https://developers.cloudflare.com/web-analytics/) or [Observatory](https://developers.cloudflare.com/speed/observatory/). This script runs in users' browsers when they visit the customer's site, and its purpose is to collect performance-related data, for example, page load time, and send it to Cloudflare's systems for processing. This [data](https://developers.cloudflare.com/web-analytics/data-metrics/) is then presented to the customer, providing valuable insights into the website's performance and usage. The RUM beacon script can be enabled into a webpage in two ways: * **One-click setup**: For [sites proxied through Cloudflare](https://developers.cloudflare.com/web-analytics/get-started/#sites-proxied-through-cloudflare) that have Web Analytics enabled, the snippet can be _automatically_ injected into pages as the HTML response passes through Cloudflare's edge network to the browser by simply enabling the automatic injection option. * **Manual setup**: Websites can _manually_ add the script by embedding a code snippet into their pages. Refer to the [Sites not proxied through Cloudflare section](https://developers.cloudflare.com/web-analytics/get-started/#sites-not-proxied-through-cloudflare), for more information about how to manually insert the snippet into your HTML. ## Data collection Once downloaded to the browser, the RUM beacon script runs as JavaScript in the browser. It collects performance data from browser [APIs ↗](https://developer.mozilla.org/en-US/docs/Web/API/Performance%5FAPI) and sends this data to Cloudflare for processing. The data collected from the browser is summarized in the table below: | Field | Example | Description | How it is collected | | -------------------- | ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | pageloadId | 0c698922-8d60-40bf-85ac-7982b5f8034d | The unique ID for the page. | Generated in the browser code. | | referrer | [https://cfrumtest.com/ ↗](https://cfrumtest.com/) | The referring page URL. | If it is a multi-page application (MPA), then it is generated from [document.referrer ↗](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer). If it is a single-page application (SPA), then it is generated from a local in-memory variable in the beacon code which stores previous URLs. | | startTime | 1693488419352 | Baseline for performance-related timestamps. | [performance.timeOrigin ↗](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin) | | memory | { totalJSHeapSize: 39973671, usedJSHeapSize: 39127515, jsHeapSizeLimit: 4294705152 } | Measures memory heap size. | [performance.memory ↗](https://developer.mozilla.org/en-US/docs/Web/API/Performance/memory) (deprecated) | | timings | Object of [PerformanceTiming ↗](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceTiming) | Timing data. | [performance.timing ↗](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) (deprecated, fallback when timingV2 is unavailable) | | timingV2 | Array of [PerformanceNavigationTiming ↗](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) | Navigation timing data. | [performance.getEntriesByType("navigation") ↗](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType) | | resources | Array of [PerformanceResourceTiming ↗](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming) | Resource timing data. | [performance.getEntriesByType("resource") ↗](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming) | | firstPaint | Array of [PerformancePaintTiming ↗](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) | Paint timing data. | [performance.getEntriesByType("paint") ↗](https://developer.mozilla.org/en-US/docs/Web/API/PerformancePaintTiming) | | firstContentfulPaint | 209 | First Contentful Paint metric. | [web-vitals module ↗](https://www.npmjs.com/package/web-vitals) [1](#user-content-fn-1) | | FCP | 209 | First Contentful Paint metric. | [web-vitals module ↗](https://www.npmjs.com/package/web-vitals) [1](#user-content-fn-1) | | LCP | 209 | Largest Contentful Paint metric. | [web-vitals module ↗](https://www.npmjs.com/package/web-vitals) [1](#user-content-fn-1) | | CLS | 0.001 | Cumulative Layout Shift metric. | [web-vitals module ↗](https://www.npmjs.com/package/web-vitals) [1](#user-content-fn-1) | | | | | | | TTFB | 0.03 | Time to First Byte metric. | [web-vitals module ↗](https://www.npmjs.com/package/web-vitals) [1](#user-content-fn-1) | | INP | 1.23 | Interaction to Next Paint metric. | [web-vitals module ↗](https://www.npmjs.com/package/web-vitals) [1](#user-content-fn-1) | | landingPath | [https://cfrumtest.com/ ↗](https://cfrumtest.com/) | The landing page URL. | [performance.getEntriesByType("navigation") ↗](https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntriesByType) | ## Data processing RUM data is generally processed at the nearest Cloudflare data center based on how the incoming request is routed. This is determined by a number of factors including [Anycast ↗](https://www.cloudflare.com/en-gb/learning/cdn/glossary/anycast-network/) and [Unimog ↗](https://blog.cloudflare.com/unimog-cloudflares-edge-load-balancer/). Since RUM data does not use location services, it may be processed in a different country or region from where it originated. Although the RUM service receives the client/source IP address from the beacon as part of normal HTTP request handling process, it discards the IP address at the nearest Cloudflare data center and does not store it in core databases or logs. ## Privacy information The RUM beacon script does not store any data in the browser or access any storage data, such as [cookies ↗](https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie), [localStorage ↗](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage), [sessionStorage ↗](https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage), IP address, or [IndexedDB ↗](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB%5FAPI/Using%5FIndexedDB). The data we collect is performance data from the browser performance [APIs ↗](https://developer.mozilla.org/en-US/docs/Web/API/Performance%5FAPI). This performance data is ephemeral and only relates to the current webpage that is being viewed. If the user refreshes their browser, all the previous performance data is gone and new performance data starts being available. This data is not stored or accessed from anywhere on the device, it is only available as in-memory data. ## RUM excluding EEA/EU Customers have the option to enable RUM globally or to limit its application to exclude users connecting to Cloudflare data centers in the EEA/EU. If the latter option is selected, the RUM beacon does not process performance data for us
…