From 760d27e16458c4cfa25f2b2e166541f3df7c1a48 Mon Sep 17 00:00:00 2001
From: Daniel <198354403+BaconMan1168@users.noreply.github.com>
Date: Mon, 7 Sep 2026 08:35:15 +0800
Subject: [PATCH] fix(PerformanceResourceTiming): clarify startTime is not
 always fetchStart

The startTime bullet claimed the value is equivalent to fetchStart, which
contradicted the timestamp diagram below it. The two only coincide when there
are no HTTP redirects, since fetchStart is the time immediately before the
final resource in the redirection is fetched.
---
 files/en-us/web/api/performanceresourcetiming/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/files/en-us/web/api/performanceresourcetiming/index.md b/files/en-us/web/api/performanceresourcetiming/index.md
index eb7a16004797126..1481f68b816760e 100644
--- a/files/en-us/web/api/performanceresourcetiming/index.md
+++ b/files/en-us/web/api/performanceresourcetiming/index.md
@@ -62,7 +62,7 @@ This interface extends the following {{domxref("PerformanceEntry")}} properties
 - {{domxref("PerformanceEntry.name")}} {{ReadOnlyInline}}
   - : Returns the resource's URL.
 - {{domxref("PerformanceEntry.startTime")}} {{ReadOnlyInline}}
-  - : Returns the {{domxref("DOMHighResTimeStamp","timestamp")}} for the time a resource fetch started. This value is equivalent to {{domxref("PerformanceResourceTiming.fetchStart")}}.
+  - : Returns the {{domxref("DOMHighResTimeStamp","timestamp")}} for the time a resource fetch started. If there are no HTTP redirects, this value is equivalent to {{domxref("PerformanceResourceTiming.fetchStart")}}. If there are HTTP redirects, this value is the time the first fetch in the redirection started, whereas `fetchStart` returns the time immediately before the user agent starts to fetch the final resource in the redirection.
 
 ### Timestamps