We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am opening this issue so I can link to it from the README. There's already a lot of 'informational' stuff in the repository.
I tested cState with Pingdom Tools and web.dev (which uses Google's Lighthouse, I believe).
cState got top notch scores all throughout.
This is in part thanks to the good work the people at Netlify are doing.
On the other hand, cState makes few requests (one for the HTML which includes the CSS and JS), another for the logo, and another for the favicon.
When you are making a status page, looks are rarely the thing that matters. Ease of use and speed are much more important.
Feel free to reply with any more information you have on speed, what might need to be changed, etc.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am opening this issue so I can link to it from the README. There's already a lot of 'informational' stuff in the repository.
I tested cState with Pingdom Tools and web.dev (which uses Google's Lighthouse, I believe).
cState got top notch scores all throughout.
This is in part thanks to the good work the people at Netlify are doing.
On the other hand, cState makes few requests (one for the HTML which includes the CSS and JS), another for the logo, and another for the favicon.
When you are making a status page, looks are rarely the thing that matters. Ease of use and speed are much more important.
Feel free to reply with any more information you have on speed, what might need to be changed, etc.
The text was updated successfully, but these errors were encountered: