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.

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

Ryte Site Health check: improve response speed #14387

Open
2 tasks done
afercia opened this issue Feb 17, 2020 · 5 comments
Open
2 tasks done

Ryte Site Health check: improve response speed #14387

afercia opened this issue Feb 17, 2020 · 5 comments

Comments

@afercia
Copy link
Contributor

afercia commented Feb 17, 2020

Product owner: @JessieHenkes
Roadmap issue: Yoast/roadmap#102

  • I've read and understood the contribution guidelines.
  • I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened.

The Ryte Site Health check calls the Ryte API thus adding some delay to the Site Health page load.

There are already plans to improve this. Creating this issue to keep track of the progress.

Please describe what you expected to happen and why.

I expected the Site Health page to load immediately without any delay.

How can we reproduce this behavior?

  • test the feature/site-health branch or trunk then the branch will be merged
  • go to the Site Health page by clicking the "Site Health" link in the WordPress admin menu
  • notice the page doesn't load immediately
  • after the page loads, navigate to another page
  • click again the "Site Health" link in the WordPress admin menu
  • repeat this a few times and notice that depending on network conditions / random API response speed, the delay of the page load can be even more noticeable

Used versions

  • WordPress version: 5.3.2
  • Yoast SEO version: 13.0-RC2 on the feature/site-health branch
@afercia
Copy link
Contributor Author

afercia commented Mar 10, 2020

@JessieHenkes not sure this issue should be in the Queue, as there are no actionable items so far. This requires improvements on the Ryte side or something at a server configuration level.

@JessieHenkes
Copy link
Contributor

@afercia can you address this one to Ryte (do you have contacts?) and close this issue?

@afercia
Copy link
Contributor Author

afercia commented Mar 12, 2020

@JessieHenkes I don't have contacts at Ryte. @jdevalk knows more about the plans for the Ryte response.

@jdevalk
Copy link
Contributor

jdevalk commented Mar 12, 2020

I’ll pick this one up.

@karlijnbok
Copy link
Contributor

@jdevalk Can this issue be closed?

@karlijnbok karlijnbok moved this from Queue to Needs Action in Team Plugin #3 Apr 28, 2020
@IreneStr IreneStr removed this from Needs Action in Team Plugin #3 May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants