Archive
- Set goals based on potential impact considerations
- Remove unnecessary or redundant information
- Modularize bandwidth-heavy components within projects
- Tree shaking should be used to remove unnecessary code
- Redundancy and duplication in code should be avoided
- Third-party services should be assessed as first parties
- Code must follow good semantic practices
- Render blocking should be resolved
- Information to help understand the usefulness of a page should exist
- Forms must validate for errors, accounting for tooling requirements
- Metadata is structured for machine readability
- Sustainable CSS user preference media queries are used
- Layouts work across devices and requirements
- Use beneficial JavaScript and its APIs
- Ensure that your scripts are secure
- Dependencies are appropriately used and maintained
- Include expected and beneficial files
- Avoid using deprecated, proprietary, or outdated code
- Use the most efficient solution to implement your service
- Use the latest stable language version
- Take advantage of native features and functionality
- Run fewer, simpler queries as possible