WSG Report and Statement Tool

The information that you provide below will generate a sustainability report that you can download and further refine.

None of the fields are required, and none of the information you enter is stored outside your web browser.

Choose a document type Sustainability Report (Detailed) Sustainability Statement (Simple)

Basic information
In this section you can provide the minimal set of information recommended for your sustainability report. This includes information about your organization, the standards you applied, and your contact information for feedback.

About your report

Name of your organization (Example: "Example Inc.")

Name of your website or application (Example: "Example website" or "Example app version 1.1")

Address of your product or service (Example: "https://example.com")

Application of sustainability

Sustainability best practices

W3C Web Sustainability Guidelines (WSG)

Other (Show/Hide)

General Policy Framework for the Ecodesign of Digital Services (ARCEP)

Handbook of Sustainable Design of Digital Services (GR491)

United Nations Sustainable Development Goals (SDGs)

Other

Sustainability standards

Global Reporting Initiative (GRI)

Software Carbon Intensity (SCI)

ISO Environment and Sustainability Family (ISO)

Other (Show/Hide)

Automated Source Code Resource Sustainability Measure (ASCRSM)

Other

Sustainability legislation

Corporate Sustainability Reporting Directive (CSRD)

Ecodesign for Sustainable Products Regulation (ESPR)

Other (Show/Hide)

Green Transition Directive (EU/2024/825)

Energy Efficiency Directive (EU/2023/1791)

Visant à réduire l'empreinte environnementale du numérique (REEN)

Other

Conformance status

Fully conformant: the content fully conforms to the above without any exceptions.

Partially conformant: some parts of the content do not fully conform to the above.

Non conformant: the content does not conform to the above.

Not assessed: the content has not been evaluated or the evaluation results are not available.

Additional sustainability considerations

Further considerations that go beyond the scope of what is mentioned above.

Greenwashing: the content does not contain any greenwashing or claims that cannot be reinforced with evidence without any exceptions. Evidence for claims should be provided in the above box if required.

Feedback options

Phone (Example: "+12 34 567 89 00")

E-mail (Example: "sustainability@example.com")

Address (Example: "PO Box 1, 234 Example Ville")

Other contact options (Example: "@YourName" on social media)

Typical duration for response (Example: "5 business days")

Date of publication

Publication date of this sustainability report

Web Sustainability Guidelines
In this section you can describe the efforts your organization takes to ensure sustainability. This helps users to understand your sincerity and the validity of the claims you make in your sustainability report.

User Experience Design

2.1 - Identify, assess, disclose, review, and mitigate sustainability impacts

Success Criteria - Impact analysis

Conformance status:

Observations:

Success Criteria - External impact

Conformance status:

Observations:

2.2 - Understand user requirements or constraints

Success Criteria - Audience evaluation

Conformance status:

Observations:

2.3 - Integrate sustainability into every stage of the ideation process

Success Criteria - Sustainable brand development

Conformance status:

Observations:

Success Criteria - Wireframes and prototypes

Conformance status:

Observations:

Success Criteria - Participation and testing

Conformance status:

Observations:

Success Criteria - Environmental ideation

Conformance status:

Observations:

2.4 - Design efficient and streamlined user journeys

Success Criteria - Efficient paths

Conformance status:

Observations:

Success Criteria - Patterns for efficiency

Conformance status:

Observations:

Success Criteria - Content discovery

Conformance status:

Observations:

2.5 - Design to assist and not to distract

Success Criteria - Respect user attention

Conformance status:

Observations:

Success Criteria - Distraction-free design

Conformance status:

Observations:

Success Criteria - Remove engagement traps

Conformance status:

Observations:

2.6 - Avoid being manipulative or deceptive

Success Criteria - Deceptive design patterns

Conformance status:

Observations:

Success Criteria - Advertisements

Conformance status:

Observations:

Success Criteria - Analytics and tracking

Conformance status:

Observations:

Success Criteria - Search Engine Optimization

Conformance status:

Observations:

2.7 - Make deliverables understandable and reusable

Success Criteria - Deliverables reusability

Conformance status:

Observations:

Success Criteria - Deliverables documentation

Conformance status:

Observations:

Success Criteria - Deliverables readability

Conformance status:

Observations:

2.8 - Use a design system for interface consistency

Success Criteria - Design system

Conformance status:

Observations:

2.9 - Optimize media to reduce resource use

Success Criteria - Need for media

Conformance status:

Observations:

Success Criteria - Optimized media

Conformance status:

Observations:

Success Criteria - Lazy loading

Conformance status:

Observations:

Success Criteria - User-controlled media

Conformance status:

Observations:

Success Criteria - Media management and use

Conformance status:

Observations:

2.10 - Ensure animation is proportionate and easy to control

Success Criteria - Need for animation

Conformance status:

Observations:

Success Criteria - Avoiding overburdening

Conformance status:

Observations:

Success Criteria - Control animation

Conformance status:

Observations:

Success Criteria - Efficient animation

Conformance status:

Observations:

2.11 - Use optimized web typography

Success Criteria - Pre-installed typefaces

Conformance status:

Observations:

Success Criteria - Web font optimization

Conformance status:

Observations:

Success Criteria - Web font subsetting

Conformance status:

Observations:

2.12 - Avoid unwanted notifications

Success Criteria - Need for notification

Conformance status:

Observations:

Success Criteria - Notification settings

Conformance status:

Observations:

2.13 - Reduce the impact of downloadable and physical documents

Success Criteria - Printed documents

Conformance status:

Observations:

Success Criteria - Optimized documents

Conformance status:

Observations:

Success Criteria - Optimized delivery

Conformance status:

Observations:

Success Criteria - Labels and choice

Conformance status:

Observations:

2.14 - Involve users early in the project

Success Criteria - Early user testing

Conformance status:

Observations:

2.15 - Audit and test for bugs or issues requiring resolution

Success Criteria - Ongoing evaluation

Conformance status:

Observations:

Success Criteria - Automated tests

Conformance status:

Observations:

Success Criteria - Performance testing

Conformance status:

Observations:

2.16 - Validate usability through testing and real-world usage

Success Criteria - Usage changes

Conformance status:

Observations:

Success Criteria - Usability testing

Conformance status:

Observations:

2.17 - Provide cross-platform compatibility support

Success Criteria - Compatibility documentation

Conformance status:

Observations:

Success Criteria - Maintaining compatibility

Conformance status:

Observations:

Success Criteria - User constraints

Conformance status:

Observations:

Web Development

3.1 - Set goals based on performance and energy impact

Success Criteria - Performance goals

Conformance status:

Observations:

Success Criteria - Energy intensity

Conformance status:

Observations:

3.2 - Minify and remove unused code

Success Criteria - Minified code

Conformance status:

Observations:

Success Criteria - Remove redundancy

Conformance status:

Observations:

3.3 - Modularize bandwidth-heavy components

Success Criteria - Code splitting

Conformance status:

Observations:

3.4 - Avoid redundancy and duplication in code

Success Criteria - Remove or simplify

Conformance status:

Observations:

Success Criteria - Iteration over recreation

Conformance status:

Observations:

Success Criteria - Organize code arrangement

Conformance status:

Observations:

3.5 - Treat third parties the same as first parties

Success Criteria - Assess and reduce

Conformance status:

Observations:

Success Criteria - Third-party implementation

Conformance status:

Observations:

Success Criteria - Self-hosting

Conformance status:

Observations:

Success Criteria - Third-party preferences

Conformance status:

Observations:

3.6 - Ensure code follows good semantic practices

Success Criteria - Semantic code

Conformance status:

Observations:

Success Criteria - Optional features

Conformance status:

Observations:

Success Criteria - Non-standard code

Conformance status:

Observations:

Success Criteria - Custom code

Conformance status:

Observations:

3.7 - Defer the loading of non-critical resources

Success Criteria - Asynchronous code

Conformance status:

Observations:

Success Criteria - Optimized loading

Conformance status:

Observations:

3.8 - Structure metadata for machine readability

Success Criteria - Required elements

Conformance status:

Observations:

Success Criteria - Meta tags

Conformance status:

Observations:

Success Criteria - Structured data

Conformance status:

Observations:

3.9 - Use media queries that support sustainability goals

Success Criteria - Media and preference queries

Conformance status:

Observations:

3.10 - Ensure layouts work for different devices and requirements

Success Criteria - Device-adaptable

Conformance status:

Observations:

Success Criteria - Progressive enhancement

Conformance status:

Observations:

Success Criteria - Carbon-aware design

Conformance status:

Observations:

Success Criteria - Alternative browsing

Conformance status:

Observations:

3.11 - Use sustainable JavaScript and APIs

Success Criteria - Sustainable JavaScript

Conformance status:

Observations:

Success Criteria - Energy-relevant APIs

Conformance status:

Observations:

Success Criteria - API requests

Conformance status:

Observations:

3.12 - Use dependencies sparingly and maintain them

Success Criteria - Dependency management

Conformance status:

Observations:

Success Criteria - Dependency necessity

Conformance status:

Observations:

Success Criteria - Dependency updates

Conformance status:

Observations:

3.13 - Include expected and beneficial files

Success Criteria - Expected files

Conformance status:

Observations:

Success Criteria - Beneficial files

Conformance status:

Observations:

3.14 - Use the most efficient solution for your service

Success Criteria - Appropriate Implementation

Conformance status:

Observations:

Success Criteria - Optimized methodology

Conformance status:

Observations:

Success Criteria - Static over dynamic

Conformance status:

Observations:

Success Criteria - Extensions and plugins

Conformance status:

Observations:

Success Criteria - Interface components

Conformance status:

Observations:

3.15 - Use the latest stable language version

Success Criteria - Versioning

Conformance status:

Observations:

Success Criteria - Language choice

Conformance status:

Observations:

3.16 - Reduce the number and complexity of database queries

Success Criteria - Efficient database querying

Conformance status:

Observations:

Success Criteria - Reuse of retrieved data

Conformance status:

Observations:

Success Criteria - Data minimization in queries

Conformance status:

Observations:

Success Criteria - Data lifecycle controls

Conformance status:

Observations:

Hosting, Infrastructure, and Systems

4.1 - Use sustainable hosting

Success Criteria - Provider selection

Conformance status:

Observations:

Success Criteria - Efficient operation

Conformance status:

Observations:

Success Criteria - Equipment longevity

Conformance status:

Observations:

Success Criteria - Low-carbon electricity

Conformance status:

Observations:

Success Criteria - Remaining emissions

Conformance status:

Observations:

Success Criteria - Domain names

Conformance status:

Observations:

4.2 - Optimize caching and support offline access

Success Criteria - Caching resources

Conformance status:

Observations:

Success Criteria - Offline access

Conformance status:

Observations:

4.3 - Reduce data transfer with compression

Success Criteria - Server-side compression

Conformance status:

Observations:

Success Criteria - Media compression

Conformance status:

Observations:

4.4 - Setup necessary error pages and redirection links

Success Criteria - Error pages

Conformance status:

Observations:

Success Criteria - Redirection

Conformance status:

Observations:

4.5 - Avoid maintaining unnecessary virtualized environments or containers

Success Criteria - Unused environments

Conformance status:

Observations:

4.6 - Use automation wisely

Success Criteria - Task automation

Conformance status:

Observations:

Success Criteria - Necessary tasks

Conformance status:

Observations:

Success Criteria - Automated scaling

Conformance status:

Observations:

Success Criteria - Suspicious activity management

Conformance status:

Observations:

4.7 - Define the frequency of data refreshes

Success Criteria - Refresh frequency

Conformance status:

Observations:

4.8 - Back up critical data at routine intervals

Success Criteria - Data backups

Conformance status:

Observations:

4.9 - Assess the impact and requirements of data processing

Success Criteria - Carbon shifting

Conformance status:

Observations:

Success Criteria - Protocol efficiency

Conformance status:

Observations:

Success Criteria - Event-driven architecture

Conformance status:

Observations:

Success Criteria - Data processing efficiency

Conformance status:

Observations:

Success Criteria - Efficient location

Conformance status:

Observations:

4.10 - Use Content Delivery Networks (CDNs) when beneficial

Success Criteria - Global CDNs

Conformance status:

Observations:

Success Criteria - Sustainability commitment

Conformance status:

Observations:

Success Criteria - Inappropriate resources

Conformance status:

Observations:

4.11 - Ensure infrastructure fits project requirements

Success Criteria - Lowest requirements

Conformance status:

Observations:

4.12 - Store data according to the needs of your users

Success Criteria - Remove unused data

Conformance status:

Observations:

Success Criteria - Lifecycle management

Conformance status:

Observations:

Success Criteria - Efficient storage

Conformance status:

Observations:

Success Criteria - Optimized logging

Conformance status:

Observations:

Success Criteria - Asset downloads

Conformance status:

Observations:

Business Strategy and Product Management

5.1 - Have an ethical and sustainable product strategy

Success Criteria - Public documents

Conformance status:

Observations:

Success Criteria - Achievements and compliance

Conformance status:

Observations:

Success Criteria - Governance over time

Conformance status:

Observations:

Success Criteria - Technology legislation

Conformance status:

Observations:

5.2 - Assign a sustainability advocate

Success Criteria - Advocate for sustainability

Conformance status:

Observations:

5.3 - Inform, raise awareness, and train for sustainability

Success Criteria - Inform and aware

Conformance status:

Observations:

Success Criteria - Routine training

Conformance status:

Observations:

Success Criteria - Active participation

Conformance status:

Observations:

Success Criteria - Training materials

Conformance status:

Observations:

Success Criteria - Incentivize progress

Conformance status:

Observations:

5.4 - Communicate the environmental impact of user choices

Success Criteria - Communication of impact

Conformance status:

Observations:

5.5 - Calculate the environmental impact

Success Criteria - Life-cycle assessment

Conformance status:

Observations:

Success Criteria - Competitor impact

Conformance status:

Observations:

Success Criteria - Tooling impact

Conformance status:

Observations:

5.6 - Define clear organizational sustainability goals and metrics

Success Criteria - Web sustainability goals

Conformance status:

Observations:

5.7 - Validate web sustainability efforts through external verification

Success Criteria - Obtaining verification

Conformance status:

Observations:

Success Criteria - Maintaining verification

Conformance status:

Observations:

5.8 - Support mandatory disclosures and reporting

Success Criteria - Policies and practices

Conformance status:

Observations:

Success Criteria - Impact reports

Conformance status:

Observations:

Success Criteria - Disclosure reporting

Conformance status:

Observations:

Success Criteria - Impact reduction

Conformance status:

Observations:

5.9 - Create one or more impact business models

Success Criteria - Theory of change

Conformance status:

Observations:

5.10 - Follow a product management and maintenance strategy

Success Criteria - Management and maintenance

Conformance status:

Observations:

Success Criteria - Planning Strategy

Conformance status:

Observations:

Success Criteria - Resourcing products

Conformance status:

Observations:

Success Criteria - Resource measurement

Conformance status:

Observations:

Success Criteria - Failure indicators

Conformance status:

Observations:

5.11 - Implement continuous improvement procedures

Success Criteria - Continuous improvement

Conformance status:

Observations:

Success Criteria - Retrospectives conducted

Conformance status:

Observations:

Success Criteria - Iterative consideration

Conformance status:

Observations:

Success Criteria - Functionality decisions

Conformance status:

Observations:

5.12 - Document updates and evolutions

Success Criteria - Feature changes

Conformance status:

Observations:

5.13 - Evaluate if a digital product or service is necessary

Success Criteria - Sustainable Development Goals

Conformance status:

Observations:

Success Criteria - Creation evaluation

Conformance status:

Observations:

Success Criteria - Obstacle consideration

Conformance status:

Observations:

5.14 - Provide a supplier standards of practice document

Success Criteria - Vetting potential partners

Conformance status:

Observations:

Success Criteria - Collaborative measurement

Conformance status:

Observations:

Success Criteria - Informative partner promotion

Conformance status:

Observations:

5.15 - Share economic benefits

Success Criteria - Living wage

Conformance status:

Observations:

Success Criteria - Incentivisation

Conformance status:

Observations:

Success Criteria - Employee benefits

Conformance status:

Observations:

5.16 - Share decision-making power with affected parties

Success Criteria - Decision-making

Conformance status:

Observations:

5.17 - Use Diversity, Equity, Justice, Inclusion (DEJI) practices

Success Criteria - DEJI practices

Conformance status:

Observations:

Success Criteria - DEJI training

Conformance status:

Observations:

Success Criteria - DEJI improvements

Conformance status:

Observations:

5.18 - Promote responsible data practices

Success Criteria - Data practices

Conformance status:

Observations:

Success Criteria - Data ownership

Conformance status:

Observations:

Success Criteria - Outdated content

Conformance status:

Observations:

5.19 - Establish responsible practices around AI and emerging or disruptive technologies

Success Criteria - AI (Artificial Intelligence) and data collection

Conformance status:

Observations:

Success Criteria - Business adaptation

Conformance status:

Observations:

Success Criteria - Environmental responsibilities

Conformance status:

Observations:

Success Criteria - Automated tooling

Conformance status:

Observations:

Success Criteria - Quantum resilience

Conformance status:

Observations:

5.20 - Adopt responsible financial practices

Success Criteria - Fuel divestment

Conformance status:

Observations:

Success Criteria - Responsible finance

Conformance status:

Observations:

5.21 - Adopt organizational philanthropy practices

Success Criteria - Philanthropy policy

Conformance status:

Observations:

Success Criteria - Voluntary work

Conformance status:

Observations:

5.22 - Plan for a digital product or service's care and end-of-life

Success Criteria - End-of-life care

Conformance status:

Observations:

5.23 - Repair, reuse, refurbish, recycle or reduce e-waste

Success Criteria - E-waste management

Conformance status:

Observations:

Success Criteria - E-waste policy

Conformance status:

Observations:

Success Criteria - Refurbishment strategy

Conformance status:

Observations:

Success Criteria - Right to repair

Conformance status:

Observations:

5.24 - Define performance, environmental, and human budgets

Success Criteria - Environmental budget

Conformance status:

Observations:

Success Criteria - Performance budget

Conformance status:

Observations:

Success Criteria - Human budget

Conformance status:

Observations:

Success Criteria - Measurable improvements

Conformance status:

Observations:

5.25 - Use and contribute to open source

Success Criteria - Open source governance

Conformance status:

Observations:

Success Criteria - Collaboration and contribution

Conformance status:

Observations:

5.26 - Create a business continuity and disaster recovery plan

Success Criteria - Plan of action

Conformance status:

Observations:

Success Criteria - Audience awareness

Conformance status:

Observations:

Additional Information

Provide any additional information related to conformity (e.g. a URL to a detailed progress report).

Approval and complaints process
In this section you can add information about the formal approval of this sustainability report and, if applicable, any complaints escalation procedure.

Formal complaints

Describe any formal complaints procedures

Approval of the sustainability report

Name of person or department (Example: "John Doe")

Position or function (Example: "Director of Communication")

Preview results