Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Stats: Site Performance mismatch with Stats #101071

Open
dzver opened this issue Mar 10, 2025 · 2 comments
Open

Stats: Site Performance mismatch with Stats #101071

dzver opened this issue Mar 10, 2025 · 2 comments
Labels
[Feature Group] Site Settings & Tools Settings and tools for managing and configuring your site. [Feature] Site Performance Features related to the speed and performance of your site. [Feature] Stats Everything related to our analytics product at /stats/ Needs triage Ticket needs to be triaged [Pri] Low Address when resources are available. [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@dzver
Copy link
Member

dzver commented Mar 10, 2025 •
edited
Loading

Context and steps to reproduce

The number of visits between Site Performance and Stats is vastly different. Why is that?

Image Image

The visual difference helps obscure the data difference but ideally, the numbers should either match, or we should specify what the numbers mean.

Site owner impact

Fewer than 20% of the total website/platform users

Severity

Moderate

What other impact(s) does this issue have?

No response

If a workaround is available, please outline it here.

No response

Platform

Simple
@dzver dzver added [Feature Group] Site Settings & Tools Settings and tools for managing and configuring your site. [Feature] Site Performance Features related to the speed and performance of your site. [Feature] Stats Everything related to our analytics product at /stats/ [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Mar 10, 2025
@github-actions github-actions bot added the [Pri] Low Address when resources are available. label Mar 10, 2025
@github-actions GitHub Actions
Copy link

This issue could use some more labels, to help prioritize and categorize our work. Could you please add at least a [Type], a [Feature], and a [Pri] label?

@supernovia
Copy link
Contributor

📌 REPRODUCTION RESULTS

  • Tested on Atomic – Could not replicate

📌 ACTIONS

  • Requested author feedback

📌 Message to Author
@dzver can you share where I can access the LCP view that you have there?

@supernovia supernovia moved this from Needs Triage to In Triage in Automattic Prioritization: The One Board ™ Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[Feature Group] Site Settings & Tools Settings and tools for managing and configuring your site. [Feature] Site Performance Features related to the speed and performance of your site. [Feature] Stats Everything related to our analytics product at /stats/ Needs triage Ticket needs to be triaged [Pri] Low Address when resources are available. [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Automattic Prioritization: The One Board ™
Status: In Triage
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dzver @supernovia