Digital sustainability. technical efficiency on Shopify

For Francesco Guiducci, digital sustainability on Shopify is first of all technical efficiency, product longevity and no pointless waste. It means lighter pages, fewer dependencies, images suited to their context and code that serves a real function. Francesco Guiducci, freelance Shopify specialist in Rome, works on the theme, apps, scripts and external resources to cut the superfluous without removing value. The service is for merchants who want a tidier, more maintainable store. Results are measured before and after, but they are not a certified CO₂ measure or an ESG claim.

When two solutions genuinely meet the same requirement, Francesco Guiducci prefers the one with less complexity, less code and fewer external dependencies. That does not mean dropping useful features for the sake of speed. It means avoiding technical weight that brings no concrete benefit to the merchant or to the people using the store.

The first question is simple: is this resource, app, library or integration really needed? If yes, it should be made as efficient as possible. If not, the cleanest improvement is often to remove it.

Digital sustainability work acts on five areas: images and video, JavaScript and third-party scripts, apps and dependencies, theme and components, fonts, CSS and external resources. Francesco Guiducci evaluates each element by function and real impact and keeps what is needed.

• Images and videoReal dimensions, formats, quality-to-weight ratio, responsive loading and lazy loading where appropriate are checked. A hero designed for desktop should not make a phone download a file sized for a much larger screen. For video, the question is whether autoplay, external players or early loading are justified by the content.
• JavaScript and third-party scriptsThe analysis covers what loads before useful content, which scripts block rendering and how much work the browser must do. Apps, pixels, widgets and libraries can be necessary, but they are judged by function and real impact. When HTML, Liquid or CSS are robust enough, JavaScript is not added out of habit.
• Apps and dependenciesHaving fewer apps is not a goal in itself: an app that solves a problem well can be more efficient than custom code that must be maintained. The target is overlap, leftover snippets after an uninstall and integrations that keep loading resources without a function.
• Theme and componentsConfigurable, reusable components are preferred to near-identical variants of the same block. A tidy theme is easier to maintain and makes it clearer where a problem comes from. Native Shopify features are preferred when they cover the requirement well, without ideology.
• Fonts, CSS and external resourcesThe check covers how many fonts and variants load, which stylesheets are really needed and how many resources come from external hosts. Fewer requests and dependencies help performance and make the system more predictable and less fragile.

Digital sustainability is not judged by a single number. For technical work, observable indicators are used: Core Web Vitals, rendering times, transferred weight, number of requests, third-party scripts, JavaScript work and the real behaviour of the main pages.

Measuring before and after avoids two common mistakes: optimising something that is not a real problem, or claiming an improvement only because the code looks cleaner.

A faster page may transfer less data and need less processing, but this does not automatically lead to a quantified environmental impact. Impact also depends on infrastructure, network, device, frequency of use, service lifetime and other factors that a frontend test does not measure.

For this reason technical evidence and environmental claims stay separate. Without a methodology and a measurement suited to the claim, web optimisation does not become a CO₂ figure or a green label.

A lighter solution that worsens accessibility, security or usability is not considered sustainable. A simple interface, a maintainable technical base and components that stay updatable have lasting value, even when the benefit cannot be expressed as one KPI.

The W3C Web Sustainability Guidelines reflect this broader view, which includes performance, accessibility, privacy and resilience. They are currently a Draft Group Note: an evolving reference, not a certification or a conformance standard.

The digital sustainability service has precise limits: it does not assign CO₂ amounts to pages, does not use Lighthouse as an environmental certification and does not remove useful features to improve a number. Francesco Guiducci states these limits to avoid claims that technical work cannot support.

• No amount of CO₂ is assigned automatically to each page.
• No Lighthouse score is used as an environmental certification.
• No useful feature is removed just to reach a higher performance number.
• No store is declared green because it uses compressed images or fewer scripts.
• No more complex custom code is treated as sustainable when an existing solution is simpler to maintain.

Francesco Guiducci starts from real bottlenecks and separates what is necessary from what has simply become technical debt. To see where a store loads more code, apps or resources than it needs, the starting point is the Shopify audit.

• Technical reference: Shopify theme performanceShopify's official best practices for theme performance.
• Technical reference: W3C Web Sustainability GuidelinesW3C Draft Group Note, an evolving reference and not a conformance standard.

The cost of digital sustainability work depends on the project and on how much work is needed, which emerges from the store analysis with Francesco Guiducci, with no estimates before images, scripts and apps have been reviewed. The list of services can be viewed on ifgecommerce.com.

• WhatsApp+39 378 083 2717
• Emailinfo@ifgecommerce.com
• Contact page
• List of services and packsService list on ifgecommerce.com

• Shopify auditThe starting point for finding unnecessary code, apps and resources.
• Technical SEO and performanceWork on Core Web Vitals, rendering and page weight.
• Custom Liquid developmentTailored components and logic when native features are not enough.
• Maintenance and supportA technical base kept up over time, with components that stay updatable.
• AccessibilityWhy a lighter solution must not make the store harder to use.

• Does Francesco Guiducci certify the environmental impact of a Shopify store?No. Francesco Guiducci works on the technical efficiency of a Shopify store and does not issue certified CO₂ measures or ESG claims. A better Lighthouse score, less JavaScript or a few megabytes saved can point to a more efficient system, but they are not an environmental assessment on their own.
• Is a faster page also more sustainable?Not automatically. For Francesco Guiducci, a faster page may transfer less data and need less processing, but impact also depends on infrastructure, network, device, frequency of use and service lifetime. A frontend test does not measure those factors, so performance and sustainability are not treated as synonyms.
• Which indicators does Francesco Guiducci use to judge the work?Francesco Guiducci compares observable indicators before and after each intervention: Core Web Vitals, rendering times, transferred weight, number of requests, third-party scripts, JavaScript work and the real behaviour of the main pages. No single number is enough to describe the digital sustainability of a store.
• Is reducing installed apps always the goal?No. Francesco Guiducci does not treat fewer apps as a goal in itself: an app that solves a problem well can be more efficient than custom code that has to be maintained. The work targets overlap, leftover snippets after an uninstall and integrations that keep loading resources without a function.
• Can useful features be removed to get a better score?No. Francesco Guiducci does not remove useful features just to reach a higher performance number. A lighter solution that worsens accessibility, security or usability is not considered sustainable, and technical weight is reduced only when it brings no concrete benefit.
• Are the W3C Web Sustainability Guidelines a certification?No. The W3C Web Sustainability Guidelines are currently a Draft Group Note. Francesco Guiducci treats them as an evolving reference covering performance, accessibility, privacy and resilience, not as a certification or a conformance standard that a website can claim to meet.
• Where does the work start on an existing store?Francesco Guiducci starts from real bottlenecks, separating what is necessary from what is only technical debt. The starting point is the Shopify audit, which shows where the store loads more code, apps or resources than it needs.