Submitted by Christoph Weber
on Thu, 07/29/2021 - 14:28
Great article, thanks!
There is an additional advantage, which is really a subset of your second argument: If your site loads over HTTP/2 or HTTP/3, then avoiding the new server request is sidestepping an actual antipattern, and your site speed gets a more pronounced boost than under the older HTTP 1.1 protocol. HTTP/2 and HTTP/3 use multiplexed streams of data over the same connection, and the font file becomes just one more resource that is multiplexed onto that stream, which is already going at full speed. No connection cost, no TCP ramp-up cost, nothing else, just the raw time it takes to transmit the font file.
Great article, thanks!
There is an additional advantage, which is really a subset of your second argument: If your site loads over HTTP/2 or HTTP/3, then avoiding the new server request is sidestepping an actual antipattern, and your site speed gets a more pronounced boost than under the older HTTP 1.1 protocol. HTTP/2 and HTTP/3 use multiplexed streams of data over the same connection, and the font file becomes just one more resource that is multiplexed onto that stream, which is already going at full speed. No connection cost, no TCP ramp-up cost, nothing else, just the raw time it takes to transmit the font file.