Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Ecodesign a website around useful tasks

    Ecodesign starts with the service’s purpose. Smaller images help, but features, media and the equipment required to use the service matter too.

    Go to the method

    Person working on a laptop
    AI-generated illustration

    Start with a task and a framework

    Write down the essential task: find opening times, compare a service, book or send an enquiry. Ask whether each feature helps that task and whether a simpler solution delivers the same service. An animated carousel or decorative video may add transfers and constraints without useful information.

    The RGESN introduced by Arcep provides a technical framework for digital-service ecodesign. Select applicable criteria and document responses. Consulting the framework does not certify a website.

    • Useful task.
    • Audience and equipment.
    • Features that can be simplified.
    • Applicable criteria and evidence.

    Reduce transfers across the actual journey

    Measure transfers across the whole journey: opening, navigation and final action. Fictional example: the initial page becomes lighter but a gallery now loads every large image on first interaction; the opening gain does not describe the overall result. Review images, fonts, scripts and third parties, then compare suitable dimensions, deferred loading and removal of unused calls under identical conditions.

    Match caching to update frequency and reduce repeated requests. Organise long lists meaningfully or use accessible pagination. Removing a feature people need solely because it consumes resources is not sufficient reasoning: compare its usefulness with alternatives.

    Define what the displayed weight measures. In Resource Timing, encodedBodySize concerns the response body before HTTP content decompression, while decodedBodySize concerns the body afterwards. The latter is not the memory occupied by an image decoded into pixels. Fictional text-response example: 12 000 encoded bytes and 48 000 decoded bytes give a one-to-four ratio, or a 75% reduction of this body relative to its decoded size. This calculation describes neither all journey transfers nor environmental impact.

    Do not turn a reported zero size into proof of no traffic. transferSize can be zero for a locally cached resource or because some cross-origin information is not exposed. Rules also depend on the browser and service-worker responses. Resource Timing is cited here as its 1 September 2026 Candidate Recommendation Draft: check the actual tool and conditions. Retain bytes, scenario and visibility limits without presenting this measure alone as a carbon assessment or RGESN conformance.

    • Weight and requests per task.
    • Images sized for their display.
    • Justified third-party services.
    • Outdated content and avoidable downloads.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Fictional example: distinguish text-response sizes
    ReferenceValue or readingLimit
    encodedBodySize12 000 BBody with HTTP content compression
    decodedBodySize48 000 BBody after HTTP decompression, not pixel memory
    1 − 12 000 / 48 000 = 75 %Body reduction relative to decoded sizeNeither total network traffic nor carbon savings
    transferSizeZero possible depending on cache and data exposureInsufficient evidence of no traffic

    Test compatibility and trade-offs

    Try the journey on less powerful hardware, a slow connection and with keyboard navigation. Compatibility may prevent a simple task from requiring newer equipment. Check zoom, error messages and layout stability; reducing weight must not make information inaccessible.

    Overcompressed imagery may hide a product detail needed for comparison. Removing a font may improve loading while changing the visual identity. Record each trade-off’s observable effect, maintenance cost and reversal method if the experience worsens. The performance and accessibility guides explain complementary checks.

    Publish a verifiable approach

    Record scope, device, connection, cache and observed outcome before claiming a reduction. Fictional example: a return visit reuses cached images; do not compare its transfers with an uncached first visit as if design alone caused the difference. Report these situations separately. Measured bytes, requests and durations do not become a certain carbon footprint without an appropriate method and assumptions.

    A declaration should make criteria and evidence understandable. Arcep provides an example ecodesign declaration. Reassess after adding video, another language or an integration. The approach concerns an evolving service rather than a frozen page.

    Content updated on

    Acceptance matrix to adapt to your project

    These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    A video starts although text is sufficient for the task.Compare a simpler version and verify task completion.Same task on both versions, observed transfers and information still accessible without video.

    Frequently asked questions

    How can two versions be compared when caching changes the result?

    Define two scenarios: a first visit without retained resources, then a return visit with comparable caching. Use the same journeys and conditions for each version. Publish the measurement definition; an improvement in one scenario does not establish the same gain for every visitor.

    Can carbon reduction be claimed from smaller image files?

    File reduction can be measured in bytes. Its carbon effect requires a method, assumptions and scope. Describe the measurement without assigning precision it does not possess.