Mochyon Pulse
| 开发者 | nabha |
|---|---|
| 更新时间 | 2026年5月14日 07:23 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Stop guessing why your WordPress site is slow.
Mochyon Pulse analyzes every layer of your site’s performance — from Google Core Web Vitals to individual plugin impact — and tells you exactly what to fix first. One click, no configuration, and (mostly) plain English results.
This is a diagnostic tool that gives you a clear, prioritized report that helps you take action.
How It Works
- Click “Run New Analysis” in your WordPress admin
- Pulse scans your site
- You’ll see a complete performance report with prioritized recommendations
- Core Web Vitals — your real-world LCP, INP, CLS, and TTFB scores from Google, with pass/warn/fail ratings
- Per-plugin performance impact — see exactly how much load time, JavaScript, CSS, and database queries each plugin adds to your page
- Asset inventory — every script and stylesheet on your page, sized and attributed to the plugin that loaded it
- Environment check — PHP version, CDN detection, compression support, and server configuration
- Plugin inventory — optimization gaps, redundant plugins, and missing essentials
- Plain English narrative — a written summary that explains what’s wrong, why it matters, and what to do about it
- Impact-prioritized findings — issues ranked by their actual effect on your Core Web Vitals, so you know what to fix first
- PDF reports — download a polished report to share with your developer, agency, or hosting provider
- Historical tracking — compare your baseline, previous scan, and latest results side by side to measure progress
- Site owners who know their site is slow but don’t know why
- Freelancers and agencies who need to explain performance issues to clients
- Developers who want a quick diagnostic before diving into optimization
- Anyone evaluating whether their plugins, hosting, or theme is the bottleneck
安装:
- Upload the
mochyon-pulsefolder to the/wp-content/plugins/directory, or install the plugin through the WordPress plugins screen. - Activate the plugin through the “Plugins” screen in WordPress.
- Navigate to the Pulse page in the admin menu.
- Click “Run New Analysis” to start your first performance scan.
常见问题:
Do I need to configure anything?
No. Pulse works immediately after activation — no API keys, no setup, no settings to tweak. Just click "Run New Analysis" and you’re done.
Will this plugin slow down my site?
No. Scans run in the background and only when you request them. Pulse never adds scripts, styles, or processing to your front-end pages. Your visitors are unaffected.
Does this plugin change anything on my site?
No. Mochyon Pulse is strictly a diagnostic tool. It reads and reports but never modifies your site’s code, database, or configuration.
Can I share the results?
Yes. You can download a PDF report from the dashboard that summarizes your performance analysis, findings, and per-plugin impact — ready to hand off to a team member or stakeholder.
How does the per-plugin impact analysis work?
Pulse makes instrumented requests to your site that measure how much execution time and how many database queries each plugin uses. It also attributes every JavaScript and CSS file to the plugin that loaded it. The result is a table showing exactly what each plugin costs your page load.
How often can I run a scan?
Scans can be re-run after roughly 30 seconds by default. Developers can customize that retry interval with the mochyon_pulse_retry_interval filter. Because scans take up room in your database, by default only up to 10 scans are retained, with your baseline (typically your first scan) always protected for comparison.
What data is sent externally?
When you run an analysis, your site’s URL is sent to the Mochyon API proxy at mochyon.com, which retrieves PageSpeed Insights and Chrome UX Report data from Google. No personal data is collected or stored. See our Privacy Policy and Terms of Service for details.
Can I run Pulse on a development or staging site?
Your site needs to be publicly accessible on the web. Pulse relies on Google’s PageSpeed Insights and Chrome UX Report APIs, which can only analyze URLs that are reachable from the public internet. Isolated local development environments, password-protected staging sites, and sites behind a VPN won’t work.
What are the requirements?
WordPress 6.0 or later and PHP 8.0 or later.
更新日志:
1.6.15
- Fixed settings link text displaying as "_settings" instead of "Settings"
- Improved reliability of OPCache detection (now a beta feature)
- Increased the default timeout for PageSpeed Insights requests from 120 to 180 seconds, reducing timeout failures on slower connections
- Fixed input sanitization warnings in backend profiler
- Added Plugin Check (PCP) to build validation
- Moved CI linting to local pre-commit and pre-push hooks
- First scans can now be named before they run, with a Baseline example placeholder
- Scan error details now persist and display on the Analyze page for scans with partial collector failures
- Shows which checks completed and which were skipped, with error messages for each
- Fixed environment collector crash caused by calling a renamed method on an external WordPress class
- Inline scripts now loaded via wp_add_inline_script() for better CSP compatibility
- PHPCS and PHPUnit checks now gate deployments in CI
- Fixed contradictory OPcache findings
- Per-strategy field data — CrUX metrics now split by mobile and desktop
- Unified dashboard and comparison view layouts
- Lab TTFB now computed from server response time plus network model
- Fixed OPcache interned strings display using configured directive
- Technical details now shown inline under each finding instead of in an accordion
- Colored badges and borders for high/medium/low impact finding tags
- Tested URL displayed in scan report subtitle
- Fixed Mobile/Desktop toggle flicker on page load
- Scan progress now shows spinners for each in-progress step and a shimmer animation with elapsed time
- Added technical details to findings that previously lacked diagnostic data
- Improved dashboard accessibility for keyboard and screen reader users
- New dedicated "New Scan" screen — scan trigger moved out of the Analyze page for a cleaner workflow
- Branded header bar with Mochyon Pulse logo across all admin screens
- Comparison basis toggle — switch the Change column between Previous and Baseline in scan history
- New environment findings: OPcache status, WP-Cron mode, autoloaded options size, and object cache detection
- Backend time column added to scan history table
- CrUX field data now confined to the Real-User Performance panel
- Fixed Mobile/Desktop toggle flicker on page load
- Fixed PDF report formatting: spacing, page breaks, and missing findings
- Fixed scan retention deleting one extra scan at the limit
- Fixed cancelled scans reverting to running on page reload
- Fixed false-positive compression detection
- Numerous UI polish improvements across dashboard, history, and comparison views
- Improved dashboard accessibility for keyboard and screen reader users, including sortable tables, device toggles, scan history controls, live status messages, and clearer focus targets
- Improved status and badge color contrast throughout the dashboard
- Added a warning banner when you're approaching or at your scan storage limit, with a link to adjust the setting
- Fixed text domain mismatch flagged by WordPress Plugin Check
- PDF report generation no longer requires an external CDN — the library is now bundled with the plugin
- Renamed the plugin from Mochyon Lightspeed to Mochyon Pulse
- Existing scan history, settings, and preferences are automatically migrated on upgrade
- Improved progress feedback during scans — shows elapsed time and context-specific hints while waiting for PageSpeed Insights
- Clearer error messages when a scan fails — plain-English explanations with collapsible technical details instead of raw API errors
- When only one strategy (mobile or desktop) fails, the scan now completes with the available data instead of showing a generic failure
- Increased the default timeout for PageSpeed Insights requests from 75 to 120 seconds, reducing timeout failures on slower connections
- Fixed output escaping and added missing translator comments for WordPress Plugin Check compliance
- Used POST requests for backend profiler to bypass page caches
- Mobile and desktop PageSpeed Insights requests now run concurrently, reducing total scan time
- Increased the default timeout for PageSpeed Insights requests from 60 to 75 seconds, reducing timeout failures on slower connections
- “Changes Since Last Scan” table now appears directly above the Performance Breakdown so you can see what moved before the current metrics
- Comparison table shows separate rows for mobile and desktop values where they differ (Core Web Vitals and Lighthouse Performance Score), so you can tell which device regressed or improved
- Mobile/Desktop toggle, performance score, and metric cards are now grouped in a shared panel so it’s clear which sections the toggle controls
- Removed the small stats row (Backend Time, DB Time, Peak Memory, Page Weight, PHP/CDN badges) from the main report and the scan-to-scan comparison view — the same information already appears in the Comparison table and Performance Breakdown below
- Comparison table now keeps historical rows visible when the latest scan is missing a metric (e.g. when PageSpeed Insights times out), showing “—” for the missing value instead of silently dropping the row
- Added Mobile/Desktop toggle on the dashboard and history pages — switch between mobile and desktop lab data like PageSpeed Insights, with your selection remembered across pages
- Added a Real-User Performance panel that shows CrUX field data from Chrome users above the toggle when available
- PDF reports now show three sections: Real-User Performance (when available), Mobile Performance, and Desktop Performance — each with its own score and metric table
- Developer briefs now include the same three-section layout in markdown
- Scan comparisons now show per-strategy deltas (mobile vs mobile, desktop vs desktop) with CrUX comparisons when both scans have field data
- Existing scans from before this update continue to display correctly
- Added a Page Weight column to Scan History showing total transfer size in KB with scan-over-scan deltas
- Added optional scan name input so you can label an analysis before it runs — placeholder rotates through common optimization examples for inspiration
- Darkened muted text throughout the dashboard (settings descriptions, history subtitles, metric labels, danger-zone hints) so it meets WCAG AAA contrast requirements
- Added visible keyboard focus rings on every button, link, input, and control
- Respects the system "Reduce motion" setting — animations and transitions stop when you ask them to
- Progress bar, status messages, and icon-only buttons now speak correctly to screen readers
- Fixed analysis freezing when you switch away from the Analyze screen and come back — scans now run in the background and pick up where they left off
- Multisite: plugin inventory now recognizes plugins activated network-wide, so network-wide caching, CDN, and image-optimization plugins are no longer flagged as missing on subsite scans
- Multisite: network-deactivating the plugin now unschedules pending scan jobs on every subsite, not just the current one
- Multisite: uninstalling the plugin now cleans up scan data, settings, and transients on every subsite in the network
- Added UTM tags to outbound links so visits driven by the plugin show up as a distinct source in Google Analytics
- Removed the stray underline from the Feedback email button on the Settings page
- Scan History now hides in-progress, failed, and cancelled scans so the list only shows results you can view and compare
- Added a review request banner on Pulse pages after your first completed scan
- Added a Feedback section on the Settings page for sending feedback directly to the Mochyon team
- Redesigned the Analyze page’s compared view: side-by-side Core Web Vitals metric cards with deltas, findings grouped into resolved / new / still present, stacked plugin impact tables, a site health summary showing backend, database, memory, and page weight changes, and a plain-English summary that explains what changed between the two scans
- Scan History now shows a green or red delta next to each Score, LCP, and TTFB value indicating the change from the previous scan; columns are left-aligned and widened so values line up cleanly down the list
- Added LCP and TTFB columns to the Scan History table
- Removed the always-redundant Status column from the Scan History table
- Replaced the Delete text button with a compact trash icon
- Auto-named scans ("Scan 1", "Scan 2", …) now keep their number when other scans are deleted; the number is assigned once at creation and can be edited via the rename button
- Removed the relative time suffix (e.g. "(4 minutes ago)") from the report date heading
- First stable release
- Fixed cancel button appearing on rate-limit errors when no scan is running
- Fixed admin page titles showing raw unicode escapes instead of proper characters
- Added i18n support with full translation template
- Added uninstall.php for clean data removal
- Added license.txt and readme.txt for WordPress.org compatibility
- Added FAQ about running on development/staging sites
- Fixed cancelled scans bypassing rate limiter, allowing unintended scan restarts
- Improved rate-limit message to show seconds when under a minute
- Added 30-second scan cooldown to prevent rapid-fire API requests
- SSL certificates are now verified on self-requests in production (disabled only in debug mode)
- Improved output escaping across all templates to follow WordPress coding standards
- Redesigned history and settings pages to match the dashboard design system
- Improved metrics context text readability
- Added collector timeout and collector name display during scan progress
- Fixed “View latest” link showing empty state instead of the latest scan
- Added PDF report download with client-side generation
- Added Lighthouse performance score to dashboard and comparison table
- Added performance score to PDF report
- Improved metric names to use plain English throughout
- Fixed scan retention pruning
- Added contextual “Get help” notice to dashboard and PDF report
- Various typography and layout polish
- Rewrote narrative generator with diagnosis and root-cause sentences
- Added site context to narrative (WooCommerce, page builder, plugin filtering)
- Added next-step sentence to narrative summary
- Multi-screen UI with separate Analyze, History, and Settings pages
- Submenu navigation in the WordPress admin
- Scan record baseline and comparison picker