Within analytics for a single site or the amalgamated data for what could be multiple sites at the company level, you will find this improved reporting in the new Cache Breakdown chart.

Getting a breakdown of cache performance

Navigate to the Cache Breakdown chart from a company Dashboard or the Site Information page for a particular WordPress environment by selecting Analytics in the left-hand menu and then clicking on the Cache tab at the top of the Analytics landing page:

This chart tallies the number of requests resolved by:

• Server cache
• Edge cache
• The CDN
• Non-cached responses

Your server cache consists of complete website pages generated dynamically by WordPress and then stored for a period on your website’s own hard drive. WordPress can deliver these again to website browsers without having to generate them from content in its database.

The contents of server cache can also end up in edge cache if you have enabled that free service. Pages served from edge cache don’t require any resources from your site’s server.

The CDN works like an edge cache for static content like images, video, linked JavaScript and CSS files, and downloads in numerous other document formats.

The new Cache breakdown chart gives you a clear view of the relative performances of the caches available to a Kinsta-hosted WordPress site.

And don’t forget that you can now dig deeper into MyKinsta Analytics data for charts like this one and view up to 90 days of traffic history.

Not already a Kinsta customer? Let us introduce you to the MyKinsta dashboard.

The post A new view of cache performance for your WordPress site appeared first on Kinsta®.

This update adds five new analytics endpoints to the Kinsta API, covering top countries, top cities, top client IPs, visits dispersion, and response code breakdown.

That makes it easier to pull traffic and request data into your own dashboards, reports, similar to Kinsta’s earlier analytics API releases, which focused on bringing usage and reporting data into external tools.

Get top countries and cities

You can now retrieve the top countries and cities behind traffic to a WordPress environment.

These endpoints are useful for understanding where visitors are coming from, identifying regional trends, or enriching your traffic reports.

Here is an example request for top countries:

curl -i -X GET \
 'https://api.kinsta.com/v2/sites/environments/{env_id}/analytics/top-countries?company_id={company_id}&time_span=30_days' \
 -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

A typical response returns a list of locations and their associated views:

{
 "analytics": {
   "analytics_response": {
     "key": "countries",
     "data": [
       {
         "name": "country",
         "views": "1000"
       }
     ]
   }
 }
}

The top cities endpoint works the same way. Replace top-countries with top-cities in the URL to retrieve city-level data instead.

You can learn more in the API documentation for top countries and top cities.

Identify top client IPs

The new top client IPs endpoint lets you see which client IP addresses generate the most traffic in an environment. This can help with traffic analysis, troubleshooting unusual spikes, or spotting repeat sources of requests.

Example request:

curl -i -X GET \
 'https://api.kinsta.com/v2/sites/environments/{env_id}/analytics/top-client-ips?company_id={company_id}&time_span=30_days' \
 -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

And this is what the response looks like:

{
 "analytics": {
   "analytics_response": {
     "key": "topClientIPs",
     "data": [
       {
         "ip": "0.0.0.0",
         "value": "1000"
       }
     ]
   }
 }
}

You can find more details in the API documentation for top client IPs.

Check visits dispersion over time

You can also retrieve visits dispersion data, which shows how traffic is distributed over time by category. This can help you understand patterns in visitor behavior and how traffic composition changes across a selected period.

Example request:

curl -i -X GET \
 'https://api.kinsta.com/v2/sites/environments/{env_id}/analytics/visits-dispersion?company_id={company_id}&time_span=30_days' \
 -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Here is what the response looks like:

{
 "analytics": {
   "analytics_response": {
     "key": "userAgent",
     "data": [
       {
         "name": "mobile",
         "dataset": [
           {
             "date": "2025-11-08T00:00:00.000Z",
             "percent": "30.20"
           }
         ]
       }
     ]
   }
 }
}

You can explore the available parameters in the API documentation for visits dispersion.

Review response code breakdown

The response code breakdown endpoint gives you a clearer view of how your environment responds to requests over time. This is especially useful for monitoring trends in successful responses, redirects, or errors as part of operational reporting.

Example request:

curl -i -X GET \
 'https://api.kinsta.com/v2/sites/environments/{env_id}/analytics/response-codes?company_id={company_id}&time_span=30_days' \
 -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Example response:

{
  "analytics": {
    "analytics_response": {
      "key": "responseCodes",
      "data": [
        {
          "response_code": "200",
          "data": [
            {
              "key": "2025-11-08T00:00:00.000Z",
              "value": "50"
            }
          ]
        },
        {
          "response_code": "404",
          "data": [
            {
              "key": "2025-11-08T00:00:00.000Z",
              "value": "5"
            }
          ]
        }
      ]
    }
  }
}

You can find full request and response details in the API documentation for response code breakdown.

Build on your analytics workflows

These new endpoints build on the analytics capabilities already available in the Kinsta API, giving you a more detailed view of traffic sources and request patterns.

Whether you’re building dashboards, auditing trends, or investigating anomalies, you now have more data points to work with through the API.

You can find all request examples and schema references in the Kinsta API reference.

The post Access more traffic and response insights with the Kinsta API appeared first on Kinsta®.

While we didn’t conduct wind tunnel tests, we’re confident that our new one-click access to the WordPress administrative interface from the MyKinsta dashboard can save you at least a dozen seconds every time you log in.

But this WordPress Admin auto-login feature isn’t just about saving time: it’s another way we’re making website hosting simpler and more secure.

Accessing WordPress Admin with one click

Enabling WordPress auto-login has changed the row of buttons at the top of the Site Information page in MyKinsta. When you navigate to that page for a specific WordPress environment (whether that be a live site or a staging site), you see options to Log in to WP Admin and Visit WP login:

The Visit WP login button gets you to the WordPress administration interface the old-fashioned way: where you enter a username or email address and a password in the form served up by wp-login.php.

The Log in to WP Admin button sends you directly into the WordPress administrative interface by matching the email address you use in MyKinsta with an email address among the WordPress user accounts.

These options mean you don’t have to store WordPress login credentials somewhere else, continually type, or copy, or paste passwords. Simpler and more secure.

If the address associated with your account in MyKinsta isn’t already linked to a user in WordPress, MyKinsta can auto-generate a WordPress user with administrator permissions for future one-click logins.

You are asked if that’s what you want to do:

A WordPress Admin user created by MyKinsta in this way will be assigned an auto-generated username. The first and last names found in your MyKinsta Account Settings are used to create a user-friendly display name in WordPress.

Enabling and disabling WP Admin auto-login

The WP Admin auto-login feature is enabled by default for all sites. Company Owners, Company Administrators, and Company Developers can disable (and re-enable) the capability for any environment by navigating to Sites > sitename > User management > WP Admin auto-login and clicking the Disable (or Enable) button:

Questions about WP Admin auto-login?

Here are some answers to likely questions about the MyKinsta auto-login feature for WordPress Admin:

Is this all part of MyKinsta’s SSO capabilities?

In late 2025, we unveiled single sign-on (SSO) functionality for MyKinsta, supporting the Security Assertion Markup Language (SAML) standard. The functionality allows organizations to mediate their teams’ access to MyKinsta using their preferred identity provider, but it does not extend to the WordPress Admin dashboard.

Kinsta’s one-click access to WordPress Admin is available to all of our customers, whether or not their organization uses SAML SSO to access MyKinsta. For users of SSO access to MyKinsta, one-click logins to WordPress Admin dashboards help organizations meet their need for simplicity and security.

Can I access WordPress directly using one of those auto-generated accounts?

When MyKinsta creates a new WordPress user account for auto-login (because it couldn’t find a matching email address in the WordPress database), it creates a strong password along with the randomly generated username for that new account.

Once created, that account can be used for manual access via wp-login.php (often accessed at /wp-admin/). However, you won’t know the password.

Two solutions are to auto-login to WordPress through MyKinsta and update the password in your user profile, or follow the “Lost your password?” procedure using your email address and WordPress’s own login form.

Changing your password in WordPress does not affect MyKinsta’s ability to log you in with one click.

What if I change my name or email address in MyKinsta?

An email address is the key to matching user accounts in MyKinsta with those in the WordPress user database. If you’re using the auto-login feature and change your email address in MyKinsta’s Account Settings, MyKinsta will attempt to log in to WordPress using that new address. If an account with that email address is not already in WordPress, MyKinsta will ask if you want to generate a new WordPress administrator’s account on the fly.

The first name and last name found in your MyKinsta Account Settings are used only when auto-generating a new WordPress user account for one-click login. That information becomes the user-friendly display name in WordPress. If you later change your name in MyKinsta without changing your email address, the display name in WordPress will remain unchanged.

The post Log in to WordPress Admin dashboards with a single click in MyKinsta appeared first on Kinsta®.