ANAYIL GROUPHosting · My Domains Submit a Ticket
Help center
HomeWeb Performance Optimisation (WPO)[WPO-001] Separate origin latency from browser delay
Web Performance Optimisation (WPO)7 min•Difficulty: Intermedio

[WPO-001] Separate origin latency from browser delay

Measure DNS, connection, TLS, first-byte wait and download time to locate the slow segment.

Ingeniería de Rendimiento AnayilUpdated: 2026-10-10

Apply this guide to your situation

This answer covers “[WPO-001] Separate origin latency from browser delay”. Read it with the summary and confirm that the symptom and service match what you are experiencing. Available options can vary by plan and account setup.

  • Before changing anything, note what you expected, what happened and roughly when. Check whether the issue affects one page or the whole service.
  • Save the full error message and note recent changes. Hide passwords, access codes, personal data and keys before sharing screenshots or logs.
  • If a step requires administrator access, restarting services or editing server files, stop if you do not administer that server. Send support the service name, error and checks you have already made.

L3 technical diagnosis

Performance / configurationSeverity: Medium; high if conversion or availability is affected

User symptoms

The page feels slow before content appears. Compare repeated requests and a static route with a dynamic route.

Observed code or message

High TTFB; curl reports a high `time_starttransfer`

Likely root cause

Total time combines DNS, TCP connection, TLS negotiation, upstream wait and transfer. Without separating timings, the bottleneck could be the network, proxy, application or a large response.

Likely-cause and resolution matrix

Follow a branch only when evidence supports it. A symptom may have more than one cause; do not change layers by guesswork.

01Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

02Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

03Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

04Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

05Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

Prerequisites

  • Authorised access to the affected site, repository or service metrics.
  • A reproducible URL and timestamp; use staging for infrastructure changes.
  • A backup or rollback method for configuration and deployments.

Important warnings

  • Inspection commands do not authorise production changes. Do not run load tests or global purges without an approved plan.
  • Never store private responses in shared caches. Server changes in Anayil Panel depend on the controls available for the service and may require its administrator/provider.

Step-by-step walkthrough

1. Reproduce and narrow the issue

The page feels slow before content appears. Compare repeated requests and a static route with a dynamic route. Run repeated samples against a public URL and compare a small static route. Record UTC time, region and HTTP status.
bash
curl -sS -o /dev/null -w 'dns=%{time_namelookup} connect=%{time_connect} tls=%{time_appconnect} ttfb=%{time_starttransfer} total=%{time_total} code=%{http_code}\n' https://example.com/
Expected output:
High TTFB; curl reports a high `time_starttransfer`

2. Apply the appropriate correction

If DNS, connection or TLS dominate, share evidence with the network or proxy operator. If `time_starttransfer` rises only on dynamic pages, correlate upstream, application and database logs. If `total - ttfb` dominates, inspect response size and compression. Do not tune limits before locating the slow segment.

3. Verify the experience

Repeat at least five requests under comparable conditions; confirm the corrected segment improves without increasing errors.
Expected output:
The improvement is reproducible on the affected route and profile with no new functional errors.

Troubleshooting & Solutions

High TTFB; curl reports a high `time_starttransfer`

Root cause: Total time combines DNS, TCP connection, TLS negotiation, upstream wait and transfer. Without separating timings, the bottleneck could be the network, proxy, application or a large response.

Resolution: If DNS, connection or TLS dominate, share evidence with the network or proxy operator. If `time_starttransfer` rises only on dynamic pages, correlate upstream, application and database logs. If `total - ttfb` dominates, inspect response size and compression. Do not tune limits before locating the slow segment.

Rollback and recovery plan

Roll back only the changed directive, dependency or release using the recorded value. If 5xx errors, data exposure or session failures occur, have the operator disable the new rule and retain redacted logs for analysis.

Related runbooks in this category:

Was this technical guide helpful?

Facing a production outage?

Hosting Anayil system administrators can directly intervene on your server infrastructure.

Open Support Ticket at Hosting Anayil