Implement SQL query to compare impact of using auto-sizes plugin for sizes=auto
functionality
#162
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR's query takes the approach from #108 and uses it in a comparison over time, specifically focused on determining the impact of the
sizes="auto"
addition from the Enhanced Responsive Images plugin (slug:auto-sizes
). The relevant feature was recently committed to WordPress Core.It compares sites that were using the plugin in 2024-06 with the same intersection of sites not using the plugin in 2024-05. It then also considers only images with the same URL on the same site, to get as close to a consistent dataset as possible.
The timeframe was chosen because it needs to be before 2024-07, as in July version 1.1.0 of the plugin introduced additional functionality which we don't want to influence the result. Additionally, the choice of comparing between adjacent months was made so that there's the least possible room for changes on each site that could skew the data.
Query results
Since the raw query results are so large, please see this spreadsheet.
The spreadsheet also contains a summary of the diff in another tab, as well as the results of a similar query that gets the LCP passing rate of these sites before and after, as another reference point. For the CrUX data, it uses the approach from https://colab.research.google.com/drive/1TmbJhSBuM-gTHA_E_W96pSjraQkFYpyi#scrollTo=XoNNe9GNW2hm.