cirvgreen

Know your Core Web Vitals without leaving WordPress. Cirv Pulse monitors your Lighthouse performance score and tells you exactly what to fix.
Google uses Core Web Vitals as a ranking factor. If your LCP is slow, your CLS is high, or your INP is poor — you’re losing rankings and traffic. Cirv Pulse puts these numbers on your WordPress dashboard with clear pass/fail indicators and fix-it recommendations.
<h4>Why Core Web Vitals Matter</h4>
<ul>
<li>Google ranking factor – CWV directly impacts search rankings since 2021</li>
<li>User experience – Slow sites lose 53% of mobile visitors (Google data)</li>
<li>Conversion rates – Every 100ms of latency costs 1% in conversions</li>
<li>Competitive edge – Most WordPress sites fail CWV (your competitors included)</li>
</ul>
<h4>Free Features</h4>
One-Click Performance Scan 
Enter any URL and get a complete Core Web Vitals report in 10-30 seconds. No account needed. Powered by the free Google PageSpeed Insights API.
5 Key Metrics Tracked 
* LCP (Largest Contentful Paint) — loading performance 
* INP (Interaction to Next Paint) — interactivity responsiveness 
* CLS (Cumulative Layout Shift) — visual stability 
* FCP (First Contentful Paint) — perceived load speed 
* TTFB (Time to First Byte) — server response time
Color-Coded Score Dashboard 
Green (Good), Yellow (Needs Improvement), Red (Poor) — see your performance status at a glance with an overall 0-100 score.
Smart Recommendations 
Rule-based performance engine analyzes your scores and generates specific, actionable fixes. Not generic advice — recommendations tailored to your actual metrics.
Scan History 
Last 10 scans stored so you can track improvements over time.
<h4>Perfect For</h4>
<ul>
<li>SEO professionals – Monitor client sites from their WordPress dashboards</li>
<li>Agencies – Deliver performance reports without external tools</li>
<li>E-commerce – Track product page performance across your catalog</li>
<li>Bloggers – Ensure fast load times for better rankings</li>
<li>Anyone who wants to know their Lighthouse score without opening Chrome DevTools</li>
</ul>
<h4>Works With Everything</h4>
Cirv Pulse works with any WordPress theme, page builder, or hosting provider. It scans your live pages via Google’s API — compatible with Elementor, Divi, Gutenberg, WPBakery, and more.
<h3>Additional Info</h3>
Privacy & GDPR Compliance: 
Cirv Pulse sends your page URL to Google PageSpeed Insights API for analysis. No personal data is collected or stored by the plugin. Google’s privacy policy applies to the API call. No tracking cookies are set.
Related Plugins: 
* Cirv Box – Schema.org structured data for better Google rankings 
* Cirv Guard – WCAG accessibility compliance scanning 
* More Cirvgreen plugins coming soon
Support & Documentation: 
* Built-in help in plugin settings 
* Online documentation: https://cirvgreen.com/docs/cirv-pulse 
* Support forum: WordPress.org support forum 
* Email: support@cirvgreen.com
<h3>Third-Party Service Usage</h3>
This plugin uses the Google PageSpeed Insights API to analyze web page performance.
<ul>
<li>Service: Google PageSpeed Insights API v5</li>
<li>URL: https://www.googleapis.com/pagespeedonline/v5/runPagespeed</li>
<li>Data sent: The URL you enter for scanning</li>
<li>When: Only when you manually trigger a scan</li>
<li>Privacy policy: https://policies.google.com/privacy</li>
<li>Terms of service: https://developers.google.com/terms</li>
</ul>
No other third-party services are used. An optional API key from Google Cloud Console can be configured to increase rate limits.

Cirv Pulse

Real-time Core Web Vitals monitoring inside WordPress. Track LCP, INP, CLS and get actionable performance recommendations without leaving your dashboa …

dimedaughter

A simple plugin that eliminates render blocking CSS using current (at the time of writing) best-practices, speeding up your site and improving your SEO in seconds.
Directions for use:
<ul>
<li>Install</li>
<li>Activate</li>
<li>That’s it</li>
</ul>

Simple Eliminate Render Blocking CSS

Eliminates render blocking CSS using current (at the time of writing) best-practices

Cirv Pulse vs Simple Eliminate Render Blocking CSS