What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To monitor WordPress with New Relic, install the Infrastructure agent and PHP agent on the WordPress host, set the application name and license configuration, restart Apache, Nginx or PHP-FPM, then generate real requests. New Relic’s WordPress APM view can show transaction duration, PHP work, database and web-server activity, and WordPress hook, plugin and theme callbacks. Add browser monitoring—automatically through the PHP agent or manually with timing calls—to connect backend response time with the experience in a visitor’s browser.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What New Relic monitors in a WordPress site
WordPress performance is rarely a single number. A slow page can result from PHP execution, a plugin callback, a theme function, a MySQL query, Apache or Nginx, or work done in the visitor’s browser. New Relic’s full-stack WordPress integration is designed to put those layers in one investigation path rather than making you guess from a page-speed score.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Application requests: APM transactions and call duration show which request paths are slow and how much time is spent in application code or dependencies.
- WordPress execution: WordPress-specific instrumentation measures hook execution time and callback counts, with attribution to plugins and themes.
- Infrastructure dependencies: PHP, Apache and MySQL telemetry can be viewed with the application data.
- Real-user loading: Browser monitoring records front-end timing so a slow server response can be separated from delays after the response reaches the browser.
The result is a chain you can follow: a visitor-facing page or transaction, the PHP work behind it, the WordPress hook or callback consuming time, and the database or web-server activity involved. The integration’s stated purpose is to help diagnose issues in a WordPress application and optimize its code.
Requirements and access to confirm first
WordPress and PHP compatibility
Check New Relic’s current compatibility documentation before changing the site. The WordPress-specific functionality lists WordPress 6.0 or later. Confirm the PHP version and operating environment against the PHP agent’s requirements as well; compatibility can differ between a self-managed server, a container and a managed host.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Server-level access
The normal installation requires access to the WordPress host. You need a way to install the Infrastructure agent, install the PHP agent, edit its configuration, and restart the process that loads PHP. Depending on the stack, that means Apache, Nginx with PHP-FPM, or another PHP-FPM service. On shared or managed hosting, those actions may be restricted. Ask the provider whether it supports New Relic’s Infrastructure and PHP agents and whether it will perform the restart.
Information to have ready
- Your New Relic account and license configuration value.
- A distinctive application name for this WordPress installation. Include the site’s role or environment when you operate more than one instance, so staging and production do not merge into one service.
- The web-server and PHP process arrangement, including whether PHP runs through PHP-FPM.
- Permission to create real requests after installation for verification.
Install the agents in the correct order
New Relic’s PHP monitoring has two parts: a PHP extension that collects data from the application and a local proxy daemon that transmits it to New Relic. The Infrastructure agent supplies host-level telemetry. Both layers matter when you need to distinguish PHP or WordPress work from machine, web-server or database behavior.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- Review requirements. Confirm the WordPress version, PHP environment and host permissions against New Relic’s compatibility and installation documentation.
- Install the Infrastructure agent. Use New Relic’s guided installer when the host is supported and you have the required privileges. Use the documented manual installation method when your operating system, image or provisioning system requires it.
- Install the PHP agent. Install the PHP extension and the local proxy daemon on the same host. The extension must be loaded by the PHP runtime serving WordPress; installing files without loading the extension will not produce PHP transactions.
- Set the license configuration. Enter the account’s license value in the agent configuration using the method appropriate to your installation. Protect the value as you would any other service credential.
- Set the application name. Choose a name that identifies this site and environment in APM. Avoid a generic name shared by unrelated WordPress instances.
- Restart the serving processes. Restart Apache or the relevant web server, and restart PHP-FPM when PHP-FPM is used. A restart is required for the PHP extension and changed configuration to take effect.
- Exercise the site. Request the home page, a representative content page, an administrative or authenticated route if it is safe to do so, and any important dynamic endpoint. New Relic needs real transactions before the application view can display useful data.
- Allow ingestion time. New Relic advises waiting several minutes for application data to appear. Do not conclude that installation failed immediately after the first restart.
Do not install only the browser script and call the site monitored. Browser timing can show what a visitor experienced, but it cannot identify the PHP callback, WordPress hook, MySQL activity or server process that caused a slow response. Conversely, APM alone cannot show delays that occur after the response has arrived in the browser.
Open and read the WordPress APM view
Find the application
In New Relic, open APM & services and select the application name you configured for WordPress. The WordPress integration supplies a pre-built dashboard with transactions, visitors and call duration, alongside PHP, Apache and MySQL information.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Start with transactions and call duration
Use transaction duration to identify the request paths that consume the most time. Compare more than one request type: a home page, an individual post, search, a catalog or membership route, and an API endpoint can execute different plugins and hooks. A high-duration transaction tells you where to start; its associated trace and dependency information tells you whether the time is in WordPress code or outside it.
Separate application time from dependencies
When a transaction is slow, inspect its breakdown rather than treating total duration as a plugin verdict. Time attributed to PHP application code points toward WordPress execution, while database or web-server segments point to a dependency or serving layer. The full-stack integration lets you view MySQL and Apache telemetry with the PHP application data, so you can test those alternatives in the same incident.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Use visitors as context
Visitor and request volume changes the meaning of a duration spike. A callback that is tolerable on a quiet site can become a capacity problem when traffic rises. Compare the slow transaction with its request volume and time window before changing code or disabling a feature.
Find a slow WordPress plugin, theme or hook
Understand what hook instrumentation measures
WordPress-specific instrumentation records hook execution time and callback counts and can attribute the work to plugins and themes. This is more actionable than a list of active plugins: it shows which callbacks actually ran during a transaction and how much execution time they consumed.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
- Open a slow transaction in the WordPress APM application.
- Inspect the WordPress hook and callback details for that request.
- Sort or filter by execution time to find callbacks that dominate the request.
- Check callback counts. A short callback invoked hundreds of times can matter as much as a longer callback invoked once.
- Map the callback to its plugin or theme attribution, then reproduce the same route with the feature enabled before making a change.
- After a code, configuration or plugin change, generate the same type of requests and compare transaction and hook data over a comparable period.
Attribution is a diagnostic lead, not proof that a plugin is defective. A plugin callback may be waiting on MySQL, calling another service or running because a theme or another plugin triggered its hook. Follow the dependency timing before removing functionality.
Choose the right hook-detail setting
The setting newrelic.framework.wordpress.hooks.options controls how much WordPress callback detail is collected. More detail can make a diagnosis easier, but it also increases instrumentation work and data volume. Select the least detailed mode that answers the question you are investigating.
| Mode | What it records | Best use | Trade-off |
|---|---|---|---|
all_callbacks |
The broadest callback detail across instrumented hooks. | Initial investigation when you do not yet know which plugin, theme or callback is involved. | Highest detail and potentially the greatest instrumentation overhead. |
plugin_callbacks |
Focuses on callbacks supplied by plugins and themes. | Finding extension or theme work while reducing unrelated callback detail. | Less broad than recording every callback, so a non-plugin callback may not be visible. |
threshold |
Records only hooks exceeding the configured threshold. New Relic documents a 1 ms default. | Production monitoring where you need to surface materially slow hooks without collecting every short callback. | Fast hooks below the threshold are omitted, which can hide high-frequency low-duration work. |
Use broad detail temporarily when tracing an unknown problem, then move to a narrower setting once you know which evidence you need routinely. If you change this option, reload the PHP configuration in the same way as other agent changes and restart the relevant PHP or web-server process.
Monitor backend response and browser loading together
Automatic browser instrumentation
The PHP agent can inject the New Relic browser agent automatically. This is the simplest way to connect a server-side transaction with front-end timing when the site’s response structure allows the injection. After enabling it, request a normal page and allow the browser data time to arrive before judging the result.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Manual browser instrumentation
Manual instrumentation is useful when automatic insertion is unsuitable or when the site controls its document template directly. Place the generated browser header in the document head and the generated footer immediately before the closing </body> tag. Preserve the placement exactly: the head starts browser timing early, while the footer lets the agent capture the end of page loading.
Interpret the two data sets as one request
- If the backend transaction is long and browser response timing is also long, investigate PHP, hooks, database calls and server capacity first.
- If the backend completes quickly but browser timing is poor, inspect front-end work, resource loading and browser-side conditions rather than blaming a PHP callback.
- If backend traces show a normal request but only some visitors report delays, compare browser timing by affected experience and environment.
Browser and APM data are complementary, not interchangeable. A page-load measurement cannot identify the slow WordPress hook, and a PHP transaction duration cannot describe everything that happens after the first byte reaches a visitor.
Installation choices by hosting model
| Hosting situation | Installation access | Backend depth available | Likely constraint |
|---|---|---|---|
| Self-managed virtual or dedicated server | Usually direct root or administrator access for the Infrastructure agent, PHP extension, proxy daemon and restarts. | Infrastructure, PHP transactions, WordPress hooks, plugins and themes, Apache or Nginx, and MySQL when each component is configured. | You are responsible for process restarts, configuration correctness and protecting the license setting. |
| Containerized WordPress | Depends on whether the image and runtime permit the agents and a local proxy daemon. | Potentially the same application and dependency layers, provided the agents can load in the serving container and report from the correct host context. | Image rebuilds, process supervision and ephemeral containers can make installation and persistence different from a traditional server. |
| Managed WordPress or shared hosting | Often no root access; provider involvement may be required. | What the host exposes. PHP and browser monitoring may be possible even when Infrastructure or server telemetry is not. | The provider may restrict extensions, daemons, configuration files or restarts. Confirm support before attempting installation. |
Compare an approach on four practical axes: whether you can install and restart services, how deeply it can inspect PHP and WordPress, whether browser timing is available, and how much instrumentation detail the host can tolerate. A managed host that cannot load the PHP extension cannot provide the same hook-level diagnosis as a server you control.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify data after the restart
A successful service restart only proves that a process restarted; it does not prove that the correct PHP runtime loaded the agent. Verify in this order:
- Make a real request to the WordPress site after the restart. Include a route that normally exercises the code you want to inspect.
- Wait several minutes, then check APM & services for the configured application name.
- Confirm that transactions and call duration are populated rather than viewing an empty dashboard.
- Open a transaction and look for PHP and WordPress execution details.
- Check the related Infrastructure, Apache and MySQL views when those agents or integrations are installed.
- For browser monitoring, load a page in a normal browser and allow more ingestion time. New Relic’s browser installation guidance directs you to troubleshooting if data is still absent after more than 15 minutes.
Generate traffic after every configuration change. An idle site can look unmonitored simply because no transaction has been created since the agent loaded.
Troubleshoot missing or incomplete telemetry
No application appears in APM
- Check that the PHP extension is loaded by the PHP runtime serving WordPress, not only by a command-line PHP binary.
- Recheck the license configuration and application name for spelling, scope and the configuration file actually used by the web process.
- Restart Apache, Nginx or PHP-FPM after changing the agent settings.
- Generate new requests and wait several minutes before checking again.
Transactions appear but WordPress detail is absent
- Confirm that the WordPress-specific compatibility requirements are met, including WordPress 6.0 or later for the documented functionality.
- Check which PHP process serves the site and whether that process can load the WordPress instrumentation.
- Review the hook-detail option and its threshold. A threshold mode will omit hooks that do not exceed the configured limit; the documented default is 1 ms.
Browser data is missing
- Confirm that automatic injection is enabled, or verify that the manually generated header is in the document head and the footer is immediately before
</body>. - Inspect the page’s content-security policy and other restrictions that can block the browser agent.
- Check response content-length or output handling if the automatic injector cannot safely modify the response.
- Check hosting permissions and allow more than 15 minutes for browser data before escalating to the documented troubleshooting path.
Only some requests are visible
Compare the missing route with the route that reports data. Different PHP pools, web servers, caches or hostnames can serve different requests. A full-page cache may prevent PHP from running at all, while an API or authenticated request still reaches the instrumented process. Verify the serving path before changing WordPress code.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Use the data to make a safe performance change
- Define the symptom. Record the route, approximate time window and whether the complaint is a slow server response, a slow browser load or both.
- Find the transaction. Use APM transaction duration and request volume to locate the matching request path.
- Locate the layer. Decide whether the dominant segment is PHP/WordPress, a hook or callback, MySQL, Apache/Nginx or browser work.
- Increase detail only when needed. Use
all_callbacksfor an unknown WordPress problem,plugin_callbacksfor extension-focused work, orthresholdto limit routine collection. - Change one cause at a time. Adjust the responsible plugin configuration, query, theme callback or server setting in a controlled environment when possible.
- Reproduce the original request. Use the same route and comparable traffic conditions, then compare transaction, dependency and hook timing.
- Keep the evidence that answers the question. Once the cause is understood, reduce callback detail if the broader mode is no longer necessary.
This process prevents a common mistake: disabling a plugin because it appears in a slow request when the actual delay is a database dependency or another callback that caused it to run.
What New Relic cannot establish by itself
Telemetry identifies observed execution and timing; it does not automatically prove a universal ranking of plugins or a permanent fix. Results depend on the routes requested, traffic pattern, cache state, PHP runtime and instrumentation settings. The available documentation does not establish a universal benchmark or market-wide performance number for WordPress sites. Treat the 1 ms hook threshold as a configuration default for threshold-mode instrumentation, not as a definition of a slow WordPress hook for every site.
Likewise, browser monitoring does not replace testing on the devices, networks and page types that matter to your visitors. Use it to connect a real browser experience with the corresponding backend transaction, then investigate the layer where the timing actually accumulates.
Quick Recap
A practical monitoring baseline
- Keep a distinct New Relic application name for each important WordPress environment.
- Keep the Infrastructure and PHP agents on the same serving path as the site they describe.
- Verify data after restarts with real requests instead of relying on process status alone.
- Begin investigations with transactions and call duration, then move into hooks, plugins, themes and dependencies.
- Use browser instrumentation when the question includes visitor-perceived page loading.
- Choose the lowest hook-detail level that still answers the current diagnostic question.
- When data is missing, check agent loading, license and configuration values, process restarts, CSP or response constraints, and hosting permissions before editing WordPress code.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
