Cloudflare can participate in a website’s delivery path while the origin, content system and applications live elsewhere. Plan those boundaries clearly before changing caching, routing or security behavior.
The 20 examples below returned successful responses with Cloudflare’s cf-ray header on the exact public routes pictured. This is evidence of Cloudflare participation in the observed delivery path. It does not prove use of Workers, Pages, a particular WAF plan or a specific origin host.
The visual examples are useful for understanding the content that a delivery layer must preserve: campaign pages, news, public information, product catalogs and design resources. The implementation brief should connect each content type to its freshness, privacy and failure requirements instead of applying one broad rule to the entire domain.
Before the examples
What makes good Cloudflare website development in 2026?
Start with an inventory of responses
List public documents, versioned assets, search results, APIs and personalized pages. Record what may be shared across visitors and what must remain private. The visitor’s task should determine those boundaries; the presence of a CDN is not a reason to cache everything.
Separate delivery evidence from product claims
Cloudflare documents cf-ray as a header associated with requests through its network. It is useful for observing a delivery path, but it does not identify every enabled product or certify the site’s security. Keep architecture claims tied to their actual supporting evidence.
Define how quickly a correction, expired offer or emergency notice must become visible. Cloudflare’s default cache behavior does not cache HTML or JSON merely because a request passes through its network. Review the actual rules and origin headers before making assumptions about what visitors receive.
Compare the public content and navigation needs in each example. The edge evidence is separately recorded; a screenshot cannot reveal the origin, cache policy or protection settings behind the page.
We start with five recognizable brands or organizations: UNICEF, Shopify, Dropbox Brand Guidelines, Mattel Creations storefront, AXA UK. Each attribution applies to the named website property, not every product or website belonging to its organization. This is a curated reading sequence, not a measured ranking.
UNICEF's saved homepage places a large vaccination photograph beneath a familiar blue institutional header. Topic, research, story and action routes remain available above the campaign, allowing the page to serve readers who want either immediate news or broader organizational information. The composition is useful for a public-interest site that must publish current material without losing its permanent structure. A successful response from the pictured route included Cloudflare's cf-ray header. That indicates Cloudflare participation in this request's delivery path; it does not establish the site's origin host, CMS, security configuration or the infrastructure behind donations.
What you can learn
Keep campaign publishing separate from critical institutional routes. Test navigation and media fallbacks in a safe preview, and define how urgent corrections propagate through caches so the public page does not retain outdated campaign information after an approved change.
Pros
The stable institutional header makes changing campaign imagery recognizable as part of the same organization.
Research and action routes remain available for visitors whose task differs from the featured story.
Cons & considerations
Large photography requires careful captioning, consent and contextual treatment for vulnerable subjects.
A campaign-led opening still needs clear dates and accessible routes to detailed supporting information.
PHPCMS dependency association; runtime not independently observed
Earlier cited evidence retained; no current scan result. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.unicef.org/ returned status 200 at https://www.unicef.org/ with cf-ray: a54c4d279c302719-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Shopify's captured homepage uses a dark merchant-focused scene with a large aspirational headline and a clear starting action. Product, pricing and enterprise routes remain in a compact header, while the human subject supplies a concrete setting for a broad platform proposition. This is useful for studying how technical infrastructure can be introduced through a recognizable business activity. Cloudflare's cf-ray header was observed on this marketing route. The observation does not establish the hosting or protection of every Shopify merchant, checkout or administrative interface. Those are separate properties and services with their own configurations.
What you can learn
Keep the public platform narrative distinct from merchant operations. When planning edge behavior, identify which marketing responses are public and cacheable, and treat account entry, application state and commerce actions according to their actual data and authentication requirements.
Pros
The merchant scene gives the broad proposition a human context without a dense technical diagram.
Pricing and product routes remain visible for visitors who need practical evaluation details.
Cons & considerations
Aspirational copy needs concrete explanations nearby so newcomers can understand the actual offer.
A successful public-page response cannot demonstrate checkout behavior, application availability or account security.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.shopify.com/ returned status 200 at https://www.shopify.com/ with cf-ray: a54c4d99582cccc8-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Dropbox's brand portal turns its categories into a grid of labeled tiles. Framework, voice, logo, typography, color, imagery and motion appear as distinct areas, each using a visual treatment related to its subject. This makes the portal itself an example of the system it explains. The observed cf-ray response confirms Cloudflare's role in the delivery path for brand.dropbox.com, the specific property shown. It should not be treated as evidence about Dropbox file storage or customer account infrastructure. The development value lies in predictable public asset discovery and clearly maintained brand guidance.
What you can learn
Give each guideline area a stable address and identify who approves changes to downloadable assets. Preview revised tiles and labels together, and plan cache invalidation so outdated logos or instructions do not persist after a brand-system release.
Pros
The labeled tile grid makes the major content areas visible without opening a complex menu.
Each tile demonstrates part of the visual language while remaining a practical navigation target.
Cons & considerations
Colorful categories still need readable labels and keyboard focus that do not depend on color alone.
Public brand assets need version and usage context so old downloads are not mistaken for current guidance.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://brand.dropbox.com/ returned status 200 at https://brand.dropbox.com/ with cf-ray: a54c4d18a8bd72c8-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Mattel Creations opens with a featured collectible in a wide campaign scene, followed by a row of colorful product categories. Brand marks sit between the main header and the hero, giving fans several ways into a large assortment. The page is useful for understanding how a launch moment can coexist with ordinary browsing. A successful response from the storefront carried Cloudflare's cf-ray header. This identifies an edge-delivery signal for the observed route, not a guarantee about traffic handling, release fairness, inventory accuracy or the protection of checkout and customer accounts.
What you can learn
Treat launch pages and transaction paths as separate operational concerns. Rehearse campaign publication, expiration and links to unavailable products, and test appropriate cache boundaries and failure messages without using a real purchase to validate the design.
Pros
The featured collectible receives enough space to explain its visual appeal and collaboration context.
The category row provides a practical alternative for visitors uninterested in the launch.
Cons & considerations
Limited-release messaging can create confusion if availability and campaign copy are updated at different times.
A crowded brand strip needs a clear mobile treatment so fans can still find the relevant collection.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://creations.mattel.com/ returned status 200 at https://creations.mattel.com/ with cf-ray: a54c4d11bbf5fc10-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
AXA UK's saved homepage places a broad human-centered campaign beneath a detailed product navigation bar. Insurance categories begin below the hero, giving the visitor a route from brand story into a more specific need. The page is useful for studying a service business where public information, quotes and existing-customer journeys coexist. Cloudflare's cf-ray header was observed on the public route. That supports only an edge-delivery association for this request. It does not verify insurance terms, account security, quote processing or the infrastructure behind claims, and the visual review should not be read as financial guidance.
What you can learn
Separate public product explanation from personalized quote and account routes. Preview current campaign copy alongside the actual product links, and document which responses must remain private or uncached before adding broad edge rules to an existing site.
Pros
The product navigation remains visible above the campaign for visitors with a specific need.
The next section starts translating the brand message into recognizable service categories.
Cons & considerations
Large brand campaigns can delay practical comparison details if they dominate the first screen.
Quote and existing-customer actions need precise labels so visitors understand which workflow they are entering.
Visible tech stack
Referenced on the public page
CloudflareDelivery / hosting signal
ASP.NETReported response header
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.axa.co.uk/ returned status 200 at https://www.axa.co.uk/ with cf-ray: a54c4d108e946e2c-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Travelers uses several photographs to support a short service proposition, then divides the opening into personal and business insurance routes. A compact quote area sits alongside the business panel, while claims and preparation links remain in the header. This is a useful pattern for a site serving different audiences without forcing them through a generic brand story. The observed cf-ray response identifies Cloudflare in this public page's delivery path. It does not establish how quote details are processed or certify any security control, policy coverage or service outcome beyond the limited response observation.
What you can learn
Map the audience split before applying shared caching or routing rules. Keep public explanatory content distinguishable from personalized quote responses, and review the labels, errors and return paths for each audience in an approved test environment.
Pros
The personal and business panels make the main audience distinction visible early.
Claims and prevention routes acknowledge existing customers as well as new prospects.
Cons & considerations
A compact quote area needs clear labels and error handling that remain usable on small screens.
Several audience routes can become confusing if the receiving pages do not preserve the visitor's selected context.
Visible tech stack
Referenced on the public page
CloudflareDelivery / hosting signal
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.travelers.com/ returned status 200 at https://www.travelers.com/ with cf-ray: a54c4d0e58d3b668-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Lemonade's saved homepage uses a sparse illustration, a centered proposition and a strongly colored pricing action. Product categories sit in a thin header, while a cookie-choice panel occupies the lower-left portion of the view. The scene shows how even a minimal design has to accommodate operational layers that are not part of the main campaign. Cloudflare's cf-ray header was observed on the public route. That is evidence of edge participation for the request, not proof of privacy compliance, quote accuracy or the processing architecture behind the insurance service.
What you can learn
Design consent and utility layers alongside the main page instead of adding them after approval. Check that they leave the primary content and keyboard path usable, and keep personalized pricing responses separate from public-page cache behavior.
Pros
The single prominent action makes the immediate next step easy to identify.
Light illustrations support the proposition without requiring a large photographic asset.
Cons & considerations
The visible consent panel competes with the otherwise spare layout and needs careful mobile placement.
A simple pricing invitation must still lead to clear conditions, disclosures and recoverable form states.
Visible tech stack
Earlier / documented evidence
Cloudflare
Earlier cited evidence retained; no current scan result. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.lemonade.com/ returned status 200 at https://www.lemonade.com/ with cf-ray: a54c4d0ebef1f596-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Allbirds combines a full-body lifestyle photograph with a close product view in a split campaign composition. A short action sits over the imagery, while the header and search remain compact. The pairing makes the shoe visible both as an object and as something used in a real setting. Cloudflare's cf-ray header appeared in a successful response from the pictured storefront route. This establishes edge participation for that response only. It does not identify the complete retail platform or prove performance, stock consistency or the behavior of cart and payment journeys outside the captured page.
What you can learn
Plan campaign assets around both context and product detail, then test their crops in preview. Define independent caching and update rules for promotional content, product facts and personalized commerce responses rather than treating the storefront as one uniform page type.
Pros
Two image scales help connect the product's appearance with its everyday use.
A restrained header leaves the campaign legible while retaining familiar shopping controls.
Cons & considerations
Overlay copy can lose contrast when the imagery changes between releases.
A lifestyle-led opening needs accessible product specifications and availability information beyond the visual campaign.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.allbirds.com/ returned status 200 at https://www.allbirds.com/ with cf-ray: a54c4d120b778e47-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
IDEO's saved homepage frames a large workshop photograph within a dark patterned field. A concise service statement begins below, while the menu and work action occupy small areas near the top. The visual gives an abstract consulting offer a tangible setting: people working around material rather than a generic illustration of innovation. The public route returned a cf-ray header, supporting Cloudflare participation in delivery. It does not show the agency's internal tools, client systems or exact security configuration. The useful reference is the connection between a service proposition and credible, contextualized visual evidence.
What you can learn
Treat project and workshop imagery as content with explicit context and permissions. Preview the surrounding copy, navigation and mobile crop together, and define how approved updates reach both the origin and any edge cache without leaving conflicting service descriptions.
Pros
The workshop scene gives the service proposition a recognizable human activity.
The focused navigation keeps the first screen visually calm despite the detailed photograph.
Cons & considerations
An abstract headline still needs specific examples of services and engagement types nearby.
A highly photographic opening can make work discovery slower if the archive route remains too understated.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.ideo.com/ returned status 200 at https://www.ideo.com/ with cf-ray: a54c4d19b82e4711-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
TEDAI Vienna uses a landscape and an oversized theme word to establish its event identity. Speaker, program and partner routes sit in a narrow header, with a dated participation action near the bottom of the hero. The design is useful for a site that needs a memorable visual campaign while still communicating a practical event. A cf-ray header was observed on this specific TEDAI property. That signal does not establish the infrastructure of every TED website or the services handling tickets, attendee data and livestreams. Event delivery requires those responsibilities to be identified separately.
What you can learn
Model the event edition explicitly. Preview dates, venue information and action destinations together, then define the transition from registration to live information to archive so cached pages do not continue inviting visitors to an expired event.
Pros
The visual theme gives the event a recognizable identity before the detailed program begins.
Program and speaker routes remain visible for visitors evaluating the substance of the conference.
Cons & considerations
Large thematic copy can obscure essential dates and location if those details are too quiet.
An event site needs deliberate archival and redirect behavior when the next edition replaces the current campaign.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://tedai-vienna.ted.com/ returned status 200 at https://tedai-vienna.ted.com/ with cf-ray: a54c4d196fedcba4-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Fivetran places a concise data-platform proposition beside a customer-oriented visual containing a laptop and small interface-style labels. A row of recognizable company marks begins underneath. The composition connects a technical offer with a real work setting while keeping the first action easy to find. Cloudflare's cf-ray header was observed on the pictured public route. This does not establish how Fivetran's connectors transfer customer data or where its service workloads run. The review concerns the marketing page and the planning distinction between a publicly cached explanation and the separate operational product.
What you can learn
Use customer examples to explain a concrete workflow, with scope and source attached. Review changes to technical terminology and product links in preview, and avoid letting edge configuration for the marketing site spill into authenticated or data-processing endpoints.
Pros
The adjacent visual gives a technical proposition a more tangible work context.
Customer proof begins close to the explanation rather than requiring a long scroll.
Cons & considerations
Small interface labels can become unreadable when the composition shrinks on mobile.
Company marks require contextual case studies so they are not mistaken for proof of every advertised capability.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.fivetran.com/ returned status 200 at https://www.fivetran.com/ with cf-ray: a54c4d1a8b0ecab0-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Vanta's saved opening uses a purple field, a proposition and an email-based demo action. A partial interface appears below, while customer marks form a separate row at the lower edge. The page makes the request for a conversation prominent but gives it some product context. Its successful response included Cloudflare's cf-ray header. That identifies edge participation for this public marketing route; it does not independently verify compliance claims, certify a customer's security posture or establish the infrastructure behind evidence collection. The page's reassuring visual language and its technical proof should be evaluated separately.
What you can learn
Keep public marketing content, demo submissions and the operational application clearly separated. Preview the form with accessible labels and error states, then document the destination, retention and failure handling of submitted details in the approved test workflow.
Pros
The centered hierarchy makes the intended next step apparent without several competing actions.
The interface preview gives the proposition a visible product reference near the top of the page.
Cons & considerations
A compact email field can hide important consent and validation needs if designed only for appearance.
Trust-related claims need precise definitions and supporting material beyond customer logos and a confident headline.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.vanta.com/ returned status 200 at https://www.vanta.com/ with cf-ray: a54c4d1a78810d77-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
NCR Voyix uses a purple split composition with a concise platform statement and two human-centered retail scenes. The header includes solution, platform, industry, service and resource routes, giving visitors several ways to narrow the broad corporate offer. This is useful for a company whose technologies serve different business contexts. Cloudflare's cf-ray header was observed on the public corporate route. It does not establish the architecture of point-of-sale systems, customer deployments or payment processing. The website's edge delivery and the systems it markets should remain distinct subjects in any technical brief.
What you can learn
Map industry journeys to specific solution pages before building the hero. Preview the wording and destinations with representatives from each offering, and keep edge routing changes scoped to the public website rather than assuming a single rule fits every service.
Pros
Human scenes make a broad technology proposition easier to connect with real business settings.
Several evaluation routes are available without forcing every visitor through the same sales narrative.
Cons & considerations
A dense enterprise navigation needs careful naming to avoid overlap between solutions, products and industries.
Broad platform language should lead to concrete descriptions of the systems and responsibilities involved.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.ncrvoyix.com/ returned status 200 at https://www.ncrvoyix.com/ with cf-ray: a54c4d1b5afb1950-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Greenhouse pairs a large hiring proposition with an abstract fingerprint-and-leaf illustration. The dark green hero is followed by a lighter section with separate employer and job-seeker choices. The composition is useful because it begins to separate audiences before a visitor reaches deeper product content. A successful response from the marketing route included Cloudflare's cf-ray header. That supports edge participation for this page, not claims about applicant-data security, hiring outcomes or the operation of recruitment workflows. The development lesson concerns clear routing and the boundary between public content and more sensitive application experiences.
What you can learn
Make audience labels persist through the next page and any external handoff. Preview the employer and job-seeker paths separately, and ensure that public cache rules cannot be applied indiscriminately to personalized candidate or recruiting information.
Pros
The audience choices acknowledge that not every visitor is a prospective software buyer.
The limited visual palette gives the headline and next section a coherent relationship.
Cons & considerations
Abstract illustration cannot replace a clear explanation of the product's actual workflow.
Closely related hiring journeys need careful labels so candidates do not enter a sales-oriented path by mistake.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.greenhouse.com/ returned status 200 at https://www.greenhouse.com/ with cf-ray: a54c4d1b2bee9a6b-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
London City Hall opens with a direct institutional statement, followed by a large city photograph and a prominent event notice. Search and menu controls sit in a dark header alongside the Mayor and Assembly identities. The page illustrates the challenge of combining permanent civic information with seasonal announcements. Cloudflare's cf-ray header was observed on the public route, establishing a limited delivery signal. It does not verify the security, accessibility or availability of government services linked elsewhere. Public information, event ticketing and citizen-service applications may have different owners and operational requirements.
What you can learn
Give notices explicit start and end dates and retain a dependable route to permanent information. Preview the page with the notice visible and dismissed, then test update propagation so corrections are not stranded behind a stale cached version.
Pros
The institutional introduction identifies the public body before the visitor encounters a campaign.
Search provides a direct alternative for residents arriving with a specific information need.
Cons & considerations
A large notice can consume substantial mobile space and needs accessible dismissal behavior.
Event and civic-service links require clear destinations so temporary campaigns do not obscure essential public tasks.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.london.gov.uk/ returned status 200 at https://www.london.gov.uk/ with cf-ray: a54c4d2a0b6d5cfd-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Médecins Sans Frontières gives an urgent field report a large photographic hero, with a substantial headline and a contrasting reading action. A stable white header retains organizational, country, news and support routes. The design demonstrates how an institution can foreground a current issue without making the entire website a single campaign. The observed cf-ray header supports Cloudflare participation in delivery of this public route. It does not prove the origin architecture or the controls protecting donations and private operational systems. The editorial image and the technology observation have separate sources and purposes.
What you can learn
Build an urgent-publishing workflow that includes source review, image context and correction handling. Preview long headlines with realistic photographs, and define how an approved change is refreshed across public caches without delaying critical information or exposing unpublished material.
Pros
The field photograph and specific headline give the report a clear editorial subject.
Permanent organizational routes remain visible above the urgent story.
Cons & considerations
Sensitive reporting needs careful image permissions, context and language that respects the people depicted.
Long headlines over photography require repeated checks for contrast, cropping and readability on smaller screens.
Earlier cited evidence retained; no current scan result. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.msf.org/ returned status 200 at https://www.msf.org/ with cf-ray: a54c4d2e8cc4062a-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Plex's saved discovery page combines a welcome area, a featured title and several visible browsing categories. Rows of artwork begin below, giving the visitor content to explore before the page becomes an account or playback workflow. The dense but grouped layout is useful for studying a public catalog with many possible entry points. Cloudflare's cf-ray header was observed on this route. That does not establish how licensed playback, recommendation systems or private libraries are delivered. The public discovery shell, user state and media streams should be treated as different responsibilities when planning caching and routing.
What you can learn
Inventory the page's data types before choosing edge behavior. Keep public catalog summaries separate from personalized recommendations and playback permissions, and preview unavailable artwork, long titles and empty rows as well as the ideal populated homepage.
Pros
Visible categories let readers begin with a topic instead of relying only on the featured title.
Artwork rows demonstrate the breadth of the catalog close to the first screen.
Cons & considerations
Dense media grids need consistent labels and keyboard behavior beyond their visual grouping.
Public availability and playback permissions may vary, so the interface needs clear handling of unavailable content.
Earlier cited evidence retained; no current scan result. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://watch.plex.tv/ returned status 200 at https://watch.plex.tv/ with cf-ray: a54c4d379f1e4a89-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Anthropic's captured homepage begins with a substantial institutional statement and a restrained navigation bar. A collection of small images introduces a public-benefit report below, giving the page a mix of organizational explanation and current publishing. The quiet editorial treatment is a useful reference for a technology company that wants readers to engage with its stated purpose and supporting material. Cloudflare's cf-ray header appeared on the public route. This identifies an edge-delivery relationship, not the infrastructure running AI inference or a verification of safety claims. The review evaluates visible communication, with the service architecture outside scope.
What you can learn
Give institutional claims maintained destinations with clear dates and authorship. Preview long-form excerpts and report artwork together, and keep marketing-page cache rules separate from authenticated products, APIs and any response containing user-provided information.
Pros
The opening statement explains the organization's position without depending on an animated demonstration.
A report feature offers a route from broad purpose into a more substantial publication.
Cons & considerations
Dense introductory copy needs careful mobile line length and hierarchy to remain approachable.
Institutional claims require supporting material and explicit boundaries rather than reassurance from a restrained visual style alone.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.anthropic.com/ returned status 200 at https://www.anthropic.com/ with cf-ray: a54c4d380acd08cc-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
GitLab's saved homepage uses a dark gradient, a large platform headline and a trial action. An announcement strip sits above the navigation, while a support-style chat panel occupies the lower-right area. The page demonstrates how marketing, product news and assistance can share the first screen, with the risk that each asks for attention at once. Its response included Cloudflare's cf-ray header. This supports edge participation for the public marketing route only; it does not establish the infrastructure of GitLab repositories, CI jobs or private customer instances. Those workloads require separate operational evidence.
What you can learn
Review overlays and announcements as part of the page, not as independent additions. Preview their combined mobile footprint, preserve the underlying reading and keyboard paths, and scope caching and security rules to the actual public or authenticated resource involved.
Pros
The primary proposition and trial route remain visually prominent within the dark composition.
Assistance is available without requiring readers to locate a separate contact page.
Cons & considerations
A chat panel can obscure content or compete with the main action on smaller screens.
Multiple promotional layers need ownership and expiry rules to avoid an overloaded or contradictory opening.
Vue.jsFramework dependency association; not independently observed
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://about.gitlab.com/ returned status 200 at https://about.gitlab.com/ with cf-ray: a54c4d8f9d6323fc-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
The World Health Organization's captured homepage places a current vaccination story below a substantial institutional header. Topic, country, newsroom and emergency routes remain visible, alongside search and language controls. The composition is useful for a large public-information site because it preserves practical routes while highlighting a current story. Cloudflare's cf-ray header was observed on the successful public response. This establishes a delivery-path signal, not a review of health guidance or a certification of the site's security and availability. The screenshot's editorial subject and the observed technology association should not be conflated.
What you can learn
Keep urgent notices, language variants and permanent topic pages within a coordinated publishing process. Preview long translated titles and campaign imagery, and define an update-and-purge workflow so corrected public information does not remain inconsistent across cached routes.
Pros
Task-oriented categories give readers routes beyond the featured story without requiring a deep menu search.
Language controls acknowledge the needs of an international audience in the stable page frame.
Cons & considerations
A substantial header needs careful mobile prioritization so search and essential categories remain usable.
Time-sensitive public information requires clear publication context and a dependable correction process beyond visual approval.
Public source checked November 3, 2026. References may be embedded or legacy—not a complete backend inventory.
Platform source: Observed public HTTP response. On 2026-11-03, an HTTP HEAD request to https://www.who.int/ returned status 200 at https://www.who.int/ with cf-ray: a54c4db168efdb59-LAX. Cloudflare participation in this response’s delivery path; not proof of Workers, Pages, a specific security plan, caching, or the origin provider. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Begin with the current origin and a route inventory. Preserve application behavior, redirects and necessary headers while testing a bounded change. Assign ownership for both the origin and the edge configuration so a delivery problem has a clear investigation path.
Use edge behavior for a specific public task
A redirect, a controlled response transformation or a defined cache policy should solve an identified requirement. Document inputs, exceptions and rollback. Avoid adding logic merely because it can run close to visitors; every extra rule becomes part of the system someone must maintain.
Treat application hosting as a separate architecture decision
Workers or other application products have their own runtime and data requirements. A cf-ray header alone does not prove that a reference site uses them. Evaluate the application’s needs directly and keep public content, authenticated behavior and durable data responsibilities clear.
From references to requirements
Plan cache boundaries, verification and recovery
Classify content by sensitivity and change rate
A hashed image, an event notice and an account response should not share a policy by accident. Define the intended behavior for each class and test representative URLs. Include query strings, cookies and authentication in the review where they affect the actual response.
Verify a correction after invalidation
Cloudflare provides targeted cache-purge options. A successful purge API response is not itself proof that a specific cached object changed, so request the relevant resource afterward and inspect the result. Keep the correction process understandable to the people responsible for publishing.
Record the previous configuration, the changed routes and the observations that would trigger reversal. Check real public tasks after release without submitting production forms. Keep origin failures, edge-rule failures and external integration problems distinguishable in the operating notes.
A useful handover demonstration
Ask the actual team to carry out its routine job: publish a realistic update, correct a mistake, preview a narrow screen, and identify who owns an integration failure. For a library or frontend framework, also ask who maintains the content source and deployment. A polished screenshot does not answer those operational questions.
Beyond the screenshot
A Cloudflare website change checklist
Identify the origin and the owner of each public or authenticated service.
Classify public documents, immutable assets, APIs and personalized responses.
Review actual origin headers and edge rules rather than assuming default caching.
Test redirects, query behavior, missing pages and key application handoffs.
Keep private and user-specific responses outside unintended shared caches.
Check content corrections and expired campaigns after any purge or invalidation.
Inspect the public page on narrow screens and through keyboard navigation.
Record the configuration change, verification evidence and scoped rollback path.
Test with real content, a keyboard, a small screen, slow or failed requests, and the people who will maintain the system. These are planning checks, not an accessibility, security, performance, or search-ranking certification.
Sources & editorial method
How this Cloudflare collection was reviewed
Each selected public route returned a successful HTTP response with cf-ray on November 3, 2026. The observation establishes Cloudflare participation in that request’s delivery path only. It does not establish a particular Cloudflare product, plan, cache policy, origin provider or security outcome. The 20 actual website captures were reused from the verified catalog and visually reviewed with their original dates and dimensions preserved. No private data, transactions or production forms were exercised.
Every image is an unmodified capture from the actual website, with its source and capture date. Some captures are reused from our shared catalog; their dates remain the original capture dates. None comes from a vendor gallery or a generated reconstruction. Moving imagery and live content can change.
Technology attribution uses public page assets or metadata, official platform documentation, or a cited first-party project case study. Documentary and framework-relationship evidence is identified where used; it is not a complete current backend inventory. A CMS image CDN alone does not establish a full CMS deployment. A library’s presence does not prove which individual controls use it, and a platform label does not establish AI authorship.
The composition notes, lessons, pros and tradeoffs are original editorial observations. We have not measured conversion, traffic, security, performance or accessibility conformance. Website owners retain their brands and imagery; these examples are not our client portfolio. Written, Edited and Curated are independent records, not dates advanced by a build. See our editorial standards or suggest a correction.
Questions worth asking
Cloudflare website development FAQs
Does Cloudflare mean a website is built with Workers or Pages?
No. A site can pass through Cloudflare while its application and content system run elsewhere. The evidence here does not claim Workers or Pages usage.
Does a cf-ray header prove a page was cached?
No. It indicates Cloudflare participation in the request path. Cache behavior requires separate evidence from the response and the configured rules.
Should every public-looking page be cached?
No. A page may vary by account, cookie, query or another input. Classify the response and its privacy requirements before choosing a shared-cache policy.
Can an edge change affect a form or account page?
Yes, depending on its scope. Review application routes and test safe error and handoff states before applying broad routing or caching changes.
Do these examples prove Cloudflare makes a site secure or fast?
No. We observed public responses and reviewed composition. Security, performance and availability need their own defined tests and evidence.
Use the edge layer to support the site’s actual content and application requirements, with boundaries and recovery steps that remain clear after launch.
