READINESS
The infrastructure that
keeps everything
online and resilient.
Readiness is the domain that determines whether the technical foundation underneath the business is stable and scalable. Hosting performance, uptime monitoring, server configuration, domain renewals, and the recovery capability that means a crisis is an inconvenience rather than a catastrophe.
Domain 08 · Typical State
Tending
Most active partnerships
99.8%
Target uptime when Readiness is Tending
Uptime monitoring active with immediate alerts
Hosting performance above acceptable thresholds
Domain renewal minimum 60 days from expiry
Staging environment available for safe testing
Server error rate below 0.5%
What this domain is
The business runs on infrastructure.
Infrastructure needs tending.
Readiness is the domain that nobody thinks about until something breaks. Then it is the only domain anyone can think about. When the website goes down, when the server slows to a crawl under traffic, when a domain expires because nobody was watching the renewal date: these are Readiness failures, and they affect every other domain instantly.
A tended Readiness domain means the infrastructure is not just functional but monitored, optimised, and prepared for growth. It means outages are detected in minutes rather than hours. It means there is a staging environment where changes are tested before they go live. It means the domain and SSL certificates are renewed automatically before anyone has to think about them.
Readiness is the technical foundation that every other domain builds on. Presence needs it to stay online. Reach needs it to pass Core Web Vitals. Intelligence needs it to keep analytics collecting data. When Readiness is tended, the rest of the stack can focus on growth rather than stability.
1s
Revenue impact per second of load time
Amazon calculated a 1-second delay costs 1% of revenue. For a serious business, server performance is a commercial variable.
4.2h
Average time to detect an outage without monitoring
Without uptime monitoring, businesses typically discover an outage when a client calls to complain.
$10k
Typical cost of a preventable domain expiry
Domain expiry causes email failure, website unavailability, and client trust damage. Monitoring makes it entirely preventable.
What Yutie does here
Every service in this domain,
named and explained.
Every service in the Readiness domain is about making the technical foundation reliable, observable, and recoverable. Nothing here is theoretical. Everything is operational.
01
Hosting Platform Management
Yutie manages the hosting environment where all digital assets live: cPanel configuration, server resource allocation, directory structures, and the maintenance tasks that keep hosting healthy over time.
cPanel account configuration and organisation
File system structure and permission audit
PHP version assessment and upgrade planning
Server resource monitoring (CPU, RAM, disk)
Hosting account security hardening
Email hosting configuration and quota management
Annual hosting plan review (right-sizing for actual needs)
02
Uptime Monitoring and Alerting
If the website goes down, Yutie knows before the client does. Uptime monitoring checks the site every minute and sends an immediate alert the moment it becomes unreachable.
Uptime monitoring service setup (UptimeRobot or equivalent)
Check frequency: every 1 minute
Alert channels: email and SMS for immediate response
Alert escalation after 5 minutes down
Monthly uptime percentage report
Uptime history in Shalom Score review
Incident log maintained for all downtime events
03
Performance Monitoring
Load speed is not static. It changes with content additions, traffic levels, and hosting changes. Yutie monitors server response time and page load speed continuously.
Server response time (TTFB) monitoring
Page load time tracking for key pages
Performance threshold alerts (e.g. TTFB above 800ms)
Monthly performance trend report
Core Web Vitals tracking (LCP, FID, CLS)
Performance degradation root cause investigation
Performance improvement intervention when threshold exceeded
04
Domain Portfolio Management
A business's domain names are irreplaceable assets. Losing one to expiry can cause email failure, loss of brand identity, and in some cases, permanent loss of a domain to a competitor.
Full domain portfolio audit (all domains owned by the business)
Expiry date monitoring for all domains
Renewal alert at 90, 60, and 30 days
Auto-renewal configuration where supported
Domain registrar access documentation
DNS record export and documentation
Domain transfer process if registrar change is needed
05
DNS Management
DNS is the directory that translates domain names into server addresses. Misconfigured DNS causes email failure, website unavailability, and integration breakdowns. Yutie manages it correctly.
Full DNS record audit and documentation
A record, CNAME, MX, TXT record management
Propagation monitoring after DNS changes
Email DNS configuration: SPF, DKIM, DMARC
Domain verification records for Google, Meta, and other platforms
DNS change testing protocol
DNS record change log maintained
06
Email Hosting Configuration
Professional email addresses on the business domain require correct hosting configuration. Yutie sets up, manages, and monitors the email hosting infrastructure.
Email hosting setup on cPanel or dedicated provider
MX record configuration and verification
Email account creation, quota, and permissions
Webmail access configuration
Email client setup guide (Outlook, Gmail, mobile)
SPAM filter configuration
Email hosting health monitoring (delivery rate, queue health)
07
CDN Configuration
A Content Delivery Network serves static assets (images, CSS, JavaScript) from servers geographically close to the visitor, dramatically reducing load time for users in different locations.
CDN provider selection and setup (Cloudflare or equivalent)
DNS configuration to route traffic through CDN
Cache rules configuration for static assets
Cache purge process documented
CDN performance metrics monitoring
CDN security features: DDoS protection, rate limiting
Free tier optimisation for cost efficiency
08
Staging Environment Setup
A staging environment is a copy of the production site where changes are tested before they go live. Without it, every update is a risk. With it, Yutie can test changes thoroughly before any client sees them.
Staging subdomain setup (e.g. staging.businessname.com)
Production environment clone to staging
Staging site password protection (not indexable by search)
Deployment workflow: staging to production
Database sync process from production to staging
Plugin and update testing on staging first
Staging environment access for owner testing
09
Error Monitoring and Resolution
A website produces errors that visitors see but the owner never hears about: 404 pages, 500 server errors, broken redirects. Yutie monitors for these and resolves them before they damage Presence or Reach.
404 error log monitoring (monthly)
Server-side error (500) detection and alert
Google Search Console crawl error monitoring
Broken link identification and fix
Redirect chain audit and compression
Error page customisation (branded 404 page)
Error rate in monthly Readiness report
10
Database Optimisation
Website databases accumulate overhead over time: post revisions, transient data, deleted records. An unoptimised database slows load time and increases hosting resource consumption.
Database size monitoring
Monthly database cleanup (revisions, transients, spam)
Database table repair and optimisation
Database backup before optimisation
Query performance monitoring where applicable
Database engine version monitoring
Optimisation results: before and after load time
11
Server Security Hardening
Server-level security is distinct from application-level security. Yutie configures the hosting environment to minimise the server-side attack surface.
Directory listing disabled across all folders
Sensitive file protection (.htaccess, wp-config.php)
File permission audit (correct permissions for all files and folders)
PHP error display disabled on production
Admin directory access restriction by IP where feasible
Brute force login protection
Server-level firewall rule review
12
Scale Readiness Assessment
When the business is growing, the infrastructure needs to be ready for the increased demand. Yutie assesses whether the current hosting setup can handle the expected growth and plans the upgrade path.
Current resource usage assessment (CPU, RAM, bandwidth)
Traffic growth projection based on Reach trajectory
Hosting plan upgrade recommendation and timing
Database performance under load assessment
CDN coverage adequacy review
Email volume capacity check
Scale readiness included in quarterly architecture review
Domain States
What each state looks like
in the Readiness domain.
Every domain is classified monthly as Tending, Waiting, or Quiet. Here is what each state means specifically for Readiness.
Tending
The infrastructure is stable, monitored, and ready.
When Readiness is Tending, the website has been up for 99.8%+ of the month, uptime monitoring is active, domains are 60+ days from expiry, the staging environment is in use, and server performance is within acceptable thresholds.
Uptime above 99.8% for the month
Server response time below 400ms
All domains more than 60 days from expiry
SSL certificate valid and auto-renewing
Staging environment active and in use for all changes
No unresolved 500 server errors
CDN serving static assets
Waiting
Core infrastructure in place, optimisation in progress.
Waiting means the hosting is functional and uptime monitoring is active, but performance optimisation, staging setup, or CDN configuration is in progress.
Uptime monitoring set up but alert channels not yet complete
Domain portfolio identified, some renewals outstanding
Staging environment planned but not yet built
CDN not yet configured
Database optimisation not yet scheduled
DNS documentation in progress
Quiet
The infrastructure is unmonitored and fragile.
Quiet means the hosting exists but nobody is watching it. Downtime is discovered when clients complain. Domain expiry is not monitored. There is no staging environment. The server has never been optimised.
No uptime monitoring
Domain expiry dates unknown
No staging environment
Server has never been optimised
DNS not documented
No error monitoring
Hosting plan not reviewed in more than 2 years
CDN not configured
The transformation
What changes when this domain
moves from Quiet to Tending.
Before: domain is quiet or unmanaged
Website downtime is discovered when a client calls to report it
A domain expires and email stops working before anyone notices
Every code change is made directly on the live site with no testing
The server slows under traffic because nobody has optimised it
Error pages appear for visitors but nobody in the business knows
After: domain is tended
Uptime monitoring alerts within 1 minute of any downtime event
Domain portfolio is monitored with 90-day advance renewal alerts
All changes are tested on staging before being deployed to production
Server performance is monitored and optimised before it degrades
Error logs are reviewed monthly and all critical errors resolved
Domain connections
How Readiness connects to the other domains.
No domain exists independently. The Shalom Score reflects how each domain affects the others.
01
Presence
Readiness keeps the website online. Without Readiness, Presence cannot be tended.
06
Stewardship
Server security hardening in Readiness overlaps with Stewardship's security monitoring scope.
07
Intelligence
Server uptime and performance data from Readiness is part of the monthly Shalom Score calculation.
02
Reach
Core Web Vitals in Reach depend on the server performance and CDN configuration held in Readiness.