Best Practices - latif-essam/todo-app-oc-project GitHub Wiki
Analyzing best Practices results for the two Apps.
Todo-App
Device >> | Mobile | Desktop |
---|---|---|
Best Practices | 93 | 93 |
Passed audits | 15 | 15 |
Not applicable | 1 | 1 |
ScreenShots | ![]() |
![]() |
Issues
- fonts with
font-display: optional
are preloadedsolution:
should preload optional fonts to Prevent layout shifting and flashes of invisibile text.
Competitor todo-app
Device >> | Mobile | Desktop |
---|---|---|
Best Practices | 64% | 71% |
Passed audits | 11 | 12 |
Not applicable | 1 | 1 |
ScreenShots | ![]() |
![]() |
Issues
there are some issues with Trust and Safety like:
- the isn't using HTTPS, so we should use HTTPS calls instead of HTTP calls.
- There are some
JS
libraries with known security vulnerabilities ex:[email protected]
.
- Register an
unload
listener, this event does not fire reliably, and listening for it can prevent browser optimizations like the Back-Forward Cache.solution:
we can usepagehide
orvisibilitychange
events instead.
- There are some Serves images ( Icons ) with low resolution, images dimension should be greater than display size.