The stages and methods of designing digital services to define the best solutions for interactions with the user.
× Filtered by: Performance
Filtered by:
Are the functionalities covered by local actions (client side) privileged rather than API exchanges ?
Do you use caching mechanisms to limit exchanges ?
Is the data fed back by the APIs really only the data that the application needs when it is requested ?
Do the libraries used allow you to take only the components that are actually useful ?
Are unused dependencies identified and removed ?
Couldn't the expected functionality be implemented with the native capabilities of the browser ?
Are all the technical equipment used by the service identified ?
Is the backward compatibility range defined ?
Don't the functionalities of the service go beyond user needs ?
Are the reference elements known, kept up to date, and made available to the entire project team ?
Do you inform users of the size constraints and accepted file format ?
Do uploads only allow the list of authorized file types ?
Are the images to be uploaded properly resized and converted to a thin client-side format before transfer ?
Are the exchanged files compressed ?
Is a CSS alternative available for an animation ?
Are the animations necessary, desired by the user ?
Are the fonts used not loaded only for a small number of objects ?
If printing, is an ink saving font installed ?
Do you limit the number of fonts loaded for the service ?
Are videos or animations outside the active area automatically paused / stopped ?
Is it really a user action that triggers the "play" ?
Are cartography objects, animations, videos presented in a static mode ?
Is the size of data stored on user device limited ?
