Sustainability Best Practices
CMSCloudHeartcoreDXP
  • Introduction
  • Infrastructure
    • Infrastructure Overview
    • Hosting
    • Architecture
    • Security and Bots
  • Backend
    • Backend Overview
    • Upgrades and patches
    • Cache responses
    • Sustainable Design Patterns
    • Performance Testing
    • Common pitfalls
    • SOAP, REST and GraphQL
    • SQL optimization
    • JAMstack
    • Monolithic vs. Service based Architecture
    • Async
    • Background tasks
  • Frontend
    • Frontend Overview
    • Page weight budget
    • Image optimization
    • Asset optimization
    • Limit use of 3rd parties
    • Lazyload resources
    • Mobile first
  • Editor
    • Editor Overview
    • Content Types
    • Content Optimization
    • Design Choices
    • Data Management
    • Housekeeping
  • Telemetry
    • Telemetry Overview
    • February 2024
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Frontend

Limit use of 3rd parties

PreviousAsset optimizationNextLazyload resources

Last updated 1 year ago

Was this helpful?

Third-party requests account for , with 94% of mobile websites having at least one identifiable third-party resource.

While third parties can enhance the functionality of your website, they will introduce more HTTP requests. Potentially this will add other undesirable outcomes for the user such as sharing data. Before adding any third party, assess their purpose and ensure they don't increase the page weight. It’s also possible that these 3rd parties are not using .

45% of all requests
green hosting providers