Something not working right? We want to help. This guide shows you how to report issues in a way that gets you answers faster.
Before You Report
Try these quick fixes first. They solve most problems:
Clear Your Cache
- Clear your browser cache (Ctrl+Shift+Delete on most browsers)
- If using a caching plugin, clear the WordPress cache
- Try again
Check for Conflicts
- Temporarily deactivate other plugins
- Test SpeedTest Pro
- If it works, reactivate plugins one by one to find the conflict
Update Everything
Make sure you’re running the latest:
- WordPress version
- SpeedTest Pro version
- PHP version (7.4 or higher recommended)
Check Console for Errors
- Open your browser’s developer tools (F12)
- Click the Console tab
- Look for red error messages
- Note any that mention SpeedTest Pro
What to Include in Your Report
The more details you provide, the faster we can help. Include:
Basic Information
- WordPress version: (Find in Dashboard > Updates)
- SpeedTest Pro version: (Find in Plugins list)
- PHP version: (Find in Speedtest Pro > Server Information)
- Browser and version: (e.g., Chrome 120)
Problem Description
- What were you trying to do?
- What happened instead?
- Can you reproduce it? (Does it happen every time?)
- When did it start? (After an update? Randomly?)
Error Messages
Copy the exact error text if you see one. Screenshots help too.
Steps to Reproduce
List the exact steps to trigger the problem:
- Go to [specific page]
- Click [specific button]
- See error
What You’ve Already Tried
Mention any troubleshooting steps you’ve taken. This saves time going back and forth.
Where to Report Issues
WordPress.org Support Forum
For general help and questions:
- Go to wordpress.org/support/plugin/speedtest-pro
- Click “Create Topic”
- Fill in your details using the template above
- Submit and wait for a response
Support forum posts are public, so don’t include sensitive information like API keys or passwords.
Direct Email
For security issues or private matters:
- Contact: support@ianb153.sg-host.com
- Include “SpeedTest Pro” in the subject line
Using the Built-In Bug Reporter
SpeedTest Pro includes a bug reporting feature that automatically collects helpful information.
How to Use It
- Go to any SpeedTest Pro page in your admin panel
- Look for the “Report Bug” link (usually in the footer or help menu)
- Click it to open the bug report form
- Describe your issue
- The form automatically includes system information
- Submit the report
This is the fastest way to get help because it includes all the technical details we need.
Common Issues and Solutions
Before reporting, check if your issue is listed here:
“No API key available” Error
Problem: SSL testing shows an API key error.
Solution: This usually means plugin activation didn’t complete properly. Deactivate and reactivate SpeedTest Pro.
PageSpeed Tests Keep Failing
Problem: Tests time out or show errors.
Solutions:
- Add your Google PageSpeed API key in Settings
- Check if your site is accessible from external sources
- Try testing a simpler page
UptimeRobot Monitors Not Working
Problem: Can’t create monitors or data not showing.
Solutions:
- Verify your API key is a “Main API Key” (not Read-Only)
- Check if monitors already exist in your UptimeRobot dashboard
- Delete existing WPSpeedTestPro monitors and try again
Tests Running Very Slowly
Problem: Benchmarks take forever or time out.
Solutions:
- Your server might be under heavy load
- Try during off-peak hours
- Check if other plugins are conflicting
Results Not Displaying
Problem: Tests complete but results don’t show.
Solutions:
- Clear browser cache
- Disable browser extensions
- Try a different browser
- Check browser console for JavaScript errors
Settings Not Saving
Problem: Changes to settings don’t persist.
Solutions:
- Check file permissions on your WordPress installation
- Look for security plugins blocking POST requests
- Verify you have admin privileges
What Happens After You Report
- You’ll get a confirmation that we received your report
- We review the details and may ask follow-up questions
- We investigate the issue and try to reproduce it
- You’ll get an update with a solution or workaround
- If it’s a bug, it gets added to our fix list
Response times vary, but we aim to acknowledge reports within 48 hours.
Tips for Faster Support
Be Specific
“It doesn’t work” is hard to debug. “When I click Run Test on the SSL page, nothing happens and I see this error in the console…” is actionable.
Include Screenshots
A picture is worth a thousand words. Screenshots help us see exactly what you’re seeing.
Check Existing Issues
Someone might have already reported your problem. Search the support forum or GitHub issues first.
Stay Patient
We’re a small team and get a lot of reports. We read everything, but responses take time.
Follow Up if Needed
If you don’t hear back in a week, it’s okay to bump your thread. We might have missed it.
Security Vulnerabilities
If you’ve found a security issue, please:
- Don’t post it publicly (no support forums or GitHub issues)
- Email us directly at support@ianb153.sg-host.com
- Use “Security Issue” in the subject line
- Describe the vulnerability and how to reproduce it
We take security seriously and will respond as quickly as possible.
Feature Requests
Have an idea for SpeedTest Pro? We love hearing them.
How to Submit Feature Requests
- WordPress.org forum – Tag your post with “feature request”
- GitHub – Open an issue with the “enhancement” label
- Email – Send your idea to support@ianb153.sg-host.com
What Makes a Good Feature Request
- Clear description of what you want
- Use case explaining why it’s useful
- Examples from other tools if applicable
- Acknowledgment that it might not happen immediately
We can’t implement every request, but we consider all of them when planning updates.