Skip to content

Commit 48d4712

Browse files
authored
Merge pull request #209 from wp-cli/regenerate-readme
2 parents 60cd45a + 9639487 commit 48d4712

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ Quick links: [Overview](#overview) | [Using](#using) | [Installing](#installing)
1111

1212
`wp profile` monitors key performance indicators of the WordPress execution process to help you quickly identify points of slowness.
1313

14-
Save hours diagnosing slow WordPress sites. Because you can easily run it on any server that supports WP-CLI, `wp profile` compliments Xdebug and New Relic by pointing you in the right direction for further debugging. Because it runs on the command line, using `wp profile` means you don't have to install a plugin and deal with the painful dashboard of a slow WordPress site. And, because it's a WP-CLI command, `wp profile` makes it easy to perform hard tasks (e.g. [profiling a WP REST API response](https://danielbachhuber.com/tip/profile-wp-rest-api/)).
14+
Save hours diagnosing slow WordPress sites. Because you can easily run it on any server that supports WP-CLI, `wp profile` compliments Xdebug and New Relic by pointing you in the right direction for further debugging. Because it runs on the command line, using `wp profile` means you don't have to install a plugin and deal with the painful dashboard of a slow WordPress site.
1515

16-
[Identify why WordPress is slow in just a few steps](https://danielbachhuber.com/tip/identify-wordpress-slowness/) with `wp profile`.
16+
[Identify why WordPress is slow in just a few steps](https://make.wordpress.org/cli/handbook/how-to/figure-out-why-wordpress-is-slow/) with `wp profile`.
1717

1818
## Using
1919

0 commit comments

Comments
 (0)