Closed throwaway-d closed 12 months ago
Thanks for the report. We are aware of the pagespeed.web.dev reports and are working through their recommendations. Some small enhancements will be included in the upcoming Retype v3.1 release. Others will take time to implement as they would involve a larger investment to implement.
Overall, the suggestions in the reports are minor issues and the metrics will improve over time with each new release of Retype.
For now, I'm going to close this issue. If there are specific issues that you feel need to be addressed, please feel free to create a new dedicated issue to that topic.
One thing I noted in the report was the following item:
Serve static assets with an efficient cache policy
The cache policy is a server side (hosting) configuration and is not something Retype itself can adjust. The question was raised previously, see https://github.com/retypeapp/retype/issues/563#issuecomment-1574151871.
We moved the retype.com hosting away from GitHub Page and to Netlify for this very reason.
The cache policy is a server side (hosting) configuration and is not something Retype itself can adjust. The question was raised previously, see https://github.com/retypeapp/retype/issues/563#issuecomment-1574151871.
The Rimgo owner also has mentioned that I need to report those speed suggestions to Codeberg Pages.
https://codeberg.org/rimgo/docs/issues/7 I've put Rimgo website through a website checker called PageSpeed Insights for some performance and accessibility suggestions to improve Rimgo website. I contacted the owner of Rimgo website about those suggestions. But the owner told me that all HTML is written by Retype, the owner didn't have any control over generated HTML.
So I think I should report the suggestions to Retype instead, right?
Here are the accessibility suggestions: https://pagespeed.web.dev/analysis/https-rimgo-codeberg-page-docs/ojicpsz30p?form_factor=mobile