HTTPArchive
Fonts 2024 Queries
In this PR, the queries from 2022 are copied to 2024 and are updated as follows:
Changes
- The data source is exclusively
httparchive.all. - All queries are annotated with the question they answer.
- All queries follow the same structure and style.
- Queries are split by the section in the chapter where they are used.
- Repeated parts are extracted into common functions.
Structure
The queries are split by the section where they are used:
design/is about foundries and families,development/is about tools and technologies, andperformance/is about hosting and serving.
Each file name starts with one of the following prefixes indicating the primary subject of the corresponding analysis:
fonts_is about font files,pages_is about HTML pages,scripts_is about JavaScript scripts, andstyles_is about CSS style sheets.
The prefix is followed by the property studied given in singular, potentially extended one or several suffixes narrowing down the scope, as in fonts_size_by_table.sql and pages_link_relation.sql.
Contents
Each query starts with a preamble indicating the section, question, and normalization type:
-- Section: Performance
-- Question: What is the distribution of the file size broken down by table?
-- Normalization: Sites
Many queries rely on temporary functions for convenience and clarity. The functions appear in several queries are extracted into a common file: common.sql. Whenever any of the functions defined in common.sql is used by a query, the query has the following line at the top:
-- INCLUDE ../common.sql
It signalizes that, prior to executing the query, common.sql has to be inlined.
As I explained there, I did not notice there was a PR open and created a new one. And even if I did, I would probably have to do that anyway to have more control. In that other PR, the queries from 2022 are copied over to the folder for 2024 with no change. So there is no progress there.
Are all the force-pushes intentionally?
Clicking on my notifications I see this which is a bit annoying.
