CMS Benchmarking

Created on 17 October 2024, 2 months ago

A benchmarking exercise is being conducted as part of Drupal CMS product research

It will involve setting up other CMSs like WordPress, Webflow, AEM and documenting/assessing specific features/workflows.

πŸ“Œ Task
Status

Active

Component

General

Created by

πŸ‡¨πŸ‡¦Canada Kushneet

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Kushneet
  • πŸ‡ΈπŸ‡ͺSweden johnwebdev

    Nice! I think these benchmarks and exercises are really valuable!

    What is the baseline? Are we setting the CMS up locally, or using some managed solution or trial experience? Or are we benchmarking all of these three as three separate benchmarks?

    If setting up locally:

    Will the exercise run on Windows, Mac - or both? Linux?
    Will you start with having an existing development environment? Or is setting that up part of the benchmark?

  • πŸ‡¬πŸ‡§United Kingdom catch

    Where this this benchmarking being tracked?

    Came here to ask if any performance comparisons are being done - e.g. if people are setting up local ddev installs (or default hosted installs for SASS) then it would be possible to run lighthouse or similar against the install and compare vs. the default install of Drupal CMS. It could use some standard steps (e.g. testing logged out vs. as an admin etc.).

  • πŸ‡¦πŸ‡ΊAustralia pameeela

    As Gabor noted in Slack, this is product benchmarking (of UX and features) rather than performance.

  • πŸ‡¬πŸ‡§United Kingdom catch

    Right but presumably UX and features would include things like responsive image and resizing support, CSS and JavaScript aggregation or the lack of it?

    And then I was hoping this could be expanded to page weight / loading times.

  • πŸ‡¦πŸ‡ΊAustralia pameeela

    It's being pretty loosely gathered by contributors here: https://airtable.com/appmVfRW1N0voF7vM/shrEI3Evagd1sCmn5/tbls3Xv0A1WxkTUq0

    Based on the contribution model I don't think it's feasible to include performance metrics.

Production build 0.71.5 2024