Skip to content

Commit 9a984b7

Browse files
authored
fix: fix typos (#3276)
* fix: fix typos Signed-off-by: Jens Oliver Meiert <jens@meiert.com> * fix: remove dup “process” Signed-off-by: Jens Oliver Meiert <jens@meiert.com> Signed-off-by: Jens Oliver Meiert <jens@meiert.com>
1 parent f674b79 commit 9a984b7

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

src/content/en/2021/page-weight.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ When a user requests a web page via [HTTP](./http), all files needed by the page
6060

6161
A negative effect of large page weight is due to [_latency_](https://developer.mozilla.org/en-US/docs/Web/Performance/Understanding_latency) and _bandwidth_ constraints. Latency measures the time it takes for the request to connect to the server storing the files and begin the process of transporting those files, while bandwidth measures the time it takes to download the resources. If a bunch of files are requested, no matter the technology, there is a limit on how much can be processed and transferred in any given period. I've audited WordPress sites that request as many as 170 files or more, which ensures terrible page loading performance starting with high latency periods.
6262

63-
Many optimizations can improve transfer/loading time, such as compressing and combining certain file requests, using HTTP/2—or the newer HTTP/3—protocols, and using a modern browser's ability to [preconnect to and preload](./resource-hints) certain files to speed the the whole process process up, but ultimately page weight will still have an impact here. The [Performance chapter](./performance) covers a wide range of factors that effect page loading performance.
63+
Many optimizations can improve transfer/loading time, such as compressing and combining certain file requests, using HTTP/2—or the newer HTTP/3—protocols, and using a modern browser's ability to [preconnect to and preload](./resource-hints) certain files to speed the whole process up, but ultimately page weight will still have an impact here. The [Performance chapter](./performance) covers a wide range of factors that effect page loading performance.
6464

6565
### Rendering
6666

src/content/en/2022/markup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -454,7 +454,7 @@ On 6.1% of pages, you still find `center` elements (hi <a hreflang="en" href="ht
454454
{{ figure_markup(
455455
image="obsolete-elements-relative-use.png",
456456
caption="Obsolete elements relative use.",
457-
description="Pie chart showing `center` is 43.0% of obsolete element usage on mobile, `font` is 38.2%, `marquee` is 7.0%, `nobr` 2.6%, `big` 2.6%, `frame` 1.5% and the the rest of the pie is make up of unlabelled other elements.",
457+
description="Pie chart showing `center` is 43.0% of obsolete element usage on mobile, `font` is 38.2%, `marquee` is 7.0%, `nobr` 2.6%, `big` 2.6%, `frame` 1.5% and the rest of the pie is made up of unlabelled other elements.",
458458
chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vRjXjOczLu9q3mcQ-UFLUOmZgefGNCPVYeEwo4cDxQTymgmD_1D5dbZ728Mz1SkEMZHxQgwcWmLjkgx/pubchart?oid=1875548366&format=interactive",
459459
sheets_gid="69619977",
460460
sql_file="obsolete_elements.sql",

0 commit comments

Comments
 (0)