Joining the HTTP Archive’s technology detection with the Chrome UX Report makes for some really interesting analyses.
I’m giving a presentation tomorrow at DrupalEurope about performance and it’s really compelling to be able to show how the user experience varies by CMS. Here’s a query that calculates the average FCP distribution for each CMS detected by Wappalyzer in the HTTP Archive:
SELECT app, COUNT(DISTINCT origin) AS freq, ROUND(SUM(IF(bin.start < 1000, bin.density, 0)) / SUM(bin.density), 4) AS fast, ROUND(SUM(IF(bin.start >= 1000 AND bin.start < 3000, bin.density, 0)) / SUM(bin.density), 4) AS avg, ROUND(SUM(IF(bin.start >= 3000, bin.density, 0)) / SUM(bin.density), 4) AS slow FROM `chrome-ux-report.all.201808`, UNNEST(first_contentful_paint.histogram.bin) AS bin JOIN ( SELECT url, app FROM `httparchive.technologies.2018_08_15_desktop` WHERE category = 'CMS' GROUP BY url, app) ON CONCAT(origin, '/') = url GROUP BY app ORDER BY freq DESC
Sorting the CMSs by popularity, there isn’t really a clear correlation with performance, but it’s still interesting to see the relative performance of each one.
- Drupal has a higher density of fast FCP than WordPress
- Wix, Squarespace, Joomla, and WordPress have < 25% fast FCP
- All CMSs are average FCP (between 1 and 3s) at the 50th percentile
- TYPO3 has the highest density of fast FCP