Check page quality, speed, and security reports
Run read-only checks and turn the findings into specific follow-up tasks.
Before you start
- A verified connection to a practice site.
- Administrator access for performance/security reports.
- EMCP Pro and enabled tools for the SEO/accessibility toolkit.
Let’s do this, step by step.
Step 01
Check the integration tools
Open Setup → Tools → WordPress → Performance & Security. For Pro audits, SEO is on WordPress and Accessibility is on Elementor; select Elementor first. Inspect dependencies and both read/write switches. Enable the actions for this task, choose Save changes, then reconnect.
Open EMCP Tools, then Setup, then Tools, then WordPress, then Performance & Security. For Pro audits, SEO is on WordPress and Accessibility is on Elementor; select Elementor first. Inspect dependencies and both read and write switches. Enable the actions for this task, choose Save changes, then reconnect.
Step 02
Choose the target and scope
Select the exact page and request reports without automatic fixes.
Start with inspection. We want to understand the findings before changing design, files, or site settings.
Step 03
Read performance findings
Run the Performance Analyzer and inspect server, database, page, and asset findings.
This report does not run a real browser or measure Core Web Vitals. If its page fetch is blocked, use the available server findings and note the missing part.
Step 04
Review accessibility proposals
Run the page accessibility check. Preview proposed contrast and image-description fixes before applying them.
Automatic checks catch some issues. Verify image descriptions against the actual images, and check keyboard access and the rendered page yourself.
Step 05
Review security findings
Run the read-only scanner and inspect flagged paths, scope limits, and skipped checks.
A flagged pattern needs review; it is not automatically malware. A clean report is not a guarantee. Do not delete files just because the score is low.
Step 06
Fix one confirmed issue
Choose one understood issue, make a bounded change, then repeat the affected check and inspect the page.
Keep the before and after results. If the report was partial, say so instead of treating it as a complete site review.
Step 07
Read plugin status reports
Where they are installed, read LiteSpeed Cache status, Wordfence status, firewall and scan-status, and Site Kit module state. All three are reads; Wordfence and Site Kit have no write tool. Note what each report cannot see, such as Google reports or file paths.
Plugin reports add context: whether the cache is on, when the last security scan ran, which Google services are set up. Treat them as reads and note their limits before acting on them.
You’re done when…
You have a prioritized list of verified findings and know each report's limits.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
A brief becomes a real page.