-
Notifications
You must be signed in to change notification settings - Fork 158
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
tracking: improve web performance and practices #268
Comments
This is the current lighthouse score https://saaskit.deno.dev/. The only score that is not 100 is the SEO score for mobile. This happens because of the size of tap area for some of the elements. Not sure if there is any way to solve this without changing the design of the page (spacing the elements). Also, not sure if we want to do it. |
I'm happy to increase these items' margins and possibly font size. |
This will bring the "Best Practices" score from 92 to 100. #268 <img width="753" alt="Screenshot 2023-07-19 at 21 01 16" src="https://github.com/denoland/saaskit/assets/8139585/aee1d398-3409-46da-a093-154af17ceb2a">
@iuioiua , just checking with you.. are you feeling that the app is slow? lighthouse doesn't seem to be complaining about it, as the performance score is still high, but: it is taking 1s for server response. there seems to be opportunities on improving server response time TTFB is also not ideal. neither on mobile nor on desktop. Should this be the result we are getting? Are you experiencing something similar? |
Yeah, I'm also noticing slowness. I suspect the sub-optimal DB logic to be the cause. Perhaps, fixing #400 is a step in the right direction. Also, ensuring that eventual consistency is being used where reasonable to do so. |
I'd be happy to hear any ideas on how performance can be improved across the site. |
The following have contributed to improving performance:
Thank you to those who helped! |
https://saaskit.deno.dev/ should have the best possible score on https://pagespeed.web.dev/
This is partly dependent on #260.
The text was updated successfully, but these errors were encountered: