Once the Nfinite Performance Audit plugin is installed and activated, running your first audit takes less than a minute. The goal of this audit is to generate a high-level performance snapshot that highlights speed risks, configuration gaps, and optimization opportunities.
This guide walks you through the process step by step.
Step 1: Open the Audit Screen
In your WordPress dashboard, go to:
Nfinite → Performance Audit
This is the main control center for the plugin. From here, you can submit new audits and review previous results.
If this is your first time here, the page will appear empty. That’s expected.
Step 2: Enter the Site URL
In the audit form, enter the full URL of the site you want to analyze.
Best practices:
- Use the live production URL, not a staging or development domain
- Include the protocol (
https://) - Avoid pages that require login or cookies to load
Example:
https://example.com
At this stage, Nfinite focuses on the homepage by default, since it typically represents the heaviest and most important performance profile of a site.
Step 3: Submit the Audit
Click Run Audit.
The plugin will begin collecting performance signals related to:
- Page speed and loading behavior
- Core Web Vitals indicators
- Caching and render-blocking patterns
- Hosting and server response clues
- Plugin and theme risk signals
Most audits complete within a few seconds, depending on the site and server response time.
Step 4: Review the Audit Snapshot
Once the audit finishes, you’ll see a summarized report with scores, warnings, and detected issues.
This snapshot is designed to answer one question quickly:
“Is this site structurally sound from a performance standpoint?”
At this stage, you’re not expected to fix anything yet. The purpose is to:
- Identify obvious bottlenecks
- Confirm whether caching is configured correctly
- Spot hosting or server-related red flags
- Understand whether deeper analysis is required
What the First Audit Is (and Isn’t)
Your first audit is intentionally lightweight.
It is:
- A fast, automated health check
- A way to surface performance risks early
- A decision-making tool for next steps
It is not:
- A replacement for manual optimization
- A guarantee of passing Core Web Vitals
- A full diagnostic of every issue on the site
If the audit shows multiple high-risk signals, that’s usually a sign that a deeper performance review is needed.
Common First-Time Questions
Why don’t I see exact fixes yet?
The initial audit focuses on detection, not remediation. Fix recommendations are contextual and depend on hosting, themes, and plugins.
Can I run multiple audits?
Yes. You can audit as many sites as you want, or rerun audits after making changes.
Does this affect site performance?
No. Audits are read-only and do not modify your site.
Next Steps
After your first audit, you should:
- Review the scores and flagged sections
- Note any caching or hosting warnings
- Decide whether to optimize internally or request a deeper review
If the results are unclear or you want expert guidance, requesting a full audit can save significant time and guesswork.