Updates to 4.1 and 4.10

drafts/guidelines.json

@@ -3739,7 +3739,7 @@
 						{
 							"title": "Monitor Metrics",
 							"testable": "[Machine Testable](https://w3c.github.io/sustyweb/star.html#HIS01-1)",
-							"description": "To assess the environmental impacts of hosting and detect overconsumption, some indicators are monitored: energy / water usage, CPU / Memory usage, allocation of servers and CPU cores, etc. These indicators are be used to calculate metrics directly related to environmental impacts, such as Power Usage Effectiveness (PUE), Water Usage Effectiveness (WUE), and Carbon Usage Effectiveness (CUE). They are displayed to visitors for transparency and monitoring reasons."
+							"description": "To assess the environmental impacts of hosting and detect overconsumption, some indicators are monitored: energy / water usage, CPU / Memory usage, allocation of servers and CPU cores, etc. These indicators are be used to calculate metrics directly related to environmental impacts, such as Power Usage Effectiveness (PUE), Water Usage Effectiveness (WUE), and Carbon Usage Effectiveness (CUE). They are displayed to visitors for transparency and monitoring reasons. If possible (to reduce redundancy) the ability to scale packages based on usage requirements is made available (manually or automatically) to reduce wasted resources."
 						},
 						{
 							"title": "Equipment Longevity",
@@ -4397,12 +4397,12 @@
 						{
 							"title": "Local Servers",
 							"testable": "[Machine Testable](https://w3c.github.io/sustyweb/star.html#HIS10-3)",
-							"description": "A hosting provider was chosen with servers located close to the visitor."
+							"description": "A hosting provider was chosen with servers located close to the visitor, considering that if you only serve a local audience, the need for distributed content (CDNs) that duplicate your materials globally may not be worthwhile."
 						},
 						{
 							"title": "Avoid Caching Inappropriate Resources",
 							"testable": "[Machine Testable](https://w3c.github.io/sustyweb/star.html#HIS10-4)",
-							"description": "Don't use the service to host dynamic resources or JavaScript (unless through a first-party host) as due to cache partitioning, cross-origin resource sharing (CORS), and other browser mechanics, any benefits are negated by weaker performance, the inability to cache or interact, and the potential introduction of security and privacy issues to be introduced. This doesn't affect JSON or other static assets."
+							"description": "Don't use the service to host dynamic / regularly changing resources or JavaScript (unless through a first-party host) as due to cache partitioning, cross-origin resource sharing (CORS), and other browser mechanics, any benefits are negated by weaker performance, the inability to cache or interact, and the potential introduction of security and privacy issues to be introduced. This doesn't affect JSON or other static assets."
 						},
 						{
 							"title": "Process Data Close to the Source",

drafts/index.html

@@ -5492,7 +5492,7 @@ <h3>Choose a Sustainable Hosting Provider</h3>
 				<p>In addition to reducing the environmental impacts of a website, choose a hosting service that mitigates the remaining impacts. To make sure of this, there are many criteria to look for.</p>
 				<section class="notoc">
 					<h4>Success Criterion - Monitor Metrics <a href="https://w3c.github.io/sustyweb/star.html#HIS01-1"><mark>(Machine Testable)</mark></a></h4>
-					<p>To assess the environmental impacts of hosting and detect overconsumption, some indicators are monitored: energy / water usage, CPU / Memory usage, allocation of servers and CPU cores, etc. These indicators are used to calculate metrics directly related to environmental impacts, such as Power Usage Effectiveness (<abbr title="Power Usage Effectiveness">PUE</abbr>), Water Usage Effectiveness (<abbr title="Water Usage Effectiveness">WUE</abbr>), and Carbon Usage Effectiveness (<abbr title="Carbon Usage Effectiveness">CUE</abbr>). They are displayed to visitors for transparency and monitoring reasons.</p>
+					<p>To assess the environmental impacts of hosting and detect overconsumption, some indicators are monitored: energy / water usage, CPU / Memory usage, allocation of servers and CPU cores, etc. These indicators are used to calculate metrics directly related to environmental impacts, such as Power Usage Effectiveness (<abbr title="Power Usage Effectiveness">PUE</abbr>), Water Usage Effectiveness (<abbr title="Water Usage Effectiveness">WUE</abbr>), and Carbon Usage Effectiveness (<abbr title="Carbon Usage Effectiveness">CUE</abbr>). They are displayed to visitors for transparency and monitoring reasons. If possible (to reduce redundancy) the ability to scale packages based on usage requirements is made available (manually or automatically) to reduce wasted resources.</p>
 				</section>
 				<section class="notoc">
 					<h4>Success Criterion - Equipment Longevity <mark class="alert">(Human Testable)</mark></h4>
@@ -6241,11 +6241,11 @@ <h4>Success Criterion - Sustainability Commitment <a href="https://w3c.github.io
 				</section>
 				<section class="notoc">
 					<h4>Success Criterion - Local Servers <a href="https://w3c.github.io/sustyweb/star.html#HIS10-3"><mark>(Machine Testable)</mark></a></h4>
-					<p>A hosting provider was chosen with servers located close to the visitor.</p>
+					<p>A hosting provider was chosen with servers located close to the visitor, considering that if you only serve a local audience, the need for distributed content (CDNs) that duplicate your materials globally may not be worthwhile.</p>
 				</section>
 				<section class="notoc">
 					<h4>Success Criterion - Avoid Caching Inappropriate Resources <a href="https://w3c.github.io/sustyweb/star.html#HIS10-4"><mark>(Machine Testable)</mark></a></h4>
-					<p>Don't use the service to host dynamic resources or JavaScript (unless through a first-party host) as due to cache partitioning, cross-origin resource sharing (<abbr title="Cross-origin resource sharing">CORS</abbr>), and other browser mechanics, any benefits are negated by weaker performance, the inability to cache or interact, and the potential introduction of security and privacy issues to be introduced. This doesn't affect <abbr title="JavaScript Object Notation">JSON</abbr> or other static assets.</p>
+					<p>Don't use the service to host dynamic / regularly changing resources or JavaScript (unless through a first-party host) as due to cache partitioning, cross-origin resource sharing (<abbr title="Cross-origin resource sharing">CORS</abbr>), and other browser mechanics, any benefits are negated by weaker performance, the inability to cache or interact, and the potential introduction of security and privacy issues to be introduced. This doesn't affect <abbr title="JavaScript Object Notation">JSON</abbr> or other static assets.</p>
 				</section>
 				<section class="notoc">
 					<h4>Success Criterion - Process Data Close to the Source <mark class="alert">(Human Testable)</mark></h4>

drafts/quickref.html

@@ -1281,7 +1281,7 @@ <h2>Hosting, Infrastructure and Systems</h2>
 						<td></td><td colspan="5"><strong>Success Criterion</strong></td>
 					</tr>
 					<tr>
-						<td><input type="checkbox" id="4.1a"></td><td colspan="5"><label for="4.1a">To assess the environmental impacts of hosting and detect overconsumption, some indicators are monitored: energy / water usage, <abbr title="Central Processing Unit">CPU</abbr> / Memory usage, allocation of servers and CPU cores, etc. These indicators are used to calculate metrics directly related to environmental impacts, such as Power Usage Effectiveness (<abbr title="Power Usage Effectiveness">PUE</abbr>), Water Usage Effectiveness (<abbr title="Water Usage Effectiveness">WUE</abbr>), and Carbon Usage Effectiveness (<abbr title="Carbon Usage Effectiveness">CUE</abbr>). They are displayed to visitors for transparency and monitoring reasons.</label></td>
+						<td><input type="checkbox" id="4.1a"></td><td colspan="5"><label for="4.1a">To assess the environmental impacts of hosting and detect overconsumption, some indicators are monitored: energy / water usage, <abbr title="Central Processing Unit">CPU</abbr> / Memory usage, allocation of servers and CPU cores, etc. These indicators are used to calculate metrics directly related to environmental impacts, such as Power Usage Effectiveness (<abbr title="Power Usage Effectiveness">PUE</abbr>), Water Usage Effectiveness (<abbr title="Water Usage Effectiveness">WUE</abbr>), and Carbon Usage Effectiveness (<abbr title="Carbon Usage Effectiveness">CUE</abbr>). They are displayed to visitors for transparency and monitoring reasons. If possible (to reduce redundancy) the ability to scale packages based on usage requirements is made available (manually or automatically) to reduce wasted resources.</label></td>
 					</tr>
 					<tr>
 						<td><input type="checkbox" id="4.1b"></td><td colspan="5"><label for="4.1b">Equipment is managed responsibly by keeping it as long as possible, using it as efficiently as possible, making sure it is certified, and purchasing long-lifespan products.</label></td>
@@ -1485,10 +1485,10 @@ <h2>Hosting, Infrastructure and Systems</h2>
 						<td><input type="checkbox" id="4.10b"></td><td colspan="5"><label for="4.10b">Verify that the CDN provides a commitment to sustainability.</label></td>
 					</tr>
 					<tr>
-						<td><input type="checkbox" id="4.10c"></td><td colspan="5"><label for="4.10c">A hosting provider was chosen with servers located close to the visitor.</label></td>
+						<td><input type="checkbox" id="4.10c"></td><td colspan="5"><label for="4.10c">A hosting provider was chosen with servers located close to the visitor, considering that if you only serve a local audience, the need for distributed content (CDNs) that duplicate your materials globally may not be worthwhile.</label></td>
 					</tr>
 					<tr>
-						<td><input type="checkbox" id="4.10d"></td><td colspan="5"><label for="4.10d">Don't the service to host dynamic resources or JavaScript (unless through a first-party host) as due to cache partitioning, cross-origin resource sharing (<abbr title="Cross-Origin Resource Sharing">CORS</abbr>), and other browser mechanics, any benefits are negated by weaker performance, the inability to cache or interact, and the potential introduction of security and privacy issues to be introduced. This doesn't affect <abbr title="JavaScript Object Notation">JSON</abbr> or other static assets.</label></td>
+						<td><input type="checkbox" id="4.10d"></td><td colspan="5"><label for="4.10d">Don't use the service to host dynamic / regularly changing resources or JavaScript (unless through a first-party host) as due to cache partitioning, cross-origin resource sharing (<abbr title="Cross-Origin Resource Sharing">CORS</abbr>), and other browser mechanics, any benefits are negated by weaker performance, the inability to cache or interact, and the potential introduction of security and privacy issues to be introduced. This doesn't affect <abbr title="JavaScript Object Notation">JSON</abbr> or other static assets.</label></td>
 					</tr>
 					<tr>
 						<td><input type="checkbox" id="4.10e"></td><td colspan="5"><label for="4.10e">All information passed between the layers of an application incurs a cost, both in terms of data transferred, and CPU cycles for (de)serialization. Wherever possible, data transformations must be performed close to the source to reduce these costs and avoid processing data that will later be discarded.</label></td>

drafts/star.html

@@ -3785,6 +3785,7 @@ <h3><dfn data-lt="Hosting">Hosting, Infrastructure and Systems</dfn></h3>
 								<p><strong>Tests</strong></p>
 								<p>Procedure</p>
 								<ol>
+									<li>Check if you only serve a local (single country) audience, if so, avoid CDN usage.</li>
 									<li>Check using analytics the average distribution of your product or service's visitors.</li>
 									<li>Check a hosting or CDN provider's locations to match as closely to your customers.</li>
 								</ol>