To tackle the intricacies of ensuring your web content renders flawlessly across different browsers and devices, especially when Cloudflare is part of your stack, here’s a concise, step-by-step guide to testing your browser’s interaction with Cloudflare services:

👉 Skip the hassle and get the ready to use 100% working script (Link in the comments section of the YouTube Video) (Latest test 31/05/2025)

Check more on: How to Bypass Cloudflare Turnstile & Cloudflare WAF – Reddit, How to Bypass Cloudflare Turnstile, Cloudflare WAF & reCAPTCHA v3 – Medium, How to Bypass Cloudflare Turnstile, WAF & reCAPTCHA v3 – LinkedIn Article

Understand Your Goal: The primary aim is to verify that Cloudflare’s caching, security, and optimization features are behaving as expected from a user’s browser perspective. This isn’t just about loading speed. it’s about checking for correct content delivery, SSL certificate validation, and WAF Web Application Firewall responses.
Basic Browser Checks:
- Developer Tools F12: Open your browser’s developer tools. Go to the “Network” tab.
  - Cache Check: Look for cf-cache-status header in the response. It should show HIT for cached assets, MISS if newly fetched, or DYNAMIC for uncached content.
  - SSL/TLS: Check the “Security” tab to ensure your SSL certificate is valid and issued by Cloudflare or your origin, proxied by Cloudflare. Look for “Connection Secure.”
  - HTTP Headers: Scrutinize other cf- prefixed headers like cf-ray, cf-bgj, cf-obi, etc., which provide insights into Cloudflare’s processing.
- Hard Refresh Ctrl+Shift+R or Cmd+Shift+R: Perform a hard refresh to bypass browser cache and force a new request to Cloudflare. This helps confirm Cloudflare’s caching effectiveness.
Cloudflare Specific Tools:
- cloudflare.com/cdn-cgi/trace: Navigate to this URL. It provides crucial information like fl Cloudflare data center, h your IP address, ip your IP, ts timestamp, visit_scheme HTTP/HTTPS, uag user agent, and colo Cloudflare’s data center code, e.g., LAX for Los Angeles. This tells you which Cloudflare edge server you’re hitting.
- “Is Cloudflare Working?” Checkers: Use third-party tools like dnschecker.org or checkforcloudflare.com to confirm your domain’s DNS is pointing to Cloudflare’s nameservers and that it’s actively protecting your site.
Simulate Different Scenarios:
- Incognito/Private Mode: Use incognito mode to ensure no browser extensions or existing cookies interfere with testing.
- Different Browsers: Test across Chrome, Firefox, Safari, Edge, and even less common browsers to catch rendering or security policy discrepancies.
- Mobile Devices: Use actual mobile devices or device emulation in developer tools to check responsiveness and mobile-specific Cloudflare optimizations.
- Geographic Testing: If possible, use VPNs or proxy services to simulate users from different global locations to check Cloudflare’s global CDN performance and routing colo value in cdn-cgi/trace.
Security Feature Verification:
- WAF Web Application Firewall Rules: If you have WAF rules, try triggering a benign one e.g., attempting a SQL injection string in a search bar if you have rules for it to see if Cloudflare blocks the request and presents a challenge page.
- Bot Management: If configured, observe how Cloudflare handles known bots or suspicious traffic by attempting to access your site with common bot user agents.
Performance Auditing:
- Google Lighthouse/PageSpeed Insights: These tools provide detailed performance reports, often highlighting areas where Cloudflare’s optimizations like image optimization, minification, Brotli compression are effective or could be improved. Look at metrics like FCP First Contentful Paint and LCP Largest Contentful Paint.
- WebPageTest.org: Offers granular waterfall charts and allows testing from various global locations, giving a real-world perspective on load times and Cloudflare’s impact.

Table of Contents

Understanding Cloudflare’s Role in Browser Interaction

Cloudflare acts as a powerful intermediary between your website’s server origin and the end-user’s browser.

It’s not just a Content Delivery Network CDN. it’s a comprehensive platform offering security, performance, and reliability services.

When a browser requests content from a Cloudflare-proxied website, the request first hits one of Cloudflare’s global edge servers.

This strategic positioning allows Cloudflare to intercept, analyze, and optimize traffic before it reaches your origin server, providing a significantly enhanced browsing experience.

From a browser’s perspective, Cloudflare directly serves content, issues SSL certificates, and enforces security policies, making it crucial to understand how browsers interact with this layer.

The Journey of a Browser Request Through Cloudflare

When a user types your website’s URL, the browser initiates a DNS lookup.

If you’re using Cloudflare, your DNS records will point to Cloudflare’s IP addresses, not your origin server’s.

DNS Resolution: The browser resolves your domain to a Cloudflare IP.
Edge Server Connection: The browser establishes a connection ideally HTTPS for security with the nearest Cloudflare edge server.
Request Analysis: Cloudflare inspects the incoming request for potential threats DDoS, malicious bots, WAF rule violations.
Content Serving:
- If the content is cached on the edge server, Cloudflare serves it directly, resulting in a fast cf-cache-status: HIT.
- If not cached, Cloudflare forwards the request to your origin server, fetches the content, caches it if eligible, and then serves it to the browser.
Optimization & Transformation: Cloudflare can perform on-the-fly optimizations like image compression Polish, code minification Auto Minify, and Brotli compression before sending the content to the browser.
Response Delivery: The browser receives the optimized content, rendering the webpage.

Key Cloudflare Features Affecting Browser Performance

Cloudflare’s suite of features is designed to make web browsing faster and more secure.

CDN Content Delivery Network: Caches static assets images, CSS, JavaScript on Cloudflare’s global network of 300+ data centers, reducing latency by serving content from a location geographically closer to the user. This significantly speeds up page load times.
Web Application Firewall WAF: Protects against common web vulnerabilities like SQL injection, cross-site scripting XSS, and DDoS attacks, preventing malicious requests from ever reaching your origin server. For the browser, this means requests might be challenged or blocked if they violate WAF rules.
SSL/TLS Encryption: Provides free Universal SSL, ensuring secure, encrypted connections between the browser and Cloudflare’s edge, preventing eavesdropping and data tampering. Browsers display a padlock icon, signaling a secure connection.
Image Optimization Polish: Compresses images, converts them to modern formats like WebP or AVIF, and serves them to compatible browsers, reducing file sizes without compromising visual quality, thereby accelerating page loads.
Brotli Compression: A more efficient compression algorithm than Gzip, reducing the size of text-based assets HTML, CSS, JS sent to supporting browsers, leading to faster download times.
Argo Smart Routing: Optimizes routes across Cloudflare’s network, bypassing congested internet paths, further reducing latency for dynamic content.
Browser Cache TTL: Cloudflare respects and can enhance browser caching headers, instructing the browser how long to store assets locally, reducing the need for repeated requests.

Essential Browser Developer Tools for Cloudflare Testing

Leveraging your browser’s built-in developer tools is paramount for understanding how Cloudflare interacts with your website and how content is delivered.

These tools provide deep insights into network requests, security headers, and performance metrics, allowing you to debug and verify Cloudflare’s configuration. Check if site uses cloudflare

Inspecting Network Requests and Headers

The “Network” tab in developer tools accessed by pressing F12 or Ctrl+Shift+I on most browsers is your primary window into how resources are loaded.

Request Waterfall: This visual timeline shows the loading sequence of all resources HTML, CSS, JS, images, fonts. It helps identify bottlenecks and understand the impact of caching.
Resource Timing: For each resource, you can see detailed timing breakdowns: DNS lookup, initial connection, SSL handshake, time to first byte TTFB, content download, etc. A low TTFB for cached assets indicates Cloudflare’s CDN is working effectively.
HTTP Headers: This is where Cloudflare’s magic is most visible.
- cf-cache-status: This header is crucial.
  - HIT: The content was served directly from Cloudflare’s cache. This is ideal for static assets.
  - MISS: The content was not in Cloudflare’s cache and was fetched from your origin server.
  - DYNAMIC: Cloudflare is not caching this resource, and it’s always fetched from your origin.
  - EXPIRED: The cached content was expired and Cloudflare revalidated with the origin.
  - REVALIDATED: Cloudflare confirmed with the origin that the cached content is still fresh.
- cf-ray: A unique ID for each request processed by Cloudflare, useful for debugging with Cloudflare support. It typically includes the Cloudflare data center code e.g., LAX for Los Angeles.
- cf-connection-info: Provides details about the connection, such as the protocol HTTP/2, HTTP/3.
- server: cloudflare: Confirms that the response is coming from a Cloudflare server.
- x-content-type-options: nosniff, x-frame-options: SAMEORIGIN, strict-transport-security: These are security headers often added or enforced by Cloudflare to enhance browser security.

Verifying SSL/TLS Status and Security Policies

The “Security” tab in developer tools confirms the integrity and security of the connection between the browser and Cloudflare.

Connection Secure/Insecure: This clearly states whether the connection is encrypted. For Cloudflare, it should always be “Connection Secure.”
Certificate Details: You can inspect the SSL certificate chain.
- Issued To: Should match your domain.
- Issued By: For Universal SSL, it will typically show “Cloudflare, Inc.” as the issuer.
- Validity Dates: Ensure the certificate is within its valid period.
Protocol: Verify that modern, secure protocols like TLS 1.2 or TLS 1.3 are being used, often indicated as HTTP/2 or HTTP/3 QUIC. Cloudflare automatically negotiates the highest supported protocol.
Security Policy Headers:
- Strict-Transport-Security HSTS: Cloudflare can enforce HSTS, which tells browsers to always connect via HTTPS, even if the user types http://.
- Content-Security-Policy CSP: While often configured at the origin, Cloudflare can also enforce or report on CSP, which helps mitigate XSS attacks by restricting sources of content a browser can load.

Utilizing Console for JavaScript Errors and Warnings

The “Console” tab is vital for catching client-side issues that might arise from Cloudflare’s optimizations or conflicts with your site’s JavaScript.

JavaScript Errors: Look for any Uncaught ReferenceError, TypeError, or other script-related errors. Sometimes, Cloudflare’s Auto Minify or Rocket Loader which defers JavaScript loading can introduce subtle timing issues or break poorly written scripts.
Warnings: The console also displays warnings, which might indicate deprecated features, potential performance issues, or security concerns e.g., mixed content warnings where an HTTPS page loads HTTP resources.
Mixed Content Issues: If your site is served over HTTPS by Cloudflare but still attempts to load some assets images, scripts, CSS over HTTP, the browser will block these “mixed content” resources and display a warning in the console. Cloudflare’s Automatic HTTPS Rewrites can help resolve this by converting http:// links to https:// on the fly.

Cloudflare-Specific Browser Trace Tools and Diagnostics

Beyond standard browser developer tools, Cloudflare provides its own set of diagnostic endpoints and encourages the use of third-party tools that leverage Cloudflare’s infrastructure to provide deeper insights into how your website is interacting with their network.

These tools are invaluable for confirming connectivity, cache status, and routing paths.

The `cdn-cgi/trace` Endpoint

This hidden endpoint, accessible on any Cloudflare-proxied domain, offers a quick and easy way to determine which Cloudflare data center your request is hitting and other vital connection details.

To use it, simply append /cdn-cgi/trace to your domain e.g., yourdomain.com/cdn-cgi/trace.

fl= Cloudflare Data Center: This field displays the specific Cloudflare data center you are connected to. For instance, LAX for Los Angeles, ORD for Chicago, LHR for London. This is crucial for verifying that users are being routed to the closest possible Cloudflare edge location, optimizing latency. A user in New York hitting an LAX data center might indicate a routing issue or a non-optimal connection path.
h= Host: The hostname you requested, confirming the domain Cloudflare is processing.
ip= Your IP Address: The IP address from which your request originated. This is useful for confirming your public IP.
ts= Timestamp: The Unix timestamp of the request.
visit_scheme= Protocol: Indicates whether the connection was http or https. This helps confirm SSL/TLS enforcement.
uag= User Agent: Your browser’s user agent string, providing details about your browser and operating system.
colo= Cloudflare Data Center Code: Same as fl, explicitly showing the IATA airport code for the Cloudflare data center.
http= HTTP Version: Shows the HTTP protocol version used for the connection e.g., http/2, http/3.
loc= Country Code: The country code inferred from your IP address.

This output is a fundamental diagnostic step, helping you confirm that your browser is indeed connecting through Cloudflare and which specific edge server is serving you.

Leveraging Third-Party Cloudflare Checkers

Several online tools allow you to verify if your domain is properly configured with Cloudflare and actively using its services.

These tools typically perform DNS lookups and HTTP header checks to confirm Cloudflare’s presence. Check if website uses cloudflare

DNS Checker dnschecker.org: This tool is excellent for verifying your domain’s DNS records from various global locations. You should see Cloudflare’s nameservers e.g., amy.ns.cloudflare.com, dave.ns.cloudflare.com and Cloudflare’s IP addresses for proxied A/AAAA records. If your A/AAAA records show your origin server’s IP, it means your domain is not being proxied by Cloudflare DNS-only mode.
Check for Cloudflare checkforcloudflare.com: This simple tool specifically tells you if a given domain is using Cloudflare, often by checking the server: cloudflare HTTP header and nameserver records.
Header Checker Tools: Websites like reqbin.com or web-sniffer.net allow you to send a request to your domain and inspect all returned HTTP headers, including the crucial cf-cache-status, cf-ray, and server: cloudflare headers.

These tools are crucial for confirming that your domain is correctly integrated with Cloudflare at the DNS level and that Cloudflare’s edge network is indeed serving your content, rather than your origin server directly.

This is often the first troubleshooting step when performance or security issues arise.

Simulating Browser Environments and User Scenarios

Effective browser testing with Cloudflare involves more than just checking headers.

It requires simulating diverse user environments and scenarios.

This ensures your website performs optimally and securely for all visitors, regardless of their browser, device, or geographical location.

Testing Across Different Browsers and Versions

Different browsers and even different versions of the same browser interpret web standards and execute JavaScript uniquely.

Cloudflare’s optimizations are designed to be broadly compatible, but testing is still crucial.

Major Browsers: Always test with the latest stable versions of Chrome, Firefox, Safari, and Edge. These cover the vast majority of internet users.
Legacy Browser Support: If your audience includes users on older systems e.g., enterprise environments with IE11, ensure critical functionality works. Cloudflare’s Universal SSL provides broad compatibility, but some modern features might not be supported.
Browser Extensions: Test with and without common browser extensions. Some extensions like ad blockers or privacy tools can interfere with site functionality or Cloudflare’s security features. Use incognito/private mode to get a clean baseline.

Mobile Device Emulation vs. Real Devices

Mobile traffic now often surpasses desktop.

Cloudflare offers mobile-specific optimizations, making thorough testing essential.

Developer Tools Device Emulation: Most modern browser developer tools e.g., Chrome DevTools’ “Device Mode” offer robust emulation for various mobile devices and screen sizes. This is excellent for checking responsiveness, touch interactions, and basic performance.
Real Mobile Devices: While emulation is useful, nothing beats testing on actual physical mobile devices smartphones, tablets. Factors like cellular network latency, CPU throttling, and specific device quirks cannot be perfectly replicated. Test across iOS and Android devices, using both Wi-Fi and cellular data. Cloudflare’s Mobile Redirect and Polish image optimization for mobile features are best validated on real devices.

Geographic Location Testing VPNs and Proxies

Cloudflare’s primary benefit is its global CDN. Cloudflare check my browser

To verify that users worldwide get optimal performance, simulate different geographic locations.

VPN Services: Use a reputable VPN Virtual Private Network to connect from different countries. After connecting, visit your site and check cdn-cgi/trace to confirm you’re hitting a Cloudflare data center colo value close to your simulated location. This verifies the efficacy of the CDN and Argo Smart Routing.
WebPageTest.org: This powerful online tool allows you to run performance tests from numerous global locations using real browsers. It provides detailed waterfall charts and metrics, showing how your site loads for users in various regions and confirming Cloudflare’s global distribution.

Simulating Attack Vectors Carefully

While not for the faint of heart, basic simulation of attack vectors in a controlled, ethical manner, and only against your own properties can help verify Cloudflare’s WAF and security features.

WAF Rule Testing: If you have specific WAF rules e.g., for SQL injection or XSS, try inputting benign, non-harmful strings that should trigger these rules into search fields or forms. Observe if Cloudflare blocks the request and presents a “Challenge” or “Blocked” page e.g., a “1020 Access Denied” error page.
Rate Limiting: If you’ve configured rate limiting, try sending a rapid succession of requests to a specific endpoint e.g., logging in repeatedly to see if Cloudflare starts blocking or challenging subsequent requests.
Bot Management: Attempt to access your site with a common bot user agent string e.g., using a tool like curl to spoof a Googlebot or Bingbot user agent if you have Cloudflare Bot Management enabled. Observe if the requests are challenged or blocked. Always conduct these tests ethically and only on your own systems, informing your team beforehand.

By systematically testing across these varied environments and scenarios, you gain a comprehensive understanding of how Cloudflare is optimizing and securing your website for all users.

Verifying Cloudflare Security Features in the Browser

Cloudflare’s security features are designed to protect your website from various threats, from DDoS attacks to sophisticated web exploits.

Verifying these features from the browser’s perspective ensures that your protection mechanisms are active and correctly configured, safeguarding your users and data.

Web Application Firewall WAF Rule Enforcement

The WAF is Cloudflare’s frontline defense against common web vulnerabilities.

When a WAF rule is triggered, Cloudflare intercepts the request before it reaches your server.

Simulating WAF Triggers: To test WAF rules, you can ethically and only on your own site attempt to input known malicious patterns into forms or URL parameters that your WAF is configured to block.
- SQL Injection: Try appending ' OR 1=1 -- to a search query or login field.
- Cross-Site Scripting XSS: Input <script>alert'XSS'.</script> into a comment field.
- Path Traversal: Attempt to access ../etc/passwd via a URL parameter.
Browser Response:
- Block Page: If the WAF rule is set to “Block,” the browser should display a Cloudflare block page e.g., “Error 1020: Access Denied” or a custom WAF block page you’ve configured.
- Challenge Page: If the rule is set to “Challenge” e.g., JavaScript Challenge, CAPTCHA, Managed Challenge, the browser will be presented with an interactive challenge. Successfully passing the challenge should then grant access.
Cloudflare Dashboard Logs: After attempting to trigger WAF rules, check your Cloudflare dashboard’s “Security” -> “Events” section. You should see logs detailing the blocked or challenged requests, including the rule ID that was triggered and the action taken. This confirms the WAF is actively working.

DDoS Protection and Challenge Pages

Cloudflare’s automated DDoS protection works by identifying and mitigating malicious traffic.

For the browser, this often manifests as a “Checking your browser…” page.

Under Attack Mode: If you enable “I’m Under Attack Mode” in your Cloudflare dashboard, every visitor will be presented with a 5-second JavaScript challenge page before gaining access to your site. This is a good way to test the challenge page experience.
Managed Challenges: Cloudflare’s automated system might issue a Managed Challenge similar to a CAPTCHA to suspicious visitors without explicit “Under Attack Mode” being on. You can sometimes trigger this by using a VPN from a high-risk IP or by sending a rapid succession of requests though direct DDoS simulation is complex and not recommended for testing.
Browser Experience: The browser should display the Cloudflare challenge page. Once the challenge is passed, the site should load normally. If it fails repeatedly, there might be a client-side JavaScript issue preventing the challenge from completing.

Bot Management and Super Bot Fight Mode

Cloudflare’s Bot Management part of higher-tier plans and Super Bot Fight Mode available on Pro/Business/Enterprise identify and manage automated traffic. Cloudflare content type

Testing with Known Bots: While not straightforward from a regular browser, you can simulate a known bot’s user agent using tools like curl or browser extensions that allow user agent spoofing.
- Set your user agent to a common bot, e.g., Googlebot or AhrefsBot.
- Access your site.
- Block: The bot might be completely blocked, resulting in a Cloudflare block page.
- Challenge: The bot might be presented with a challenge.
- Allow/Log: For good bots like search engine crawlers, they should be allowed access, and their activity logged in your Cloudflare dashboard under “Security” -> “Bots.”
Cloudflare Analytics: Check your Cloudflare dashboard’s “Analytics” -> “Security” section, specifically the “Bot Traffic” insights, to see how Cloudflare is categorizing and handling various automated requests.

SSL/TLS Encryption HTTPS Verification

As discussed in developer tools, ensuring HTTPS is active and correctly configured is fundamental.

Padlock Icon: The most immediate browser indicator of a secure connection is the padlock icon in the address bar. A broken padlock or “Not Secure” warning indicates an issue.
Mixed Content Warnings: If your site loads over HTTPS but still attempts to load some assets images, scripts, CSS over HTTP, the browser will display mixed content warnings often in the console and might block the insecure resources. Cloudflare’s Automatic HTTPS Rewrites feature can help resolve this by converting http:// links to https:// on the fly.
HSTS HTTP Strict Transport Security: If HSTS is enabled in Cloudflare or at your origin, your browser will remember to always connect to your site via HTTPS, even if you explicitly type http://. You can verify this by attempting to access your site via http:// and observing an immediate redirect to https:// without a server-side redirect being explicitly visible in the network waterfall.

By systematically testing these security features, you can ensure that Cloudflare is actively protecting your website and providing a secure browsing experience for your users, mitigating risks that could otherwise compromise your data and reputation.

Performance Auditing with Cloudflare

Cloudflare’s primary promise, beyond security, is enhanced website performance.

Auditing this performance from the browser’s perspective is critical to ensure that Cloudflare’s optimizations are effectively reducing load times and improving user experience.

Tools like Google Lighthouse, PageSpeed Insights, and WebPageTest.org are indispensable for this task.

Google Lighthouse and PageSpeed Insights

These Google tools provide comprehensive performance reports, identifying opportunities for improvement and validating the impact of Cloudflare’s optimizations.

Google Lighthouse Chrome DevTools: Built directly into Chrome’s developer tools under the “Lighthouse” tab, it runs a series of audits for performance, accessibility, SEO, best practices, and Progressive Web App PWA readiness.
- Key Metrics to Watch:
  - First Contentful Paint FCP: Measures when the first piece of content text, image appears on the screen. Cloudflare’s CDN helps reduce this by serving assets from the edge.
  - Largest Contentful Paint LCP: Measures when the largest content element is visible. Optimizing images Cloudflare Polish and ensuring fast delivery of critical resources impact LCP.
  - Cumulative Layout Shift CLS: Measures visual stability. While primarily a design/development issue, fast loading of fonts and images aided by Cloudflare can prevent layout shifts.
  - Time to Interactive TTI: Measures when the page becomes fully interactive. Deferring JavaScript Cloudflare Rocket Loader can sometimes affect this, so test carefully.
  - Speed Index: How quickly content is visually displayed during page load.
- Opportunities Section: Lighthouse suggests specific improvements. Look for recommendations like “Serve images in next-gen formats” Cloudflare Polish helps here, “Enable text compression” Cloudflare Brotli/Gzip, “Reduce server response times TTFB” Cloudflare CDN caching.
Google PageSpeed Insights PSI: A web-based version of Lighthouse, PSI provides performance scores for both mobile and desktop, running tests from Google’s servers. It’s excellent for objective, global performance checks and includes “Field Data” Real User Monitoring data from Chrome users if available, offering insights into actual user experiences.

WebPageTest.org for Granular Performance Analysis

WebPageTest is a highly powerful and configurable tool for detailed web performance analysis, offering insights beyond what Lighthouse provides.

Global Test Locations: Choose from numerous test locations worldwide, allowing you to see how your site loads from different geographical vantage points. This is crucial for verifying the effectiveness of Cloudflare’s global CDN. Test from a location far from your origin server but close to a Cloudflare data center to see significant speed improvements.
Real Browser Testing: WebPageTest uses real browsers Chrome, Firefox, Edge, Safari on actual machines, providing more accurate performance data than synthetic simulations.
Waterfall Charts: These detailed charts show the loading sequence of every single resource HTML, CSS, JS, images.
- DNS, Connect, SSL Time: Cloudflare significantly reduces these times by terminating SSL at the edge and serving content from cached resources. A low initial DNS and Connect time indicates efficient Cloudflare routing.
- TTFB Time to First Byte: A consistently low TTFB under 200ms for cached assets is a strong indicator of effective Cloudflare caching.
- Content Download Time: Faster download times for images and scripts are a direct result of Cloudflare’s image optimization and Brotli compression.
Filmstrip View: Provides a visual breakdown of your page loading progress, frame by frame, helping you pinpoint exactly when different elements appear.
Repeat View: Simulates a user revisiting your site. Cloudflare’s aggressive caching and browser caching directives should make the “Repeat View” significantly faster than the “First View.”

Monitoring Cache Hit Ratio

While not directly a browser tool, understanding your Cloudflare cache hit ratio is fundamental to performance auditing.

Cloudflare Analytics Dashboard: Navigate to your Cloudflare dashboard, then “Analytics” -> “Performance.” Here you’ll find metrics like “Total Requests,” “Cached Requests,” and “Cache Ratio.”
High Cache Ratio: A high cache ratio ideally 80% or higher for static content indicates that Cloudflare is successfully serving a large proportion of requests from its edge, significantly reducing load on your origin server and accelerating delivery to browsers. A low cache ratio might mean your caching rules need adjustment or that your site has too much dynamic content.

By regularly utilizing these tools and monitoring relevant metrics, you can ensure that Cloudflare is delivering on its promise of enhanced website performance and a superior browsing experience for your users.

Troubleshooting Common Cloudflare Browser Issues

Despite Cloudflare’s robust design, occasional browser-related issues can arise, often stemming from caching conflicts, SSL misconfigurations, or specific browser behaviors. Recaptcha c#

Knowing how to diagnose and resolve these common problems is crucial for maintaining a smooth user experience.

Mixed Content Warnings

Problem: Your site loads over HTTPS, but some resources images, scripts, CSS, fonts are still attempting to load over insecure HTTP. Browsers block these insecure resources, leading to broken images, missing styles, or non-functional JavaScript, and display “mixed content” warnings in the console and address bar.
Diagnosis:
- Check your browser’s address bar for a “Not Secure” warning or a broken padlock icon.
- Open developer tools F12 and go to the “Console” tab. Look for warnings like “Mixed Content: The page at ‘https://example.com‘ was loaded over HTTPS, but requested an insecure resource ‘http://example.com/image.jpg‘. This request has been blocked. this content must be served over HTTPS.”
Solution:
1. Automatic HTTPS Rewrites: In your Cloudflare dashboard, go to “SSL/TLS” -> “Edge Certificates” and enable “Automatic HTTPS Rewrites.” This feature automatically changes http:// links to https:// on your page when served through Cloudflare.
2. Hardcode HTTPS: Best practice is to update all internal links and asset URLs in your website’s code HTML, CSS, JavaScript to use https:// or protocol-relative URLs e.g., //example.com/asset.jpg.
3. Check Third-Party Resources: Ensure any third-party scripts, widgets, or iframes you use are also loaded over HTTPS.

Incorrectly Cached Content

Problem: Users are seeing old content e.g., outdated blog posts, old product prices, stale CSS even after you’ve updated your website. This means Cloudflare is serving old cached versions.
- Use your browser’s developer tools Network tab and check the cf-cache-status header. If it shows HIT but the content is old, it’s a caching issue.
- Perform a hard refresh Ctrl+Shift+R or Cmd+Shift+R to see if the new content appears.
1. Purge Cache: In your Cloudflare dashboard, go to “Caching” -> “Configuration.”
  - Purge Everything: For a full site update, “Purge Everything” will clear the entire cache for your domain. Use this cautiously as it will temporarily increase load on your origin server.
  - Custom Purge: For specific URLs e.g., a single blog post, use “Custom Purge” and enter the exact URLs.
2. Adjust Cache TTL: Go to “Caching” -> “Page Rules.” If you have aggressive caching rules e.g., “Cache Everything” with a very long TTL, adjust them to a more suitable duration or use a “Bypass Cache” rule for dynamic sections.
3. Verify Origin Headers: Ensure your origin server is sending correct Cache-Control headers. Cloudflare respects these headers by default. For instance, Cache-Control: no-cache will tell Cloudflare and browsers to always revalidate with the origin.

SSL Certificate Issues e.g., NET::ERR_CERT_COMMON_NAME_INVALID

Problem: Browsers display security warnings indicating an invalid or untrusted SSL certificate. This prevents users from accessing your site securely.
- Check the certificate details in your browser’s “Security” tab. Look at “Issued To” should match your domain and “Issued By” should be Cloudflare or your certificate provider.
- Ensure the certificate is within its valid date range.
1. SSL/TLS Encryption Mode: In your Cloudflare dashboard, go to “SSL/TLS” -> “Overview.”
  - Flexible: Encrypts traffic between browser and Cloudflare unencrypted between Cloudflare and origin. This mode is prone to issues if your origin serves content over HTTPS and can cause redirect loops.
  - Full: Encrypts traffic end-to-end, but your origin server uses a self-signed or invalid certificate.
  - Full Strict: Recommended. Encrypts traffic end-to-end, and your origin server must have a valid, trusted SSL certificate either from a CA or a Cloudflare Origin CA certificate.
2. Origin Certificate: If using “Full Strict”, ensure a valid SSL certificate is installed on your origin server and it’s trusted by a Certificate Authority CA, or use a Cloudflare Origin CA certificate.
3. DNS Orange Cloud: Ensure your domain’s DNS records are correctly proxied through Cloudflare orange cloud icon. If they are grey, Cloudflare’s SSL cannot work.
4. HSTS Preload: If you’ve enabled HSTS Preload, ensure your certificate is correctly configured everywhere, as HSTS forces all connections to HTTPS, making any SSL issue immediately visible and blocking.

By systematically addressing these common browser-related issues with Cloudflare, you can ensure a seamless and secure browsing experience for your users.

Integration with Performance Monitoring Tools

Integrating Cloudflare with external performance monitoring tools is essential for a holistic view of your website’s health, speed, and user experience.

These tools provide real-time data, historical trends, and alerts, helping you quantify Cloudflare’s impact and identify areas for further optimization.

Real User Monitoring RUM and Cloudflare Analytics

RUM tools collect performance data directly from real users’ browsers, providing invaluable insights into actual user experiences.

Cloudflare itself offers robust analytics that can be complemented by dedicated RUM solutions.

Cloudflare Web Analytics: This free, privacy-first analytics solution under “Analytics” -> “Web Analytics” in your dashboard provides basic page view, visitor, and performance metrics FCP, LCP, CLS without using client-side JavaScript or cookies. It measures performance from the browser’s perspective after Cloudflare has processed the request.
Cloudflare Speed Analytics: Under “Analytics” -> “Speed” in your Cloudflare dashboard, you’ll find RUM-like data for Core Web Vitals LCP, FID, CLS, TTFB, and other performance metrics, broken down by country, browser, and device. This helps you see Cloudflare’s impact on real-world performance.
Dedicated RUM Tools e.g., New Relic, Datadog, Grafana with Prometheus/Loki: For deeper insights, integrate your site with third-party RUM providers. These tools typically involve embedding a small JavaScript snippet on your site.
- They capture metrics like page load time, resource loading, JavaScript errors, and user interactions.
- By correlating RUM data with Cloudflare logs if integrated, you can attribute performance improvements or regressions to Cloudflare’s caching, optimization, or security features. For example, a significant drop in LCP after enabling Cloudflare Polish would indicate its effectiveness.
- Many RUM tools allow custom attributes, enabling you to pass Cloudflare headers like cf-ray, cf-cache-status to your RUM system for advanced debugging and analysis.

Synthetic Monitoring for Baseline Performance

Synthetic monitoring tools simulate user interactions from various global locations at regular intervals, providing consistent, controlled performance data.

This is crucial for establishing baselines and detecting performance regressions.

Tools e.g., Pingdom, GTmetrix, Catchpoint, Lighthouse CI: These services periodically visit your website, measure performance metrics load time, TTFB, requests, and often provide waterfall charts similar to WebPageTest.
Benefits with Cloudflare:
- Baseline Establishment: Set up monitors before and after integrating Cloudflare to quantify the performance improvements e.g., lower TTFB, faster FCP.
- Uptime Monitoring: Most synthetic tools offer uptime monitoring, alerting you if your site or Cloudflare’s edge becomes unavailable.
- Regression Detection: Identify performance degradation over time, which might indicate issues with caching, new content, or changes in Cloudflare’s configuration.
- Geographical Performance: Use synthetic monitors from different regions to confirm Cloudflare’s global CDN is delivering consistent performance worldwide.
Best Practices:
- Monitor key pages homepage, product pages, critical user flows.
- Run tests frequently e.g., every 5-15 minutes.
- Configure alerts for performance thresholds e.g., if load time exceeds 3 seconds.

Log Integration and Analytics Platforms

Combining Cloudflare’s extensive logs with your existing analytics and logging platforms provides a comprehensive view of your website’s traffic, security events, and performance.

Cloudflare Logpush: For Enterprise customers and via Workers for others, Cloudflare Logpush allows you to push raw HTTP request logs containing cf-ray, cf-cache-status, IP, user agent, etc. to various destinations like S3, Splunk, Sumo Logic, or directly to custom endpoints.
Benefits of Log Integration:
- Deep Dive Troubleshooting: Correlate browser-side performance issues or errors from RUM with specific Cloudflare edge requests from Logpush to pinpoint root causes.
- Security Auditing: Analyze WAF events, DDoS attacks, and bot activity in detail.
- Performance Analysis: Understand cache hit ratios, origin load, and latency from Cloudflare’s perspective, complementing browser-side metrics.
- Business Intelligence: Gain insights into traffic patterns, user locations, and popular content.
Common Integrations:
- Security Information and Event Management SIEM Systems: For advanced threat detection and compliance.
- Data Warehouses/Lakes: For long-term storage and complex analytical queries.
- Custom Dashboards: Build dashboards using tools like Grafana, leveraging Cloudflare logs for real-time operational visibility.

By embracing these monitoring strategies, you move beyond anecdotal evidence and gain a data-driven understanding of how Cloudflare is impacting your website’s performance and security for real users. Cloudflare terms

Advanced Cloudflare Browser Configurations

Beyond the default settings, Cloudflare offers advanced configurations that can further enhance browser interaction, optimize content delivery, and provide a more resilient user experience.

These often involve fine-tuning caching rules, leveraging Workers, and implementing client-side performance features.

Fine-Tuning Caching with Page Rules and Cache API

While Cloudflare’s default caching is effective, custom Page Rules and the Cache API via Workers allow for granular control over what gets cached and for how long.

Page Rules: These powerful rules available in your Cloudflare dashboard under “Rules” -> “Page Rules” allow you to specify actions for specific URLs or URL patterns.
- Cache Everything: Force Cloudflare to cache HTML pages, not just static assets, for a specified duration. This is excellent for static sites or infrequently updated pages, significantly reducing origin load.
- Bypass Cache: Exclude dynamic pages e.g., shopping carts, login areas from caching to ensure personalized content.
- Edge Cache TTL: Override the origin’s Cache-Control headers for certain paths, allowing you to set a custom caching duration at Cloudflare’s edge.
- Always Use HTTPS: Force redirects from HTTP to HTTPS for specific paths.
- Browser Cache TTL: Control how long browsers should cache assets, reducing repeat requests from the same user. This complements Cloudflare’s edge caching.
Cloudflare Cache API Workers: For ultimate control, Cloudflare Workers can interact directly with Cloudflare’s global cache.
- Custom Caching Logic: Cache responses dynamically based on request headers, cookies, or even A/B test variations.
- Pre-fetching/Pre-loading: Use Workers to proactively fetch content and populate the cache before a user explicitly requests it, dramatically speeding up subsequent loads.
- Smart Caching: Cache fragmented content or API responses that might not be easily cached by traditional means.
- Stale-While-Revalidate: Serve stale content from the cache immediately while asynchronously revalidating with the origin, providing a faster initial load for users.

Leveraging Cloudflare Workers for Client-Side Optimizations

Cloudflare Workers are serverless functions that run directly on Cloudflare’s edge network, allowing you to intercept and modify HTTP requests and responses before they reach your origin or the user’s browser.

This opens up vast possibilities for advanced client-side performance and security.

Dynamic A/B Testing: Randomly serve different versions of content HTML, CSS, JS to users based on custom logic, without modifying your origin server, and observe browser performance for each variation.
Edge-Side Includes ESI: Dynamically stitch together personalized content from different sources at the edge, reducing the need for your origin server to do complex rendering for every request.
Advanced Image/Asset Transformation: Beyond Cloudflare Polish, Workers can perform more complex image manipulations, generate responsive image srcset attributes on the fly, or even serve different assets based on browser capabilities.
User Agent-Based Routing/Optimization: Direct requests to different origins or apply specific optimizations based on the user’s device or browser e.g., serving optimized mobile content to smartphone users.
SPA Single Page Application Routing: Handle client-side routing for SPAs at the edge, ensuring correct assets are served for deep links without hitting the origin for every route change.
Client-Side Feature Flagging: Control the visibility of features to different user segments directly at the edge, allowing for phased rollouts without redeploying your application.

Implementing Browser-Specific Features and Security Headers

Cloudflare can help you deploy advanced browser features and security headers that enhance performance and protect users.

HTTP/3 QUIC: Cloudflare was an early adopter of HTTP/3, which uses the QUIC protocol for faster, more reliable connections, especially on mobile networks. Browsers supporting HTTP/3 like Chrome, Edge, and some Firefox versions will automatically benefit when connecting to Cloudflare.
Early Hints: This feature, available on Cloudflare, allows the server to send hints to the browser about critical resources like CSS, JS, fonts even before the main HTML response is fully generated. This enables the browser to start downloading these resources sooner, improving perceived load times.
Content Security Policy CSP: While primarily configured at the origin, Cloudflare can assist in deploying and monitoring CSP headers, which allow you to specify which sources of content scripts, stylesheets, images a browser is allowed to load. This helps prevent XSS and data injection attacks.
X-XSS-Protection and X-Content-Type-Options: Cloudflare automatically adds or enforces these headers to protect against XSS attacks and MIME-type sniffing, enhancing browser security.
Referrer-Policy: Control how much referrer information is sent to other sites, enhancing user privacy. Cloudflare can help configure this header.

By strategically implementing these advanced Cloudflare configurations, you can fine-tune your website’s interaction with browsers, delivering a highly optimized, secure, and resilient experience to your users, irrespective of their browsing environment.

The Islamic Perspective on Technology and Digital Ethics

From an Islamic standpoint, technology, including tools like Cloudflare that enhance digital connectivity and security, is generally viewed positively when used for beneficial purposes.

The core principles guiding Muslim engagement with technology revolve around promoting good ma'ruf, preventing harm munkar, and fostering societal well-being.

This perspective encourages the use of tools that facilitate knowledge sharing, ethical commerce, communication, and robust digital infrastructure, while cautioning against their misuse for purposes that contravene Islamic values. Get recaptcha v3 key

Promoting Halal Permissible and Discouraging Haram Forbidden Content

The internet is a vast space, and Cloudflare, as a neutral infrastructure provider, can unfortunately be used to host or accelerate content that is not permissible in Islam.

As responsible digital citizens and website owners, Muslims are encouraged to leverage technology, including Cloudflare’s capabilities, to promote content that aligns with Islamic ethics and to actively discourage or avoid content that is forbidden.

Halal Content: This includes promoting:
- Knowledge and Education: Websites disseminating Islamic knowledge, scientific research, educational courses, and beneficial information.
- Ethical Commerce: Online businesses engaged in fair trade, offering halal products and services, and avoiding riba interest, gambling, or deceptive practices. Cloudflare can secure e-commerce platforms and ensure fast delivery of product information to customers.
- Community Building: Platforms for positive social interaction, family-friendly content, and charitable initiatives.
- Dawah Calling to Islam: Websites and blogs sharing the message of Islam in a respectful and engaging manner.
- Digital Preservation: Archiving and making accessible valuable Islamic texts, historical documents, and cultural heritage. Cloudflare’s caching and security can ensure these resources are reliably available.
Discouraging Haram Content: While Cloudflare itself doesn’t filter content unless configured by the customer, e.g., via DNS filtering services like Cloudflare Gateway, a Muslim leveraging Cloudflare for their own online presence should ensure their hosted content avoids:
- Gambling and Riba Interest: Financial products or activities based on interest, betting, or speculative gambling.
- Immoral or Indecent Content: Pornography, explicit content, or material that promotes promiscuity, premarital relations, or other immoral behaviors.
- Alcohol, Narcotics, and Non-Halal Food: Promotion or sale of prohibited substances or food items.
- Polytheism, Idolatry, Blasphemy: Content that promotes beliefs contrary to pure monotheism Tawhid or disrespects religious figures.
- Gossip, Backbiting, Slander: Content that spreads misinformation, harms reputations, or fosters division.
- Harmful Entertainment: Podcast, movies, or entertainment that is vulgar, promotes violence, or distracts from righteous living, especially if it contains elements explicitly forbidden in Islam.

Alternatives and Responsible Use

When faced with online content that is not permissible, the Islamic approach emphasizes seeking alternatives and promoting responsible digital citizenship.

Seek Halal Alternatives: Instead of engaging with forbidden entertainment or content, seek out beneficial alternatives. This could include:
- Beneficial Learning: Reading the Quran, studying Islamic texts, attending online lectures, or learning new skills.
- Constructive Entertainment: Engaging with wholesome stories, educational documentaries, or nasheeds vocal podcast without instruments, though podcastal instruments themselves are a debated topic among scholars, with a strong view against them.
- Physical Activity: Engaging in sports or outdoor activities.
- Family Time: Spending quality time with family.
Responsible Digital Stewardship:
- Content Moderation: Website owners should actively moderate user-generated content to ensure it complies with ethical and Islamic standards.
- Ethical Advertising: Avoid hosting or displaying ads that promote haram products or services.
- Privacy and Data Security: Cloudflare’s security features can protect user data, which aligns with the Islamic emphasis on safeguarding trusts amanah and respecting privacy.
- Combating Misinformation: Use technology to promote truth and clarity, countering false narratives and misinformation.
- Accessibility: Design websites to be accessible to all, including those with disabilities, reflecting the Islamic value of inclusion.

In essence, a Muslim’s engagement with technology like Cloudflare should be guided by the overarching principle of seeking Allah’s pleasure by using these powerful tools to facilitate good and avoid harm.

Cloudflare, by providing robust infrastructure for the internet, enables the global dissemination of information.

The responsibility lies with the user to ensure that information is beneficial and aligns with the higher purposes of Islam.

Frequently Asked Questions

What is Cloudflare test browser?

Cloudflare test browser refers to the process of using various browser features and external tools to verify that Cloudflare’s services like caching, security, and optimization are correctly functioning and impacting the end-user’s browser experience as expected.

It involves checking HTTP headers, SSL status, and content delivery from a browser’s perspective.

How do I check if Cloudflare is working on my website?

Yes, you can check if Cloudflare is working.

The easiest way is to use a tool like dnschecker.org to see if your domain’s nameservers point to Cloudflare, or checkforcloudflare.com. Additionally, open your browser’s developer tools F12, go to the “Network” tab, and look for the server: cloudflare HTTP response header and cf-ray header on your website’s requests. Get recaptcha v2 key

What is `cf-cache-status` and what does it mean?

cf-cache-status is an HTTP response header added by Cloudflare that indicates whether a requested resource was served from Cloudflare’s cache.

HIT: The resource was served directly from Cloudflare’s edge cache.
MISS: The resource was not in Cloudflare’s cache and was fetched from your origin server.
DYNAMIC: The resource is not cached by Cloudflare and is always fetched from your origin.
EXPIRED: The cached content expired and was revalidated with the origin.

How can I force Cloudflare to update cached content in my browser?

To force Cloudflare to update cached content and see the latest version in your browser, you should first purge the cache for the specific URLs or your entire site in your Cloudflare dashboard “Caching” -> “Configuration” -> “Purge Cache”. After purging, perform a hard refresh in your browser Ctrl+Shift+R on Windows/Linux or Cmd+Shift+R on Mac to bypass your local browser cache.

Why am I seeing a “Checking your browser…” page from Cloudflare?

You are seeing a “Checking your browser…” page because Cloudflare’s automated DDoS protection system or security settings have triggered a JavaScript challenge.

This typically happens when Cloudflare detects suspicious activity, a potential DDoS attack, or if the “I’m Under Attack Mode” is enabled in your dashboard.

It verifies that the visitor is a legitimate human and not a bot.

How do I check my Cloudflare data center location `colo`?

You can check which Cloudflare data center colo you are connected to by navigating to yourdomain.com/cdn-cgi/trace in your browser.

The output will include a colo= field, which is a three-letter IATA airport code indicating the Cloudflare data center location e.g., LAX for Los Angeles, LHR for London.

What is the “Security” tab in browser developer tools used for with Cloudflare?

The “Security” tab in browser developer tools F12 is used to verify the SSL/TLS connection status of your website.

With Cloudflare, you can confirm that the connection is secure HTTPS, inspect the SSL certificate details ensuring it’s issued by Cloudflare or your certificate provider, and check the TLS protocol version being used.

How can I test Cloudflare’s Web Application Firewall WAF?

To test Cloudflare’s WAF ethically and only on your own site, you can try inputting benign, non-harmful strings that mimic common attack patterns e.g., SQL injection or XSS patterns into search bars or forms on your site. Cloudflare english

If your WAF rules are correctly configured to “Block” or “Challenge,” your browser should display a Cloudflare block page or a challenge page.

Always check your Cloudflare dashboard’s “Security” -> “Events” logs to confirm the WAF actions.

What are “mixed content” warnings and how does Cloudflare help?

Mixed content warnings occur when a website loaded over HTTPS secure attempts to load some resources images, scripts, CSS over HTTP insecure. Browsers block these insecure resources, leading to broken page elements.

Cloudflare helps with “Automatic HTTPS Rewrites” found under “SSL/TLS” -> “Edge Certificates”, which automatically converts http:// links to https:// on your page when served through Cloudflare.

Can Cloudflare improve my Google Lighthouse score?

Yes, Cloudflare can significantly improve your Google Lighthouse and PageSpeed Insights scores.

Features like CDN caching faster FCP/LCP, image optimization Polish, Brotli compression, minification Auto Minify, and early hints directly contribute to better performance metrics by reducing load times and optimizing asset delivery.

How do I test my website’s performance from different global locations with Cloudflare?

You can test your website’s performance from different global locations with Cloudflare by using online tools like WebPageTest.org. This tool allows you to select various test locations worldwide, run tests using real browsers, and provides detailed waterfall charts and metrics, confirming Cloudflare’s global CDN effectiveness and routing.

What is Cloudflare’s `server: cloudflare` header?

The server: cloudflare HTTP response header is a clear indicator that the response you are receiving in your browser is being served directly by a Cloudflare edge server.

This confirms that your domain is successfully proxied through Cloudflare.

What is Cloudflare’s “Orange Cloud” in DNS settings?

The “Orange Cloud” icon next to a DNS record in your Cloudflare dashboard indicates that traffic for that record is being proxied through Cloudflare’s network. Recaptcha test key

This means Cloudflare is providing its performance, security, and caching services.

A “Grey Cloud” means the record is DNS-only, and traffic bypasses Cloudflare, going directly to your origin server.

Why is my website showing a “Not Secure” warning despite using Cloudflare SSL?

Your website might show a “Not Secure” warning despite using Cloudflare SSL due to mixed content issues loading HTTP resources on an HTTPS page, incorrect SSL/TLS encryption mode settings in Cloudflare e.g., “Flexible” mode when your origin also uses SSL, or an issue with your origin server’s SSL certificate if you’re using “Full” or “Full Strict” SSL.

How do I clear my browser’s cache for Cloudflare-related testing?

To clear your browser’s cache for Cloudflare-related testing, you should use the “Hard Refresh” or “Empty Cache and Hard Reload” options in your browser’s developer tools often found by right-clicking the refresh button when developer tools are open. This ensures your browser requests fresh content from Cloudflare’s edge rather than serving from its local cache.

What is `cf-ray` and why is it important for debugging?

cf-ray is a unique identifier generated by Cloudflare for every request processed through their network.

It’s crucial for debugging because if you encounter an issue, providing the cf-ray ID to Cloudflare support allows them to precisely locate and analyze the specific request in their logs, significantly speeding up troubleshooting.

Can Cloudflare Workers impact browser behavior?

Yes, Cloudflare Workers can significantly impact browser behavior.

Workers run on Cloudflare’s edge network and can modify HTTP requests and responses, allowing for custom caching logic, A/B testing, edge-side content transformations, advanced routing based on user agents, and even completely custom API responses, all before content reaches the user’s browser or your origin server.

What is HTTP/3 QUIC and how does Cloudflare leverage it for browsers?

HTTP/3 is the latest version of the Hypertext Transfer Protocol, which uses the QUIC Quick UDP Internet Connections transport protocol instead of TCP.

Cloudflare was an early adopter of HTTP/3, and when enabled, it allows supporting browsers like Chrome and Edge to establish faster, more reliable, and more secure connections to Cloudflare’s edge, particularly beneficial for mobile users due to reduced head-of-line blocking and faster handshakes. Recaptcha v3 code

How can I verify Cloudflare’s image optimization Polish in my browser?

To verify Cloudflare’s image optimization Polish in your browser, check the “Network” tab in developer tools.

Look for image requests and examine their file size and Content-Type header.

If Polish is enabled, you might see images converted to WebP or AVIF formats for compatible browsers, resulting in smaller file sizes compared to the original, and potentially a cf-bgj header indicating background image processing.

Why is my browser still showing old content even after purging Cloudflare cache?

If your browser is still showing old content after purging Cloudflare’s cache, it’s highly likely your browser’s own local cache is still serving the old version. To fix this, perform a hard refresh Ctrl+Shift+R or Cmd+Shift+R or clear your browser’s entire cache for your site. Ensure no aggressive browser caching rules are set via Page Rules that might override your origin’s Cache-Control headers for that specific resource.

Cloudflare test browser