Trust is easier when you can see the rules. If you use PerfMonitoring to research performance monitoring tools, you should know how the site approaches privacy, editorial decisions, commercial relationships, and the limits of a static research site. This page explains those choices in plain English so you can judge the material with the same care you would apply to a monitoring dashboard.
Commercial disclosure in plain English
You should be able to understand how a research site works without reading between the lines. The sections below describe the current static build and the editorial practices that make its content easier to evaluate. They are intentionally specific about what is present today and cautious about features that may be added later.
Current commercial status
The uploaded build contains no affiliate links. Vendor buttons point to official vendor websites, and software logos are loaded from a third-party icon CDN. A link to a vendor does not, by itself, mean the vendor paid for inclusion.
The practical test is whether the statement still matches the deployed website. If hosting, tracking, commercial relationships, data collection or editorial processes change, the corresponding policy should change too. Keeping policy text synchronized with implementation is more useful than writing broad promises that cannot be verified from the site.
How future affiliate relationships should be handled
If affiliate links, sponsored placements or other commercial relationships are added, they should be labeled where the relationship can affect how a reader interprets the page. The disclosure should explain the relationship in plain language and be visible without forcing the reader to infer it from a URL.
The practical test is whether the statement still matches the deployed website. If hosting, tracking, commercial relationships, data collection or editorial processes change, the corresponding policy should change too. Keeping policy text synchronized with implementation is more useful than writing broad promises that cannot be verified from the site.
Editorial separation
Commercial relationships should not change technical definitions, comparison criteria or factual product descriptions. Rankings and recommendations should be based on stated evaluation criteria and should disclose material conflicts when they exist.
The practical test is whether the statement still matches the deployed website. If hosting, tracking, commercial relationships, data collection or editorial processes change, the corresponding policy should change too. Keeping policy text synchronized with implementation is more useful than writing broad promises that cannot be verified from the site.
Vendor trademarks and logos
Vendor names and marks belong to their respective owners. Logo use should follow applicable brand guidance. The project README specifically recommends verifying logo and trademark usage before production deployment.
The practical test is whether the statement still matches the deployed website. If hosting, tracking, commercial relationships, data collection or editorial processes change, the corresponding policy should change too. Keeping policy text synchronized with implementation is more useful than writing broad promises that cannot be verified from the site.
Pricing and offers
This build intentionally avoids fabricated price, offer, rating and review schema. When pricing is discussed, readers should be sent to current vendor sources because plan names, quotas and commercial terms can change.
The practical test is whether the statement still matches the deployed website. If hosting, tracking, commercial relationships, data collection or editorial processes change, the corresponding policy should change too. Keeping policy text synchronized with implementation is more useful than writing broad promises that cannot be verified from the site.
Frequently asked questions about Commercial disclosure
Why does PerfMonitoring publish a commercial disclosure?
Because transparency changes how you should interpret research. Knowing the site’s current data practices, sourcing approach and commercial status helps you judge recommendations with appropriate context.
Can this commercial disclosure change?
Yes. It should change when the site’s implementation or editorial/commercial practices change. A static policy that no longer describes the deployed site is less useful than a shorter policy that is accurate.
Where should you verify product information?
Use vendor documentation for current capabilities, pricing, limits, retention and support. Use standards and primary technical documentation for concepts such as HTTP, OpenTelemetry and Web Vitals.
Conclusion
The purpose of this page is to make the site easier to evaluate, not to hide important conditions in fine print. Use it together with the editorial and disclosure pages, and verify changing product details at their primary source before making a purchase or production decision.
Sources and further reading for Commercial disclosure
Use primary sources for definitions and current product capabilities. The references below were reviewed for this content update.