Authentication for API in Wordpress - Performance & Optimization

Performance: Authentication for API

MEDIUM IMPACT

This affects the time it takes for the API to respond and the initial page load speed when fetching data from the API.

Securing API requests in WordPress

Wordpress

function call_api_with_jwt() {
  $token = get_transient('jwt_token');
  if (!$token) {
    $response = wp_remote_post('https://example.com/wp-json/jwt-auth/v1/token', array(
      'body' => array('username' => 'user', 'password' => 'password')
    ));
    $body = json_decode(wp_remote_retrieve_body($response));
    $token = $body->token;
    set_transient('jwt_token', $token, 3600);
  }
  $response = wp_remote_get('https://example.com/wp-json/wp/v2/posts', array(
    'headers' => array('Authorization' => 'Bearer ' . $token)
  ));
  return wp_remote_retrieve_body($response);
}

JWT tokens are cached and reused, reducing repeated authentication overhead and speeding up API calls.

📈 Performance GainReduces API response delay by 100-200ms per call due to token reuse and less processing.

Securing API requests in WordPress

Wordpress

function call_api_with_basic_auth() {
  $response = wp_remote_get('https://example.com/wp-json/wp/v2/posts', array(
    'headers' => array('Authorization' => 'Basic ' . base64_encode('user:password'))
  ));
  return wp_remote_retrieve_body($response);
}

Basic authentication sends credentials with every request and can cause slower response times due to repeated encoding and lack of token caching.

📉 Performance CostAdds extra processing on each request, increasing API response time by 100-200ms per call.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Basic Auth on every request	Minimal	0	Low	[X] Bad
JWT token caching	Minimal	0	Low	[OK] Good

Rendering Pipeline

Authentication affects the network request phase and delays the time before content can be rendered because the browser waits for API responses.

→Network Request

→JavaScript Execution

→Rendering

⚠️ BottleneckNetwork Request latency due to authentication overhead

Core Web Vital Affected

INP

This affects the time it takes for the API to respond and the initial page load speed when fetching data from the API.

Optimization Tips

1Cache authentication tokens to avoid repeated login requests.

2Avoid sending credentials on every API call to reduce network latency.

3Use efficient authentication methods like JWT to improve interaction responsiveness.

Performance Quiz - 3 Questions

Which authentication method typically reduces API response time in WordPress?

A Sending Basic Auth credentials on every request

B No authentication at all

C Using JWT tokens with caching

D Using OAuth without token caching

DevTools: Network

How to check: Open DevTools, go to the Network tab, filter API requests, and inspect the timing details of authentication headers and response times.

What to look for: Look for repeated authentication requests and long waiting times before API responses to identify inefficient authentication.