docs: updated to reflect that no hydration doesn't change Lighthouse scores

arctic-hen7 · arctic-hen7 · commit aabc2477436a · 2021-12-21T14:54:24.000+11:00
On the website, this was actually caused by a Tailwind minification error.
diff --git a/docs/0.3.x/en-US/hydration.md b/docs/0.3.x/en-US/hydration.md
@@ -12,6 +12,6 @@ But with hydration, the app shell can intelligently melt the iron that it's been
 
 ## Performance Costs of Disabling Hydration
 
-Not using hydration will impact your site's performance when the user first loads a page (moving around within the app is no problem), because the browser has to do a little more work, but it also has to completely re-display your site. The difference probably won't be noticeable to users, but tools like Lighthouse will notice this and will penalise your site for it.
+Not using hydration will impact your site's performance when the user first loads a page (moving around within the app is no problem), because the browser has to do a little more work, but it also has to completely re-display your site. The difference shouldn't be visible to users at all unless they try to scroll as soon as your site loads (as in within less than half a second on modern machines), in which case they'll be thrown back to the top of the site. However, Lighthouse doesn't seem to notice any differences, so your scores there won't change!
 
 Notably, to make hydration better for the community, you should file any bugs about hydration on [the Sycamore repository](https://github.com/sycamore-rs/sycamore).
diff --git a/docs/0.3.x/en-US/what-is-perseus.md b/docs/0.3.x/en-US/what-is-perseus.md
@@ -72,13 +72,6 @@ The only issue that prevents Perseus from achieving a consistent perfect score o
 </details>
 
 <details>
-<summary>I'm seeing really low scores on mobile...</summary>
-
-Right now, it's possible that you may see scores of around 50 on mobile for this website, though do not be alarmed! This is caused by a bug in Sycamore's [hydration systems](:hydration) which makes the Perseus website unusable, so we have to disable hydration. This means Perseus has to render a page and then re-render the whole thing (which you may have noticed if you try to scroll really soon after opening this site).
-
-For the vast majority of sites, you'll be able to use hydration without a problem, and you should see _much_ higher scores (well into the 90s), though there are still some pain points for this website in particular that are being worked through (these should be sorted quite soon)!
-
-</details>
 
 If you're interested in seeing how Perseus compares on speed and a number of other features to other frameworks, check out the [comparisons page](comparisons).
 
diff --git a/docs/next/en-US/hydration.md b/docs/next/en-US/hydration.md
@@ -12,6 +12,6 @@ But with hydration, the app shell can intelligently melt the iron that it's been
 
 ## Performance Costs of Disabling Hydration
 
-Not using hydration will impact your site's performance when the user first loads a page (moving around within the app is no problem), because the browser has to do a little more work, but it also has to completely re-display your site. The difference probably won't be noticeable to users, but tools like Lighthouse will notice this and will penalise your site for it.
+Not using hydration will impact your site's performance when the user first loads a page (moving around within the app is no problem), because the browser has to do a little more work, but it also has to completely re-display your site. The difference shouldn't be visible to users at all unless they try to scroll as soon as your site loads (as in within less than half a second on modern machines), in which case they'll be thrown back to the top of the site. However, Lighthouse doesn't seem to notice any differences, so your scores there won't change!
 
 Notably, to make hydration better for the community, you should file any bugs about hydration on [the Sycamore repository](https://github.com/sycamore-rs/sycamore).
diff --git a/docs/next/en-US/what-is-perseus.md b/docs/next/en-US/what-is-perseus.md
@@ -72,13 +72,6 @@ The only issue that prevents Perseus from achieving a consistent perfect score o
 </details>
 
 <details>
-<summary>I'm seeing really low scores on mobile...</summary>
-
-Right now, it's possible that you may see scores of around 50 on mobile for this website, though do not be alarmed! This is caused by a bug in Sycamore's [hydration systems](:hydration) which makes the Perseus website unusable, so we have to disable hydration. This means Perseus has to render a page and then re-render the whole thing (which you may have noticed if you try to scroll really soon after opening this site).
-
-For the vast majority of sites, you'll be able to use hydration without a problem, and you should see _much_ higher scores (well into the 90s), though there are still some pain points for this website in particular that are being worked through (these should be sorted quite soon)!
-
-</details>
 
 If you're interested in seeing how Perseus compares on speed and a number of other features to other frameworks, check out the [comparisons page](comparisons).
 
