This article describes an OCI and Cloudflare setup for a WordPress blog with overseas readers, including the DNS, HTTPS and caching conditions to check before applying it.
For overseas readers, consider both latency to the origin and the time needed to load page resources. A WordPress site hosted in one OCI region can have different response times across visitor locations. This article explains the CDN connection steps and the conditions to check when measuring cache benefits.
My Infrastructure Configuration
The original article used the following setup. Current Free Tier eligibility and resource availability require separate checks:
- Created an Oracle Cloud (OCI) account in the Korea region utilizing free-tier resources
- Purchased a domain through name.com (for example, datainhands.com)
- Connected the domain to a WordPress instance
- Completed basic WordPress configuration
What is Cloudflare?
Cloudflare provides CDN, DNS, DDoS protection and web application firewall services. Serving eligible content from its network can reduce requests to the origin. Performance changes and available security or optimization features depend on content, settings, visitor location and plan.
Key Benefits of Cloudflare Implementation
Consider the following features and potential effects. Check their availability for your plan and configuration:
Global Performance Enhancement
- Delivery of eligible content through a distributed network
- Cached content served through the Cloudflare network
- Potential reduction in origin requests and some loading delays on cache hits
- Smart routing: check separate availability and pricing
Security Strengthening
- Free SSL/TLS certificate provisioning
- Robust DDoS protection features
- Web Application Firewall (WAF)
Optimization Features
- Auto Minify was deprecated in August 2024 and is not a current optimization feature
- Image optimization: check the plan and conditions for each feature
- Network routing: check product availability and pricing
- Caching policies suited to the response type
Implementation Guide
1. Cloudflare Account Setup
Begin by creating your Cloudflare account:
- Navigate to cloudflare.com
- Click the “Sign Up” button in the top right corner
- Enter your email address and create a password
- Complete the email verification process
2. Domain Registration Process
Follow these detailed steps to register your domain with Cloudflare:
- In the Cloudflare dashboard, locate and click “Add Site”
- Enter your domain name purchased from name.com
- Check the features and limits you need; this example selected the Free plan
- Review the available features and confirm your selection
3. DNS Configuration Migration
This critical step requires careful attention to detail:
Reviewing Existing DNS Records
The DNS quick scan can miss records. Before changing nameservers, compare it with the existing DNS inventory, including A, AAAA, CNAME and mail-related MX and TXT records. If the setup points directly to an OCI origin IP, verify that address as well.
- Compare the scan with the existing DNS inventory and check for missing records
- Verify the OCI instance’s A record accuracy
- Click “Continue to activation” after confirmation
4. Nameserver Update Process
For a full DNS setup, replace the registrar nameservers with those assigned by Cloudflare to this domain. This example uses name.com. Review the DNS inventory, DNSSEC state and rollback nameservers before proceeding:
1. Copy the Cloudflare-provided nameserver addresses (typically two are provided)
2. Access your name.com dashboard
4. Locate the nameserver configuration area
6. Input the Cloudflare nameservers
7. Save your changes
Transition time depends on the registrar, DNS caches and checking intervals. A completion email or an Active status does not prove every visitor resolver has refreshed. Check DNS answers in the locations that matter to the site.
5. SSL/TLS Security Configuration
Navigate to the SSL/TLS section in your Cloudflare dashboard for security setup:
Certificate Mode Configuration
- Access the SSL/TLS tab
- Navigate to the Overview section
- Select SSL/TLS encryption configuration
Custom SSL/TLS Option
Do not assume an origin uses a self-signed certificate merely because it runs on OCI. For HTTPS requests, Full encrypts the origin connection but does not validate the certificate’s trust, expiry or hostname. HTTP requests also use HTTP to the origin; selecting Full alone does not enforce HTTPS.
Prefer Full (strict) where possible, after verifying that the origin serves HTTPS on port 443 and presents an unexpired certificate from a publicly trusted CA or Cloudflare Origin CA, matching the requested or target hostname. Unmet certificate requirements can cause error 526. Confirm the current certificate and a recovery path before changing a production mode.
Edge Certificate Setup
- Navigate to Edge Certificates section
- Review whether HTTPS redirection is needed and whether it conflicts with existing WordPress or origin redirects before enabling Always Use HTTPS
- TLS 1.2 is the value shown in this example. Choose the minimum based on client support and policy; this edge setting does not set the origin connection TLS version
- Review each additional option and its compatibility before changing it
6. Cache Optimization Settings
Cloudflare edge caching and visitor browser caching are separate. Review content types, response headers and existing rules in the current cache menus.
Basic Cache Configuration
The values below are historical examples, not universal WordPress recommendations. Compare them with the current features and update requirements before applying them:
- Browser Cache TTL: 4 hours
- Always Online: Enabled
- Cache Level: Standard
Page Rules Configuration
The Page Rules screen below is a historical example. For new cache configuration, consult the current Cache Rules documentation. Browser Cache TTL is separate from Edge TTL; determine it from update requirements and origin headers. If allowing HTML caching, exclude authenticated and personalized responses as well. The admin-path example alone is not a complete bypass policy:
- Access the Page Rules tab
- Click Create Page Rule
- For WordPress admin pages:
- URL pattern: wp-admin
- Setting: Cache Level: Bypass
Cloudflare caches content according to eligibility and request/response conditions. Its default CDN behavior does not cache HTML or JSON, so connecting a domain does not automatically cache every WordPress page. Check static assets and HTML responses separately.
Inspect CF-Cache-Status and related headers for individual requests. HIT means that response was served from the Cloudflare cache; it does not prove site-wide correctness or privacy. Also verify responses that must bypass caching.
7. WordPress Optimization Configuration
Performance Optimization
Official documentation checked on 2026-10-03: distinguish the settings shown in this 2025 guide from current features.
- Auto Minify was deprecated on 2024-08-05. Do not follow the former enablement steps for JavaScript, CSS and HTML minification.
- The Brotli setting and API were deprecated on 2024-08-15; compression support itself was not removed. Response compression depends on factors including the browser’s Accept-Encoding header, plan and compression rules.
- Rocket Loader is available on plans including Free, but should not be enabled indiscriminately. Test JavaScript behavior separately; disable it and retest if issues occur.
Image Optimization
- Polish is unavailable on Free and available on Pro, Business and Enterprise. Skip Polish enablement when using the Free plan.
- Do not treat “Lazy Loading: On” as a universal setting without identifying its implementation. If it meant Mirage, that feature is now deprecated. Do not change an existing site’s image-loading configuration based on this guide alone.
8. Monitoring and Analytics Setup
Analytics Tool Configuration
- Access the Analytics tab
- Enable Web Analytics
- Check existing tracking and automatic insertion first. If manual insertion is required, follow the official instructions through a maintainable insertion method; do not default to editing the parent theme header.php or duplicating the snippet
Performance Monitoring Setup
- Use the current performance and analytics views, separating visitor locations and measurement conditions
- Monitor page load times
- Track cache hit rates
9. Troubleshooting and Maintenance
Cache Management
If stale responses remain after a content update, identify the cache layer and affected URLs first:
- Go to Caching → Configuration
- Prefer purging changed URLs where supported. Purging everything can increase origin requests; review the required scope and custom cache-key conditions before choosing it
SSL Issue Resolution
For mixed content warnings:
- Identify HTTP resources and how their URLs are generated; review HTTPS at the origin, redirects and WordPress URL settings together
- If stored URLs require replacement, prepare a backup and rollback, and verify the scope with a tool that preserves WordPress serialized data. A mixed-content warning alone is not a reason to run an immediate database-wide replacement
Configuration Verification
After implementation, verify:
- SSL functionality:
- Inspect connection/certificate details and mixed-content errors; the icon alone does not establish origin certificate verification
- Run SSL Labs test
- Page load performance:
- Conduct Google PageSpeed Insights analysis
- Perform GTmetrix performance testing
- Cache behavior:
- Check cache response headers
- Monitor Cloudflare cache hit rates
Expected Performance Improvements
The original 50–70% claim below lacks verified benchmark conditions and source results. It is not a general guarantee or a validation of this site today. Measure actual effects for cache hit ratio, content, visitor location and origin response time.
Historical claimed benefits (not guaranteed):
- Global page loading time reduction of 50-70%
- Significant server load reduction
- Enhanced security posture
- Improved overall availability
- Better user experience worldwide
Conclusion
This guide describes an example OCI/CDN integration. Actual performance, reliability and support conditions must be verified for the deployment and visitor locations.
For questions, include the step and error symptoms in a comment. Do not share account credentials or authentication material.
Related: Advanced WordPress Security Configuration Guide | WordPress Performance Optimization | OCI Compute Instance Best Practices | Cloudflare Cache/CDN
WordPress 6.4+ and January 2025 identify the original applicability context, not current recommended versions or compatibility with every later release. Check official requirements, support lifecycles and current service documentation before applying it.