diff --git a/sql/2024/cms/cms_adoption_by_rank_all.sql b/sql/2024/cms/cms_adoption_by_rank_all.sql new file mode 100644 index 00000000000..7b09ff55217 --- /dev/null +++ b/sql/2024/cms/cms_adoption_by_rank_all.sql @@ -0,0 +1,51 @@ +#standardSQL +# CMS adoption per rank +SELECT + client, + rank_grouping, + CASE rank_grouping + WHEN 1e8 THEN 'all' + ELSE TRIM(CAST(rank_grouping AS STRING FORMAT '99,999,999')) + END AS rank_grouping_text, + COUNT(DISTINCT page) AS pages, + MAX(total) AS total, + COUNT(DISTINCT page) / MAX(total) AS pct +FROM ( + SELECT + client, + page, + rank_grouping + FROM + `httparchive.all.pages`, + UNNEST(technologies) AS tech, + UNNEST(tech.categories) AS category, + UNNEST([1e3, 1e4, 1e5, 1e6, 1e7, 1e8]) AS rank_grouping + WHERE + date = '2024-06-01' AND + rank <= rank_grouping AND + is_root_page AND + category = 'CMS' +) +JOIN ( + SELECT + client, + rank_grouping, + COUNT(0) AS total + FROM + `httparchive.all.pages`, + UNNEST([1e3, 1e4, 1e5, 1e6, 1e7, 1e8]) AS rank_grouping + WHERE + date = '2024-06-01' AND + rank <= rank_grouping AND + is_root_page + GROUP BY + client, + rank_grouping) +USING + (client, rank_grouping) +GROUP BY + client, + rank_grouping +ORDER BY + rank_grouping, + pages DESC diff --git a/sql/2024/page-weight/bytes_per_type.sql b/sql/2024/page-weight/bytes_per_type.sql new file mode 100644 index 00000000000..6d1e56419eb --- /dev/null +++ b/sql/2024/page-weight/bytes_per_type.sql @@ -0,0 +1,25 @@ +SELECT + percentile, + client, + is_root_page, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesTotal') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS total_kbytes, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesHtml') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS html_kbytes, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesJS') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS js_kbytes, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesCss') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS css_kbytes, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesImg') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS img_kbytes, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesOther') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS other_kbytes, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesHtmlDoc') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS html_doc_kbytes, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesFont') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS font_kbytes +FROM + `httparchive.all.pages`, + UNNEST([10, 25, 50, 75, 90, 100]) AS percentile +WHERE + date = '2024-06-01' +GROUP BY + percentile, + client, + is_root_page +ORDER BY + client, + is_root_page, + percentile diff --git a/sql/2024/page-weight/compression-usage.sql b/sql/2024/page-weight/compression-usage.sql new file mode 100644 index 00000000000..60bf4a37e9e --- /dev/null +++ b/sql/2024/page-weight/compression-usage.sql @@ -0,0 +1,22 @@ +SELECT + client, + is_root_page, + COUNTIF(JSON_VALUE(lighthouse, '$.audits.uses-text-compression.score') IS NULL) AS null_count, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.uses-text-compression.score') AS FLOAT64) >= 0.9) AS pass_count, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.uses-text-compression.score') AS FLOAT64) < 0.9) AS fail_count, + COUNT(0) AS total, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.uses-text-compression.score') AS FLOAT64) >= 0.9) / COUNT(0) AS pct_pass, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.uses-text-compression.score') AS FLOAT64) < 0.9) / COUNT(0) AS pct_fail +FROM + `httparchive.all.pages` +WHERE + date = '2024-06-01' +GROUP BY + client, + is_root_page +ORDER BY + client, + is_root_page, + null_count, + pass_count, + fail_count diff --git a/sql/2024/page-weight/cwv_trend.sql b/sql/2024/page-weight/cwv_trend.sql new file mode 100644 index 00000000000..12383b28dc8 --- /dev/null +++ b/sql/2024/page-weight/cwv_trend.sql @@ -0,0 +1,86 @@ +WITH metrics_data AS ( + SELECT + date, + client, + CAST(JSON_VALUE(summary, '$.bytesTotal') AS INT64) AS bytes_total, + CAST(JSON_VALUE(lighthouse, '$.audits.largest-contentful-paint.numericValue') AS FLOAT64) AS lcp, + CAST(JSON_VALUE(lighthouse, '$.audits.cumulative-layout-shift.numericValue') AS FLOAT64) AS cls, + CAST(JSON_VALUE(lighthouse, '$.audits.total-blocking-time.numericValue') AS FLOAT64) AS tbt, + CAST(JSON_VALUE(lighthouse, '$.audits.first-contentful-paint.numericValue') AS FLOAT64) AS fcp, + CAST(JSON_VALUE(lighthouse, '$.audits.interactive.numericValue') AS FLOAT64) AS tti, + CAST(JSON_VALUE(lighthouse, '$.categories.performance.score') AS FLOAT64) AS performance_score + FROM + `httparchive.all.pages` + WHERE + date >= '2023-06-01' AND + date <= '2024-06-01' AND + EXTRACT(DAY FROM date) = 1 -- Only include data from the first day of each month +) +SELECT + date, + client, + COUNT(DISTINCT IF(bytes_total > 0, bytes_total, NULL)) AS total_pages, + + -- Page Size metrics + ROUND(APPROX_QUANTILES(bytes_total, 1000)[OFFSET(100)] / 1024, 2) AS p10_page_size_kb, + ROUND(APPROX_QUANTILES(bytes_total, 1000)[OFFSET(250)] / 1024, 2) AS p25_page_size_kb, + ROUND(APPROX_QUANTILES(bytes_total, 1000)[OFFSET(500)] / 1024, 2) AS p50_page_size_kb, + ROUND(APPROX_QUANTILES(bytes_total, 1000)[OFFSET(750)] / 1024, 2) AS p75_page_size_kb, + ROUND(APPROX_QUANTILES(bytes_total, 1000)[OFFSET(900)] / 1024, 2) AS p90_page_size_kb, + + -- LCP metrics + ROUND(APPROX_QUANTILES(lcp, 1000)[OFFSET(100)], 2) AS p10_lcp, + ROUND(APPROX_QUANTILES(lcp, 1000)[OFFSET(250)], 2) AS p25_lcp, + ROUND(APPROX_QUANTILES(lcp, 1000)[OFFSET(500)], 2) AS p50_lcp, + ROUND(APPROX_QUANTILES(lcp, 1000)[OFFSET(750)], 2) AS p75_lcp, + ROUND(APPROX_QUANTILES(lcp, 1000)[OFFSET(900)], 2) AS p90_lcp, + + -- CLS metrics + ROUND(APPROX_QUANTILES(cls, 1000)[OFFSET(100)], 3) AS p10_cls, + ROUND(APPROX_QUANTILES(cls, 1000)[OFFSET(250)], 3) AS p25_cls, + ROUND(APPROX_QUANTILES(cls, 1000)[OFFSET(500)], 3) AS p50_cls, + ROUND(APPROX_QUANTILES(cls, 1000)[OFFSET(750)], 3) AS p75_cls, + ROUND(APPROX_QUANTILES(cls, 1000)[OFFSET(900)], 3) AS p90_cls, + + -- TBT metrics (as a proxy for FID) + ROUND(APPROX_QUANTILES(tbt, 1000)[OFFSET(100)], 2) AS p10_tbt, + ROUND(APPROX_QUANTILES(tbt, 1000)[OFFSET(250)], 2) AS p25_tbt, + ROUND(APPROX_QUANTILES(tbt, 1000)[OFFSET(500)], 2) AS p50_tbt, + ROUND(APPROX_QUANTILES(tbt, 1000)[OFFSET(750)], 2) AS p75_tbt, + ROUND(APPROX_QUANTILES(tbt, 1000)[OFFSET(900)], 2) AS p90_tbt, + + -- FCP metrics + ROUND(APPROX_QUANTILES(fcp, 1000)[OFFSET(100)], 2) AS p10_fcp, + ROUND(APPROX_QUANTILES(fcp, 1000)[OFFSET(250)], 2) AS p25_fcp, + ROUND(APPROX_QUANTILES(fcp, 1000)[OFFSET(500)], 2) AS p50_fcp, + ROUND(APPROX_QUANTILES(fcp, 1000)[OFFSET(750)], 2) AS p75_fcp, + ROUND(APPROX_QUANTILES(fcp, 1000)[OFFSET(900)], 2) AS p90_fcp, + + -- TTI metrics + ROUND(APPROX_QUANTILES(tti, 1000)[OFFSET(100)], 2) AS p10_tti, + ROUND(APPROX_QUANTILES(tti, 1000)[OFFSET(250)], 2) AS p25_tti, + ROUND(APPROX_QUANTILES(tti, 1000)[OFFSET(500)], 2) AS p50_tti, + ROUND(APPROX_QUANTILES(tti, 1000)[OFFSET(750)], 2) AS p75_tti, + ROUND(APPROX_QUANTILES(tti, 1000)[OFFSET(900)], 2) AS p90_tti, + + -- Performance Score metrics + ROUND(APPROX_QUANTILES(performance_score, 1000)[OFFSET(900)] * 100, 2) AS p10_performance_score, + ROUND(APPROX_QUANTILES(performance_score, 1000)[OFFSET(750)] * 100, 2) AS p25_performance_score, + ROUND(APPROX_QUANTILES(performance_score, 1000)[OFFSET(500)] * 100, 2) AS p50_performance_score, + ROUND(APPROX_QUANTILES(performance_score, 1000)[OFFSET(250)] * 100, 2) AS p75_performance_score, + ROUND(APPROX_QUANTILES(performance_score, 1000)[OFFSET(100)] * 100, 2) AS p90_performance_score, + + -- Good CWV percentages + ROUND(COUNTIF(lcp <= 2500) / COUNT(0) * 100, 2) AS good_lcp_percent, + ROUND(COUNTIF(cls <= 0.1) / COUNT(0) * 100, 2) AS good_cls_percent, + ROUND(COUNTIF(tbt <= 300) / COUNT(0) * 100, 2) AS good_tbt_percent, + ROUND(COUNTIF(fcp <= 1800) / COUNT(0) * 100, 2) AS good_fcp_percent + +FROM + metrics_data +GROUP BY + date, + client +ORDER BY + date DESC, + client diff --git a/sql/2024/page-weight/facades-usage.sql b/sql/2024/page-weight/facades-usage.sql new file mode 100644 index 00000000000..3153db14ce5 --- /dev/null +++ b/sql/2024/page-weight/facades-usage.sql @@ -0,0 +1,22 @@ +SELECT + client, + is_root_page, + COUNTIF(JSON_VALUE(lighthouse, '$.audits.third-party-facades.score') IS NULL) AS null_count, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.third-party-facades.score') AS FLOAT64) >= 0.9) AS pass_count, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.third-party-facades.score') AS FLOAT64) < 0.9) AS fail_count, + COUNT(0) AS total, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.third-party-facades.score') AS FLOAT64) >= 0.9) / COUNT(0) AS pct_pass, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.third-party-facades.score') AS FLOAT64) < 0.9) / COUNT(0) AS pct_fail +FROM + `httparchive.all.pages` +WHERE + date = '2024-06-01' +GROUP BY + client, + is_root_page +ORDER BY + client, + is_root_page, + null_count, + pass_count, + fail_count diff --git a/sql/2024/page-weight/minified_css_usage.sql b/sql/2024/page-weight/minified_css_usage.sql new file mode 100644 index 00000000000..96b56c0614c --- /dev/null +++ b/sql/2024/page-weight/minified_css_usage.sql @@ -0,0 +1,22 @@ +SELECT + client, + is_root_page, + COUNTIF(JSON_VALUE(lighthouse, '$.audits.unminified-css.score') IS NULL) AS null_count, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.unminified-css.score') AS FLOAT64) >= 0.9) AS pass_count, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.unminified-css.score') AS FLOAT64) < 0.9) AS fail_count, + COUNT(0) AS total, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.unminified-css.score') AS FLOAT64) >= 0.9) / COUNT(0) AS pct_pass, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.unminified-css.score') AS FLOAT64) < 0.9) / COUNT(0) AS pct_fail +FROM + `httparchive.all.pages` +WHERE + date = '2024-06-01' +GROUP BY + client, + is_root_page +ORDER BY + client, + is_root_page, + null_count, + pass_count, + fail_count diff --git a/sql/2024/page-weight/minified_js_usage.sql b/sql/2024/page-weight/minified_js_usage.sql new file mode 100644 index 00000000000..b0d2fc33a1d --- /dev/null +++ b/sql/2024/page-weight/minified_js_usage.sql @@ -0,0 +1,22 @@ +SELECT + client, + is_root_page, + COUNTIF(JSON_VALUE(lighthouse, '$.audits.unminified-javascript.score') IS NULL) AS null_count, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.unminified-javascript.score') AS FLOAT64) >= 0.9) AS pass_count, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.unminified-javascript.score') AS FLOAT64) < 0.9) AS fail_count, + COUNT(0) AS total, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.unminified-javascript.score') AS FLOAT64) >= 0.9) / COUNT(0) AS pct_pass, + COUNTIF(SAFE_CAST(JSON_VALUE(lighthouse, '$.audits.unminified-javascript.score') AS FLOAT64) < 0.9) / COUNT(0) AS pct_fail +FROM + `httparchive.all.pages` +WHERE + date = '2024-06-01' +GROUP BY + client, + is_root_page +ORDER BY + client, + is_root_page, + null_count, + pass_count, + fail_count diff --git a/sql/2024/page-weight/page_weight_trend.sql b/sql/2024/page-weight/page_weight_trend.sql new file mode 100644 index 00000000000..d7abe282593 --- /dev/null +++ b/sql/2024/page-weight/page_weight_trend.sql @@ -0,0 +1,23 @@ +SELECT + date, + client, + is_root_page, + ROUND(APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesTotal') AS INT64), 1000)[OFFSET(100)] / 1024, 2) AS p10, + ROUND(APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesTotal') AS INT64), 1000)[OFFSET(250)] / 1024, 2) AS p25, + ROUND(APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesTotal') AS INT64), 1000)[OFFSET(500)] / 1024, 2) AS p50, + ROUND(APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesTotal') AS INT64), 1000)[OFFSET(750)] / 1024, 2) AS p75, + ROUND(APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.bytesTotal') AS INT64), 1000)[OFFSET(900)] / 1024, 2) AS p90 +FROM + `httparchive.all.pages` +WHERE + date >= '2023-06-01' AND date <= '2024-06-01' AND -- Adjust this range as needed + CAST(JSON_VALUE(summary, '$.bytesTotal') AS INT64) > 0 AND + EXTRACT(DAY FROM date) = 1 -- Only include data from the first day of each month +GROUP BY + date, + client, + is_root_page +ORDER BY + date DESC, + client, + is_root_page diff --git a/sql/2024/page-weight/request_type_distribution.sql b/sql/2024/page-weight/request_type_distribution.sql new file mode 100644 index 00000000000..6be041822a4 --- /dev/null +++ b/sql/2024/page-weight/request_type_distribution.sql @@ -0,0 +1,25 @@ +SELECT + percentile, + client, + is_root_page, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.reqTotal') AS INT64), 1000)[OFFSET(percentile * 10)] AS total_req, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.reqHtml') AS INT64), 1000)[OFFSET(percentile * 10)] AS html_req, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.reqJS') AS INT64), 1000)[OFFSET(percentile * 10)] AS js_req, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.reqCss') AS INT64), 1000)[OFFSET(percentile * 10)] AS css_req, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.reqImg') AS INT64), 1000)[OFFSET(percentile * 10)] AS img_req, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.reqJson') AS INT64), 1000)[OFFSET(percentile * 10)] AS json_req, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.reqOther') AS INT64), 1000)[OFFSET(percentile * 10)] AS other_req, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.reqFont') AS INT64), 1000)[OFFSET(percentile * 10)] AS font_req +FROM + `httparchive.all.pages`, + UNNEST([10, 25, 50, 75, 90, 100]) AS percentile +WHERE + date = '2024-06-01' -- Adjust this date as needed +GROUP BY + percentile, + client, + is_root_page +ORDER BY + client, + is_root_page, + percentile diff --git a/sql/2024/page-weight/response_format_distribution.sql b/sql/2024/page-weight/response_format_distribution.sql new file mode 100644 index 00000000000..e7826f0158f --- /dev/null +++ b/sql/2024/page-weight/response_format_distribution.sql @@ -0,0 +1,21 @@ +SELECT + client, + percentile, + CAST(JSON_VALUE(summary, '$.type') AS STRING) AS format, + is_root_page, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.respBodySize') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS resp_size +FROM + `httparchive.all.requests`, + UNNEST([10, 25, 50, 75, 90, 100]) AS percentile +WHERE + date = '2024-06-01' -- Adjust this date as needed +GROUP BY + client, + percentile, + format, + is_root_page +ORDER BY + format, + client, + is_root_page, + percentile diff --git a/sql/2024/page-weight/response_type_distribution.sql b/sql/2024/page-weight/response_type_distribution.sql new file mode 100644 index 00000000000..21fd85bf54d --- /dev/null +++ b/sql/2024/page-weight/response_type_distribution.sql @@ -0,0 +1,21 @@ +SELECT + client, + percentile, + CAST(JSON_VALUE(summary, '$.type') AS STRING) AS type, + is_root_page, + APPROX_QUANTILES(CAST(JSON_VALUE(summary, '$.respSize') AS INT64) / 1024, 1000)[OFFSET(percentile * 10)] AS resp_size +FROM + `httparchive.all.requests`, + UNNEST([10, 25, 50, 75, 90, 100]) AS percentile +WHERE + date = '2024-06-01' -- Adjust this date as needed +GROUP BY + client, + percentile, + type, + is_root_page +ORDER BY + client, + type, + is_root_page, + percentile diff --git a/src/config/2024.json b/src/config/2024.json index 853e8be8292..f65bbdefb8b 100644 --- a/src/config/2024.json +++ b/src/config/2024.json @@ -119,8 +119,7 @@ "part": "III", "chapter_number": "14", "title": "CMS", - "slug": "cms", - "todo": true + "slug": "cms" }, { "part": "III", diff --git a/src/config/contributors.json b/src/config/contributors.json index 234bc99d2bd..2db2be1e750 100644 --- a/src/config/contributors.json +++ b/src/config/contributors.json @@ -2227,6 +2227,10 @@ ], "2022": [ "authors" + ], + "2024": [ + "analysts", + "authors" ] }, "twitter": "sirjonathan", @@ -2587,6 +2591,17 @@ ] } }, + "LoraRaykova": { + "avatar_url": "166594702", + "github": "LoraRaykova", + "linkedin": "lraykova", + "name": "Lora Raykova", + "teams": { + "2024": [ + "authors" + ] + } + }, "veluca93": { "avatar_url": "1896483", "github": "veluca93", @@ -3149,6 +3164,17 @@ "twitter": "dark_mefody", "website": "https://mefody.dev/" }, + "niko-kaleev": { + "avatar_url": "163424699", + "github": "niko-kaleev", + "linkedin": "niko-kaleev-8760a9131", + "name": "Niko Kaleev", + "teams": { + "2024": [ + "authors" + ] + } + }, "NishuGoel": { "avatar_url": "26349046", "github": "NishuGoel", @@ -3229,6 +3255,7 @@ "authors" ], "2024": [ + "analysts", "leads", "reviewers" ] @@ -3497,6 +3524,16 @@ }, "twitter": "rachellcostello" }, + "raewrites": { + "avatar_url": "7201324", + "github": "raewrites", + "name": "Raelene Morey", + "teams": { + "2024": [ + "reviewers" + ] + } + }, "lebreRafael": { "avatar_url": "13899924", "github": "lebreRafael", @@ -4093,6 +4130,18 @@ "twitter": "tpiros", "website": "https://tamas.io" }, + "karmatosed": { + "avatar_url": "253067", + "github": "karmatosed", + "name": "Tammie Lister", + "teams": { + "2024": [ + "reviewers" + ] + }, + "twitter": "karmatosed", + "website": "https://tammielister.com/" + }, "tammyeverts": { "avatar_url": "15661032", "github": "tammyeverts", diff --git a/src/content/en/2024/cms.md b/src/content/en/2024/cms.md index a63bc37bdf6..2c7eef5e6f6 100644 --- a/src/content/en/2024/cms.md +++ b/src/content/en/2024/cms.md @@ -2,17 +2,774 @@ #See https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide#metadata-to-add-at-the-top-of-your-chapters title: CMS description: CMS chapter of the 2024 Web Almanac covering CMS adoption, user experience of websites running on CMS platforms, and CMS resource weights. -authors: [] -reviewers: [] -editors: [] -analysts: [] +authors: [sirjonathan, LoraRaykova, niko-kaleev] +reviewers: [raewrites, karmatosed] +editors: [tunetheweb] +analysts: [sirjonathan, nrllh] translators: [] +sirjonathan_bio: Jonathan Wold is an Open Web advocate with more than 18 years focused on the WordPress ecosystem. Beyond his love for WordPress, he enjoys reading widely, playing strategy games, acting, rock climbing, and occasionally writing in third-person. +LoraRaykova_bio: Lora is a Content Manager at NitroPack with 8+ years of experience developing in-depth, specialized content for SaaS companies in the CEE region. +niko-kaleev_bio: Niko is a Content Writer at NitroPack with 5+ years of experience in dissecting nuanced topics like hosting, Core Web Vitals, web performance metrics and optimizations. results: https://docs.google.com/spreadsheets/d/118lwQV_GwFYqIxXvsm57oeadJdjAJEOMCRq1PsTqhfs/ -featured_quote: -featured_stat_1: -featured_stat_label_1: -featured_stat_2: -featured_stat_label_2: -featured_stat_3: -featured_stat_label_3: +featured_quote: This year, the industry-wide focus on performance and user experience has deepened, with CMS platforms showing steady improvements across Core Web Vitals and Lighthouse scores. Many CMSs have embraced optimization strategies that enhance loading speed, interactivity, and accessibility, reflecting a shared commitment to a user-first web. +featured_stat_1: 36% +featured_stat_label_1: Percent of mobile sites using WordPress. +featured_stat_2: 49% +featured_stat_label_2: Percent of mobile sites using a CMS. +featured_stat_3: 72% +featured_stat_label_3: Percent of CMS market share that is WordPress --- + +In this chapter, we interpret the evolving landscape of the Content Management System (CMS) and its increasing influence on how users experience content on the web. We aim to explore both the broader CMS ecosystem and the unique characteristics of web pages created through these platforms. + +CMS platforms are pivotal in the collective effort to build a fast, resilient web. By examining their current state, asking critical questions, and identifying areas for future exploration, we can better understand their impact on web performance and user experience. + +This year, we've approached the data with curiosity and expertise in several popular CMSs. We encourage you to view our analysis through the lens of CMS variability and the diverse types of content they support. + +## What is a CMS? + +A **Content Management System (CMS)** is a tool that allows individuals and organizations to create, manage, and publish digital content, particularly on the web. A web-based CMS enables the seamless creation and management of websites while prioritizing user experience for both creators and visitors. + +CMS platforms offer a variety of features for users to build websites, from user-friendly templates to more customizable options that require user input in the design and structure of the site. They also include administrative tools to simplify content management. + +CMSs vary significantly in their approach to site creation. Some offer ready-made templates and drag-and-drop block builders, while others require users to design layouts and site structures. Regardless of approach, a CMS is supported by an ecosystem that typically includes hosting providers, extension developers, web agencies, and site builders. + +In this chapter of the Web Almanac, we explore the entire ecosystem surrounding CMS platforms for 2023 and 2024, respectively. When we refer to a CMS, we mean the platform itself and the associated services and tools that form its ecosystem. + +Based on Wappalyzer's CMS definition, our dataset identifies 249 individual CMS platforms. + +Some CMSs are open source, like WordPress and Joomla, while others are proprietary, such as Wix and Squarespace. These platforms offer hosting options, from free and self-hosted plans to premium, enterprise-level services. + +The CMS landscape is a diverse and interconnected ecosystem, with platforms that differ in functionality, scale, and user experience. + +## CMS Adoption + +Our analysis covers both desktop and mobile websites. While most URLs appeared in both datasets, some were accessed exclusively by desktop or mobile devices. We analyzed desktop and mobile results separately to account for these differences and avoid discrepancies. + +{{ figure_markup( + image="cms-adoption.png", + caption="CMS adoption.", + description="A bar chart of CMS adoption from 2022 to 2024 trending upwards. For desktop CMS's are used by 46% of sites in 2022, 49% of sites in 2023, and 51% of sites in 2024. For mobile it's 48%, 49%, and 51% respectively.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=2013113638&format=interactive", + sheets_gid="310746911", + sql_file="cms_adoption.sql" + ) +}} + +As of June 2024, 51% of the websites in the Web Almanac's desktop dataset were powered by a CMS, a steady increase compared to 2022. The mobile dataset shows an increase from 48% in 2022 to 51% in 2024. + +Looking closer at the raw desktop figures, we see a positive trend, with a clear bump registered in 2023. This is supported by data in both absolute and percentage terms, with the number of desktop URLs tracked by HTTP Archive (and the source CrUX dataset) growing from 5.4 million in July 2022 to 12.7 million in June 2024. The number of tracked mobile URLs, respectively, also reflects a booming growth in mobile device usage, with an increase of 8.6 million mobile URLs in the dataset for 2023 and a slight drop in 2024. + +It's important to note that our analysis differs from other commonly used datasets, such as W3Techs. These deviations are due to differing research methodologies and definitions of what qualifies as a CMS, which impact the final statistics. + +For instance, as mentioned earlier, Wappalyzer uses a more strict definition of a CMS than we do, excluding some significant platforms that appear in W3Tech's reports. You can learn more about our CMS criteria on the [Methodology page](../2022/methodology). + +### CMS adoption by geography + +As of June 2024, CMS adoption worldwide has grown steadily, matching our dataset's increased number of tracked URLs. + +{{ figure_markup( + image="cms-adoption-by-geo.png", + caption="CMS adoption by geo.", + description="A barchart showing United States of America CMS's are used on 40% of desktop and 44% of mobile sites. For India it's 30% and 33% respectively, For Japan 39% and 39%, Germany 33% and 43%, Brazil 31% and 32%, United Kingdom of Great Britain and Northern Ireland 36% and 42%, France 36% and 40%, Russian Federation 37% and 39%, Indonesia 27% and 24% and finally for Italy it's 41% on desktop and 46% on mobile.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=2018893523&format=interactive", + sheets_gid="708001576", + sql_file="cms_adoption_by_geo.sql", + width=600, + height=538 + ) +}} + +This year, unlike our analysis in 2022, we differentiate between countries and regions to offer better insights into geographical CMS usage. + +CMS adoption is highest in Italy and Spain, where 46% to 44% (40% to 41% in 2022) of mobile sites are built with a CMS. Brazil and Indonesia have the lowest adoption rates, with only 32% and 24%, respectively. Japan is seeing steady growth in mobile CMS adoption—39% in 2024 compared to 32% in 2022. Conversely, India shows a slight decrease in adoption (2% since June 2022). This can be attributed to the growing dataset and tracked URL increase, which helps us better understand the Indian web development market. + +The year-over-year (YoY) analysis for mobile results shows consistent growth across countries, putting to rest some of our [2022 speculations](../2022/cms#cms-adoption-by-geography) for a wholesale drop in CMS adoption. + +Let's explore what the CMS adoption rate by region reveals. + +{{ figure_markup( + image="cms-adoption-by-region.png", + caption="CMS adoption by region.", + description="A bar chart showing that in Europe CMS's are used on 41% of desktop sites and 46% of mobile sites. For Americas it's 40% and 42% respectively. For Asia it's 34% and 33%, Oceania 37% and 44%, and finally for Africa it's 35% of desktop and 39% of mobile sites.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=996685882&format=interactive", + sheets_gid="729753765", + sql_file="cms_adoption_by_region.sql" + ) +}} + +Following the trends in the country breakdown, Europe takes the lead with 46% for mobile results in CMS adoption rates. There are no discrepancies in the generated numbers followed by Oceania and the Americas. (44% and 42%, respectively.). It's important to note that North America has a 44% rate of mobile CMS adoption across 1.5 million site pages, as shown in our CMS adoption by subregion graph below. + +{{ figure_markup( + image="cms-adoption-by-subregion.png", + caption="CMS adoption by subregion.", + description="A bar chart showing that in Northern America CMS's are used by 41% of desktop sites and 44% of mobile sites. In Western Europe it's 39% and 46% respectively, Southern Europe 43% and 49%, Eastern Europe 35% and 39%, Eastern Asia 36% and 37%, Northern Europe 38% and 44%, South America 34% and 35%, Southern Asia 30% and 31%, South-Eastern Asia 31% and 29%, Western Asia 29% and 32%, Australia and New Zealand 37% and 44%, Central America 37% and 39%, Southern Africa 37% and 43%, Northern Africa 27% and 31%, Western Africa 27% and 36%, Eastern Africa 32% and 37%, Central Asia 25% and 33%, Caribbean 30% and 37%, Middle Africa 24% and 33%, for Melanesia it's 29% of mobile sites (no desktop data available), and finally for Polynesia it's 27% of mobile sites (again no desktop data available).", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=976092675&format=interactive", + sheets_gid="855626423", + sql_file="cms_adoption_by_subregion.sql", + width=600, + height=701 + ) +}} + +### CMS adoption by rank + +We examined CMS adoption by the estimated rank of the sites included within the dataset. + +{{ figure_markup( + image="top-cms-by-rank.png", + caption="CMS usage by rank.", + description="A bar chart showing that on the top 1,000 of sites CMS's are used by 7% of desktop and 8% of mobile sites. For the top 10,000 it's 16% and 17% respectively. For 100,000 it's 21% and 21%, 1,000,000 it's 28% and 27%, 10,000,000 it's 45% and 45%, and finally for all site's its 49% for both desktop and mobile.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=337512055&format=interactive", + sheets_gid="1821067375", + sql_file="cms_adoption_by_rank_all.sql" + ) +}} + +According to the dataset, CMSs are used by approximately 8% of the top 1,000 websites for both desktop and mobile, even though 49% of all mobile sites in the dataset use a CMS. + +This has been an ongoing trend for the past few years, most likely attributed to business's size relative to its web development needs. Smaller businesses (represented by a large chunk of our dataset here) tend to use popular CMSs for their affordability and usability. In these cases, it's often easy to identify their CMS. + +In contrast, larger businesses with higher-ranking websites often use custom-built CMS solutions that we can't readily identify. They are also more likely to obfuscate the identity of their CMS. It is improbable that more than 90% of the top 1,000 would forgo a CMS entirely.It's much more likely that they don't appear in our dataset. + +Top-ranking websites aside, this year, a significant CMS adoption decrease was observed across all rank groups. The total percentage of websites using a CMS dropped 15% from 39% in 2022, which we suspect is primarily due to the increased size of our dataset in 2024. + +A potentially correlated trend is the adoption of "headless" CMSs and the move to separate content—and the CMS that powers it—from the frontend experience offered to end-users. Another plausible explanation is the smaller size of our dataset compared to the tracked URLs used for the YoY CMS adoption rate, where we observe consistent growth. + +## Most popular CMSs + +Let's look a little more into the top CMS's. + +### Top 5 CMS adoption growth + +Among all websites that use an identifiable CMS, WordPress sites account for the majority of the relative market share—with over 35% adoption on mobile in 2024—followed by Wix (2.8%), Joomla (1.5%), Squarespace (1.5%), and Drupal (1.2%). + +{{ figure_markup( + image="top-cms-yoy.png", + caption="Top 5 CMSs Year on Year.", + description="A bar chart showing WordPress was used on 35.1% in 2022, 34.9% in 2023, and 35.6% in 2024. Wix was used on 2.4%, 2.6%, and 2.8% respectively. Joomla was 1.9%, 1.7%, and 1.5%. Squarespace was 1.3%, 1.4%, and 1.5%, and finally Drupal was 1.4%, 1.3%, and 1.2%.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1804381043&format=interactive", + sheets_gid="738765206", + sql_file="cms_adoption.sql" + ) +}} + +Comparing YoY, Drupal and Joomla continue to decline in market share while Squarespace and Wix grow (0.5% and 0.8%, respectively). WordPress continues its ascent, increasing 0.6% on mobile over 2023-2024 This represents a slower pace of growth than in previous years. + +### CMS adoption share + +This year's chapter includes a new addition where we analyze CMS market share. + +{{ figure_markup( + image="cms-adoption-share.png", + caption="CMS adoption share.", + description="A bar chart showing WordPress is 71.9% of the CMS market on mobile, Wix is 5.7%, Squarespace 3.1%, Joomla 3.0%, Drupal 2.3%, Duda 1.2%, 1C-Bitrix 1.1%, Tilda 1.1%, and following those there is a proliferation of smaller segments.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=538227468&format=interactive", + sheets_gid="738765206", + sql_file="cms_adoption.sql" + ) +}} + +Staying consistent with existing trends and reports, WordPress remains the most popular CMS in the world, with as much as 71.9% of mobile websites leveraging the open-source platform. Next come the proprietary drag-and-drop CMSs Wix and Squarespace (5.7% and 3.1%, respectively), followed by Joomla at 3%. + +While the flexibility, community-driven development, and extensive ecosystem of an open-source CMS such as WordPress contribute to its popularity, it will be interesting to see how proprietary platforms influence adoption numbers in the future—especially given the slower pace of WordPress adoption observed over the past two years. + +## CMS user experience + +With the introduction of Core Web Vitals four years ago, user experience has become a priority. That said, while users were mainly comparing CMS platforms based on ease of use, number of plugins/extensions, and themes available, they added one additional criterion—the default user experience offered by a particular platform. + +To examine these experiences, we gathered data from the Chrome User Experience Report (CrUX) and interrogated three specific metrics: + +- Core Web Vitals +- Lighthouse scores +- Resource weights + +### Core Web Vitals + +Google's Core Web Vitals are a set of three user-centric performance metrics that measure critical aspects of user experience, focusing on loading speed, interactivity, and visual stability: + +- Largest Contentful Paint (loading) +- Interaction to Next Paint (interactivity) +- Cumulative Layout Shift (visual stability) + +Since their introduction in 2020 and becoming a ranking signal in 2021, CWV are now recognized as essential to delivering a good user experience across the web. + +If you're interested in how websites perform against the Core Web Vitals on a larger scale, the [Performance](./performance) chapter covers this topic in greater detail. + +In this section, we are interested in looking at the Core Web Vitals specifically in the context of CMS platforms. + +There are 200+ known CMS platforms, but we narrowed our list to the top 10 most used CMSs, considering they have more than 85% market share. We used the Core Web Vitals Technology Report, which provides a global overview of how different technologies perform in relation to Google's Core Web Vitals. + +Below is the percentage of sites on each platform that score "good" (LCP under 2.5s; INP under 200ms; CLS below 0.1) for all three Core Web Vitals: + +{{ figure_markup( + image="core-web-vitals-yoy.png", + caption="Mobile year-over-year Core Web Vitals performance per CMS.", + description="A bar chart showing WordPress had a 28% pass rate in 2023 and 40% in 2024, Wix had 40% and 57% respectively, Joomla 37% and 45%, Drupal 46% and 56%, Squarespace 33% and 60%, 1C-Bitrix 30% and 45%, Duda 62% and 73%, TYPO3 CMS 63% and 71%, Tilda 28% and 39%, and finally Weebly 40% and 49%.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=867117364&format=interactive", + sheets_gid="216688098", + sql_file="core_web_vitals_yoy.sql", + width=600, + height=559 + ) +}} + +We decided to focus primarily on mobile results for three reasons: + +1. As of July 2024, mobile has a 68.29% global traffic share +2. Mobile devices have resource and connectivity limitations, which paint a more realistic picture of how everyday users experience the web +3. All CMS platforms, and technologies in general, score better on desktop + +Putting that aside, we can see that all 10 CMS platforms improved their Core Web Vitals, with Squarespace leading the board with a whopping 28% YoY improvement. The top 3 include Wix with 18% and 1C-Bitrix with 14%. The list then goes as follows: WordPress (11% YoY), Tilda (11% YoY), Duda (11% YoY), Drupal (10% YoY), and Weebly (10% YoY). At the bottom are TYPO3 CMS with 9% and Joomla with 8%. + +These YoY improvements are as remarkable as the overall Core Web Vitals pass rate the top 10 CMSs collectively provide. For reference, the global CWV pass rate for all origins as of June 2024 is 51%. + +Having platforms like Duda, TYPO3 CMS, and Squarespace with results way north of that is a testament to the efforts these platforms have put into enhancing user experience. + +Now, let's drill into the three Core Web Vitals to see where each platform can improve and which metrics improved the most since 2023. + +#### Largest Contentful Paint (LCP) + +Largest Contentful Paint measures how long it takes for the largest above-the-fold element to load on a page. Anything under 2.5 seconds is considered a "good" LCP score. + +This metric represents how quickly users can see what is likely the most meaningful content on a web page. + +Of the three Core Web Vitals, LCP is the hardest to optimize. That's why LCP pass rates are the lowest and LCP is considered the bottleneck to passing CWVs. + +The reason why LCP is such a challenging metric is that there are a lot of moving parts when it comes to its optimization. You need to: + +1. Ensure the LCP resource starts loading as early as possible. +2. Ensure the LCP element can be rendered as soon as its resource finishes loading. +3. Reduce the load time of the LCP resource as much as you can without sacrificing quality. +4. Deliver the initial HTML document as fast as possible. + +However, the top 10 CMSs showed some impressive results when it comes to their YoY LCP improvements and overall scores: + +{{ figure_markup( + image="lcp-yoy.png", + caption="Mobile year-over-year CMS LCP performance.", + description="Bar chart showing the change in CMS performance in 2023 versus 2024. WordPress had 28% of sites passing LCP in 2023 and 40% in 2024. Wix was 40% and 57% respectively, Joomla 37% and 45%, Drupal 46% and 56%, Squarespace 33% and 60%, 1C-Bitrix 30% and 45%, Duda 62% and 73%, TYPO3 CMS 63% and 71%, Tilda 28% and 39%, and finally Weebly had 40% of sites passing Core Web Vitals in 2023 and 49% in 2024.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1116621071&format=interactive", + sheets_gid="216688098", + sql_file="core_web_vitals_yoy.sql", + width=600, + height=559 + ) +}} + +Before diving into the YoY stats, take note that the global LCP pass rate (as of June 2024) is 63.4%. As you can see from the graph, more than half of the platforms achieve better results. + +Considering how much they have improved since 2023, Squarespace is again ahead of the other CMSs with a YoY improvement of 27%. Wix is in second place with 13%, and WordPress is third with 11%. The remaining platforms improved by less than 10%. + +#### Cumulative Layout Shift (CLS) + +Cumulative Layout Shift (CLS) is a metric used to measure layout stability. It reflects how much content unexpectedly shifts on the screen. + +A website is considered to have good CLS if at least 75% of all site visits score 0.1 or lower. + +{{ figure_markup( + image="cls-yoy.png", + caption="Mobile year-over-year CMS CLS performance.", + description="Bar chart showing change in CMS CLS performance between 2023 and 2024. WordPress improved from 77% sites being good to 82%, Wix from 94% to 87%, Joomla 73% to 77%, Drupal 82% to 86%, Squarespace 72% to 87%, 1C-Bitrix 75% to 79%, Duda 89% to 88%, TYPO3 CMS 83% to 86%, Tilda 87% to 88%, and finally Weebly 66% to 66%.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1756885568&format=interactive", + sheets_gid="216688098", + sql_file="core_web_vitals_yoy.sql", + width=600, + height=559 + ) +}} + +Comparing yearly data shows that the CLS results aren't as impressive as the LCP or the overall CWV pass rates. Most platforms made little progress, while Duda, Wix, and Weebly struggled to improve their 2023 results. + +#### Interaction to Next Paint (INP) + +After being announced in 2023 and in an experimental phase for the rest of the year, Interaction to Next Paint officially replaced First Input Delay (FID) as the new interactivity Core Web Vitals metric on March 12, 2024. + +INP assesses a page's responsiveness to user interactions by observing the latency of all qualifying interactions during a user's visit to a page. The final INP value is the longest interaction observed. + +Simply put, the newest Core Web Vital measures the time from the interaction (for example, a mouse click) until the browser can update (or paint) the screen. + +An INP below or at 200 milliseconds means a page has good responsiveness. + +Considering the whole interaction latency, including input delay, processing time, and presentation delay, the introduction of INP led to a global drop in the Core Web Vitals pass rate. + +That said, the YoY improvement and overall CWV pass rate demonstrated by the top 10 CMSs is even more impressive, considering the big changes INP introduced. + +When it comes to their INP score, the majority of platforms achieve a pass rate of 80% or above: + +{{ figure_markup( + image="inp-yoy.png", + caption="Mobile year-over-year CMS INP performance.", + description="Bar chart showing change in CMS IN performance between 2023 and 2024. WordPress improved from 69% sites being good to 82%, Wix 50% to 85%, Joomla 69% to 79%, Drupal 71% to 83%, Squarespace 85% to 90%, 1C-Bitrix 36% to 60%, Duda 70% to 87%, TYPO3 CMS 86% to 93%, Tilda 44% to 60%, and finally Weebly 68% to 74%.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=670977052&format=interactive", + sheets_gid="216688098", + sql_file="core_web_vitals_yoy.sql", + width=600, + height=559 + ) +}} + +The CMSs that fail to pass include Tilda and 1C-Bitrix, which, despite the YoY improvement, still struggle to achieve the global standard of 84.1%. + +#### The Deprecation of FID + +First Input Delay is no longer a Core Web Vitals metric. Furthermore, Chrome officially deprecated support for FID on September 9, 2024. + +The primary reasons for INP replacing FID include the scope of measurement and comprehensiveness. + +Looking at the Web Almanac's previous editions we can see that all websites had a good FID score on desktop, and nearly all on mobile. This data should indicate that visitors rarely experience a laggy website. + +Unfortunately, the reality is that the web often does have a responsiveness problem. And FID was no longer accurately measuring it. + +The issue with FID was that it only measured the delay for the first input, ignoring the processing time and presentation delay and failing to capture the page's responsiveness throughout the user's entire session. + +In contrast, INP evaluates the responsiveness of the entire page throughout the user's session, providing a more comprehensive and accurate representation of the user experience. + +### Lighthouse + +Lighthouse is an open-source, automated tool designed to improve the quality of web pages by providing a set of audits that evaluate websites based on 4 categories: + +- Performance +- Accessibility +- SEO +- Best Practices + +Lighthouse generates reports with lab data that offer developers actionable suggestions for enhancing website performance. However, it's important to note that Lighthouse scores do not directly impact the real-world field data collected by CrUX. You can further explore how Lighthouse lab scores and field data differ. + +The HTTP Archive runs Lighthouse on mobile and desktop web pages, simulating a [slow 4G connection with throttled CPU performance for mobile](./methodology#lighthouse). + +By analyzing this data, we can gain a different perspective on CMS performance through synthetic tests, which also capture metrics not monitored by CrUX. + +#### Performance score + +The Lighthouse performance score is a weighted average of several scored metrics. + +{{ figure_markup( + image="lighthouse-performance-score.png", + caption="Median Lighthouse performance score.", + description="Bar chart showing the median CMS Performance score for WordPress is 61 on desktop and 38 on mobile, Wix is 85 and 55 respectively, Squarespace 60 and 30, Joomla 58 and 39, Drupal 65 and 40, Duda 80 and 59, 1C-Bitrix 51 and 33, Weebly 71 and 33, TYPO3 CMS 65 and 47, and finally for Tistory it's 54 and 29.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=2144802411&format=interactive", + sheets_gid="14177383", + sql_file="lighthouse_scores_per_cms.sql", + width=600, + height=559 + ) +}} + +Compared to the 2022 results, where the median performance scores for most mobile platforms ranged from about 19 to 35, we observe impressive improvements for both mobile and desktop websites in 2024. + +Wix and Duda stand out as clear leaders with median desktop performance scores of 85 and 80, respectively, and Duda achieving higher scores on mobile. Next come Weebly, Drupal, TYPO3 CMS, WordPress, and Squarespace, representing median performance scores marked with the orange "Needs Improvement" status, according to the Lighthouse color-coding scheme. + +The overall positive trend is due to native and technological improvements in browsers and CMSs, which indicates an overall recognition of the importance of high-quality web performance. + +The major increase shown by proprietary platforms such as Wix and Duda is partly connected to how the CMSs operate—meaning they benefit from a streamlined, centralized development that allows greater speed for innovation in the performance field. + +As we've concluded in previous years, the lower mobile scores are an opportunity for smarter solutions, and optimizations focused on low-end devices with unstable network connections similar to those Lighthouse attempts to emulate. Moreover, it's inherent for mobile devices to fall behind their desktop counterparts, given the faster CPUs and networks available. Nonetheless, the 2024 results are encouraging, and we'll continue to track how CMS platforms fare regarding Lighthouse performance metrics. + +##### Year-over-year performance trends + +{{ figure_markup( + image="lighthouse-mobile-perf-yoy.png", + caption="Median Lighthouse mobile performance score.", + description="Bar chart showing the year on year CMS Performance score over 2023 and 2024. WordPress was 33 in 2023 and 38 in 2024, Wix was 50 and 55, Squarespace 28 and 30, Joomla 35 and 39, Drupal 36 and 40, Duda 56 and 59, 1C-Bitrix 31 and 33, Tilda 36 and 37, TYPO3 CMS 42 and 47, Weebly 32 and 33", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=270170798&format=interactive", + sheets_gid="1754565121", + sql_file="lighthouse_scores_per-cms_yoy.sql", + width=600, + height=559 + ) +}} + +The YoY performance data from 2023 to 2024 reveals an encouraging trend of incremental improvements among top CMS platforms. Duda and Wix continue to lead in mobile performance, with Duda improving from a median Lighthouse score of 56 to 59 and Wix rising from 50 to 55. WordPress also shows improvement, increasing from 33 to 38, alongside Joomla and Drupal, which moved from 35 to 39 and 36 to 40, respectively. These results reflect a broader industry focus on optimizing mobile performance, although some platforms, such as Squarespace and Weebly, showed only minor gains. These varied improvements highlight the ongoing challenges and priorities across CMS platforms as they work toward enhanced user experiences on mobile devices. + +#### SEO score + +Search Engine Optimization (or SEO) is the practice of improving the quality and quantity of visitors to a website or a web page from a website to make it more easily found in search engines. This topic is covered in our [SEO chapter](../2022/seo), but it also relates to CMSs. + +A CMS and content on it is generally set up to serve as much information to search engine crawlers as possible to make it as easy as possible for them to index site content appropriately in search engine results. Compared to a custom-built website, one might expect a CMS to provide good SEO capabilities, and the Lighthouse scores in this category remain appropriately high. + +{{ figure_markup( + image="lighthouse-seo-score.png", + caption="Median Lighthouse SEO score.", + description="Bar chart showing the median CMS SEO score for WordPress is 92 on desktop and 92 on mobile, Wix is 100 and 100 respectively, Squarespace 92 and 92, Joomla 92 and 92, Drupal 85 and 85, Duda 92 and 92, 1C-Bitrix 92 and 92, Weebly 85 and 91, TYPO3 CMS 92 and 92, and finally for Tistory it's 92 and 85.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1386400078&format=interactive", + sheets_gid="14177383", + sql_file="lighthouse_scores_per-cms.sql", + width=600, + height=559 + ) +}} + +The median SEO scores in the top 10 platforms range from 85-100, an impressive increase [from 82-92 in 2022](../2022/cms#seo-score). Given the high median performance scores, it is no surprise Wix takes the lead in SEO as well, scoring a perfect 100 for both mobile and desktop. With median scores as high as 92 for mobile and desktop, the runner-ups provide users with robust SEO best practices. + +##### Year-over-year SEO trends + +{{ figure_markup( + image="lighthouse-mobile-seo-yoy.png", + caption="Median Lighthouse mobile SEO score.", + description="Bar chart showing the year on year CMS SEO score over 2023 and 2024. WordPress was 90 in 2023 and 92 in 2024, Wix was 97 and 100, Squarespace 93 and 92, Joomla 88 and 92, Drupal 85 and 85, Duda 86 and 92, 1C-Bitrix 86 and 92, Tilda 91 and 100, TYPO3 CMS 89 and 92, and finally Weebly 85 and 91", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=61098748&format=interactive", + sheets_gid="1754565121", + sql_file="lighthouse_scores_per-cms_yoy.sql", + width=600, + height=559 + ) +}} + +The year-over-year comparison from 2023 to 2024 reveals consistently high SEO scores across the top CMS platforms, with most maintaining or slightly improving their median scores. This stability at the high end suggests that CMS platforms are prioritizing SEO best practices, ensuring that users have solid foundations for search engine visibility. + +#### Accessibility score + +An accessible website is a site designed and developed so that people with disabilities can use them. Web accessibility also benefits people without disabilities, such as those on slow internet connections. Read more in our [Accessibility chapter](../2022/accessibility). + +Lighthouse provides a set of accessibility audits and returns a weighted average of all of them. See scoring details for a full list of how each audit is weighted. + +Each accessibility audit is either a pass or a fail, but unlike other Lighthouse audits, a page doesn't get points for partially passing an accessibility audit. For example, if some elements have screen reader-friendly names but others don't, that page gets a zero for the screen reader-friendly names audit. + +{{ figure_markup( + image="lighthouse-a11y-score.png", + caption="Median Lighthouse mobile accessibility score.", + description="Bar chart showing the median CMS Accessibility score for WordPress is 86 on desktop and 86 on mobile, Wix is 95 and 94 respectively, Squarespace 93 and 94, Joomla 83 and 83, Drupal 86 and 85, Duda 89 and 88, 1C-Bitrix 75 and 75, Weebly 86 and 86, TYPO3 CMS 84 and 84, and finally for Tistory it's 78 and 74.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=476143776&format=interactive", + sheets_gid="14177383", + sql_file="lighthouse_scores_per-cms.sql", + width=600, + height=559 + ) +}} + +In 2024, the median Lighthouse accessibility score for the top 10 CMSs ranges between 74 and 95, [a slight improvement from 77 to 91 in 2022](../2022/cms#accessibility-score). Squarespace has lost the top space by a fraction to Wix, which hits the 94 and 95 marks for mobile and desktop, respectively. 1C-Bitrix had the lowest accessibility scores in 2024 and shows a slight decrease of 2 points for both desktop and mobile, perhaps reflecting that the same sites are delivered to both desktop and mobile devices. + +##### Year-over-year accessibility trends + +{{ figure_markup( + image="lighthouse-mobile-a11y-yoy.png", + caption="Median Lighthouse mobile accessibility score.", + description="Bar chart showing the year on year CMS Accessibility score over 2023 and 2024. WordPress was 87 in 2023 and 86 in 2024, Wix was 94 and 94, Squarespace 92 and 94, Joomla 84 and 83, Drupal 87 and 85, Duda 88 and 88, 1C-Bitrix 77 and 75, Tilda 81 and 84, TYPO3 CMS 86 and 84, and finally Weebly 86 and 86.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=476143776&format=interactive", + sheets_gid="1754565121", + sql_file="lighthouse_scores_per-cms_yoy.sql", + width=600, + height=559 + ) +}} + +The 2023 to 2024 comparison reveals largely stable accessibility scores across top CMS platforms, with most showing minimal changes. Wix shares the lead with Squarespace, holding steady with a high score of 94 for both years. Squarespace improved from 92 in 2023 to match Wix's 94 in 2024. Notably, WordPress, Joomla, Drupal, and TYPO3 all saw minor declines. These scores suggest a steady emphasis on accessibility across the proprietary CMSs, with the open source CMSs demonstrating room for improvement. + +#### Best practices + +Lighthouse's best practices audit evaluates whether web pages adhere to widely accepted web standards across various metrics. These include critical factors such as: + +- HTTPS support, +- console error elimination, +- deprecated APIs avoidance, +- browser compatibility optimization, +- security protocols, +- and more. + +By following these best practices, developers can enhance both the functionality and user experience of their websites, ensuring a more secure, stable, and reliable performance across different browsers and devices. + +{{ figure_markup( + image="lighthouse-best-practices-score.png", + caption="Median Lighthouse best practices score.", + description="Bar chart showing the median CMS Best Practice score for WordPress is 78 on desktop and 79 on mobile, Wix is 78 and 79 respectively, Squarespace 100 and 96, Joomla 78 and 79, Drupal 78 and 79, Duda 78 and 79, 1C-Bitrix 56 and 57, Weebly 56 and 57, TYPO3 CMS 96 and 96, and finally for Tistory it's 74 and 79.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1321714408&format=interactive", + sheets_gid="14177383", + sql_file="lighthouse_scores_per-cms.sql", + width=600, + height=559 + ) +}} + +Our 2024 analysis shows significant changes across the board compared to the results in 2022. Squarespace takes the lead from Wix, with the highest median best practices score of 100, while many of the other top 10 platforms share a score of 78 (a slight improvement since 2022). + +While most other CMSs show worse numbers in the best practices audits, TYPO3 CMS claims the second place with a 96-median score for both mobile and desktop, compared to 83 and 92 (mobile and desktop, respectively) in 2022. + +##### Year-over-year Best Practices Trends + +{{ figure_markup( + image="lighthouse-mobile-best-practices-yoy.png", + caption="Median Lighthouse mobile best practices score.", + description="Bar chart showing the year on year CMS Best Practice score over 2023 and 2024. WordPress was 92 in 2023 and 79 in 2024, Wix was 92 and 79, Squarespace 92 and 96, Joomla 83 and 79, Drupal 83 and 79, Duda 92 and 79, 1C-Bitrix 75 and 57, Tilda 83 and 79, TYPO3 CMS 92 and 96, and finally Weebly was 83 and 57.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=10302778&format=interactive", + sheets_gid="1754565121", + sql_file="lighthouse_scores_per-cms_yoy.sql", + width=600, + height=559 + ) +}} + +The YoY comparison from 2023 to 2024 shows stable best practices scores across most CMS platforms. Squarespace and TYPO3 CMS share the top position in 2024, each with a best practices score of 96. Most other platforms, including WordPress, Wix, Joomla, Drupal, Duda, and Tilda, maintained steady scores of 79, reflecting consistent adherence to web standards. In contrast, 1C-Bitrix and Weebly scored lower at 57, highlighting areas where these platforms could improve in best practices compliance. + +## Resource weights + +We leveraged HTTP Archive data to analyze the resource weight across various CMS platforms, aiming to uncover opportunities for performance optimization. While page loading speed isn't solely determined by the number of downloaded bytes, reducing the amount of data required to load a page offers several advantages. + +Fewer bytes mean lower bandwidth costs, reduced carbon emissions, and faster performance—particularly for users on slower connections. This analysis sheds light on areas where resource optimization can have a meaningful impact on both user experience and sustainability. Read the [Page Weight chapter](../2022/page-weight) for a more detailed analysis. + +{{ figure_markup( + image="median-cms-page-weight.png", + caption="Median CMS page weight.", + description="Bar chart showing median page weight for popular CMSs. WordPress has a median of 2,252 KB on desktop and 2,047 KB on mobile, Wix 2,560 and 2,215, Squarespace 3,323 and 3,015, Joomla 2,133 and 2,035, and finally Drupal is 1,903 KB on desktop and 1,762 KB on mobile.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=255848791&format=interactive", + sheets_gid="1442275519", + sql_file="resource_weights.sql" + ) +}} + +Although we observed a steady trend in increasing page weight over the past several years, in 2024, almost all top five CMSs show notable improvements. Drupal's median page weight has dropped to ~1.7 MB compared to ~2.1 MB in 2022. WordPress and Joomla now hover closely to ~2 MB compared to ~2.3 MB in 2022. Wix is the only CMS on the board that shows a slight increase in median page weight—2.2 MB compared to 2.1MB in 2022. Squarespace continues to deliver the heaviest median page weight of ~3 MB compared to ~3.5MB in 2022. + +{{ figure_markup( + image="cms-page-weight-distribution.png", + caption="Distribution of CMS page weight.", + description="Bar chart showing page weight in Killobyes (KB) at various percentiles. WordPress is 598 KB at 10th percentile, 1,101 KB at 25th percentile, 2,047 KB at 50th percentile, 3,959 KB at 75th percentile, and 7,826 KB at 90th percentile. Wix is 1,217 KB, 1,565 KB, 2,215 KB, 3,322 KB, and 6,369 KB respectively. Squarespace is 1,594 KB, 2,076 KB, 3,015 KB, 5,013 KB, 9,404 KB. Joomla is 561 KB, 1,021 KB, 2,034 KB, 4,303 KB, 9,052 KB. Drupal is 524 KB, 937 KB, 1,762 KB, 3,500 KB, 7,160 KB.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1457951957&format=interactive", + sheets_gid="2016584461", + sql_file="page_weight_distribution.sql" + ) +}} + +The distribution of page weight in each platform's percentiles is substantial. Page weight is probably related to the differences in user content across web pages, the number of images used, plugins installed, etc. The smallest pages delivered per platform come from Drupal, followed closely by WordPress—both improving on their results from 2022 (2.1 MB and 2.3 MB, respectively). + +This year, Drupal only sends 524 KB for their 10th percentile of visits, while Joomla and WordPress are not falling far behind—561 KB and 598 KB, respectively. With a notable decrease, but still serving the largest pages here, is Squarespace, with ~9.4 MB delivered for their 90th percentile of visits, a ~2 MB decrease compared to 2022 data. + +### Page weight breakdown + +Page weight refers to the total size, measured in kilobytes, of all the resources loaded on a web page. These resources—such as images, JavaScript, CSS, HTML, and fonts—collectively influence the page's performance. + +Below, we analyze and compare the resource weight across different CMS platforms, providing insights into how each CMS contributes to the overall page weight. + +#### Images + +Images are a significant resource on most websites, often accounting for the largest portion of page weight. In CMS platforms, where visuals are heavily relied upon for design and engagement, image optimization is essential. High-resolution images can slow down page load times if not properly compressed or served in modern formats like WebP. Read more in our [Media subchapter](../2022/media). + +{{ figure_markup( + image="cms-size-of-images.png", + caption="Median CMS size of images.", + description="Bar chart showing median image weight for popular CMSs. WordPress has a median of 833 KB on desktop and 725 KB on mobile, Wix 312 and 152 respectively, Squarespace 1,226 and 921, Joomla 1,035 and 988, and finally Drupal is 741 KB on desktop and 653 KB on mobile.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1544422290&format=interactive", + sheets_gid="1442275519", + sql_file="resource_weights.sql" + ) +}} + +In 2024, Wix continues to deliver substantially fewer image bytes, with only 152 KB delivered for the median of mobile views (138 KB less than in 2022). This suggests good use of image compression and lazy image loading. All the other top four platforms deliver below 1 MB of images—a significant improvement compared to 2022 data (WordPress 1,1 MB; Squarespace ~1,7 MB, Joomla ~1,5 MB, and Drupal ~1,1 MB). + +Advanced image formats greatly improve compression, enabling resource savings and faster site loading. WebP is commonly supported in all major browsers today, with over 95% support. In addition, newer image formats continue to gain popularity and adoption, namely AVIF. + +We can examine the usage of the different image formats across the top CMSs: + +{{ figure_markup( + image="image-format-popularity-by-cms.png", + caption="Image format popularity by CMS for mobile.", + description="Stacked bar chart of image format popularity across various CMSs. Most have 30-50% jpg, with 30% png, 10-20% gif, and less than 10% for webp, svg, ico, and avif. The exceptions are Wix with a large amount (70%) of webp, and Duda simialr with 46% webp.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1032342538&format=interactive", + sheets_gid="809952267", + sql_file="image_format_popularity.sql", + width=600, + height=556 + ) +}} + +In 2024, Wix and Duda continue to make the most use of WebP, at ~75% and ~60% adoption, respectively, while the rest show minor increases. + +Although WebP is now widely supported, we still observe that platforms are underutilizing the format. With the growing support of WebP, it seems all platforms have work to do to reduce the usage of the older JPEG and PNG formats without compromising on image quality. + +As of WordPress 6.1, the WebP format conversion is automatic for all WordPress websites. However, the popularity of the format seems to have plateaued compared to the 2022 data. This can be explained by the more holistic approach the core Performance team at WordPress has chosen toward general performance improvements on the platform. Read more in the section [WordPress in 2024](#wordpress-in-2024). + +#### JavaScript + +JavaScript powers much of the interactive functionality on modern websites. CMS platforms frequently use various JS libraries and frameworks to enable features like dynamic content loading, form validation, and user engagement tools. However, excessive or poorly optimized JavaScript can negatively impact performance. Find more detailed information in our [JavaScript subchapter](../2022/javascript). + +{{ figure_markup( + image="cms-size-of-js.png", + caption="Median CMS size of JS.", + description="Bar chart showing median JavaScript weight for popular CMSs. WordPress has a median of 565 KB on desktop and 528 KB on mobile, Wix 1,461 and 1,462 respectively, Squarespace 1,309 and 1,314, Joomla 409 and 386, and finally Drupal is 479 KB on desktop and 471 KB on mobile.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1698213507&format=interactive", + sheets_gid="1442275519", + sql_file="resource_weights.sql" + ) +}} + +In 2024, we observe rising JavaScript usage across the board. Almost all top five CMSs deliver more JavaScript compared to 2022 data, with Squarespace seeing a major increase, from 997 KB to ~1,3 MB. Wix still delivers the most JavaScript with a slight increase, from ~1,3 MB to ~1,4 MB. Drupal and WordPress show minor JavaScript growth, with Joomla delivering the least JS at 409 KB (an improvement from 2022's 452KB). + +#### HTML + +HTML forms the structural backbone of any web page, defining the layout and content. CMS platforms automatically generate much of the HTML code, sometimes leading to bloated and inefficient markup. While HTML is typically lightweight compared to other resources, unoptimized or overly complex HTML structures can still affect render time and user experience. Find more detailed information in the [Markup subchapter](../2022/markup). + +{{ figure_markup( + image="cms-size-of-html.png", + caption="Median CMS size of HTML.", + description="Bar chart showing median html weight for popular CMSs. WordPress has a median of 40 KB on desktop and 38 KB on mobile, Wix 142 and 143 respectively, Squarespace 25 and 25, Joomla 19 and 18, and finally Drupal is 20 KB and 20 KB.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=417293866&format=interactive", + sheets_gid="1442275519", + sql_file="resource_weights.sql" + ) +}} + +Examining the HTML document sizes, we can see that most of the top CMSs deliver a median HTML size of ~22 KB–38 KB. The only exception is Wix, which delivers ~142 KB, a notable increase over 2022's results. This may suggest extensive use of inlined resources and shows an area that can be further improved. + +#### CSS + +CSS controls the visual styling of a website, dictating elements like layout, colors, and fonts. On CMS platforms, themes and templates often come with extensive CSS files that may include unused or redundant styles. Large CSS files can increase page weight and slow down rendering times. Read more in the [CSS subchapter](../2022/css). + +{{ figure_markup( + image="cms-size-of-css.png", + caption="Median CMS size of CSS.", + description="Bar chart showing median CSS weight for popular CMSs. WordPress has a median of 121 KB on desktop and 118 KB on mobile, Wix 12 and 5 respectively, Squarespace 133 and 133, Joomla 89 and 86, and finally Drupal is 72 KB on desktop and 70 KB on mobile.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=2059559160&format=interactive", + sheets_gid="1442275519", + sql_file="resource_weights.sql" + ) +}} + +In 2024, we see a different distribution between platforms that strengthens the case for inlining CSS. Wix delivers the fewest CSS resources, dropping from 9 KB to 5 KB on mobile views in 2022. Squarespace delivers significantly more CSS this year—133 KB from 89 KB in 2022. WordPress comes second in CSS delivery with a slight increase from 2022 numbers. Drupal also shows a minor increase, while Joomla is the only CMS platform that delivers less CSS in 2024. + +#### Fonts + +CMS-based websites frequently offer a variety of fonts to enhance branding and visual appeal. However, fonts can introduce additional weight to a page, especially when multiple font families or variations are loaded. Unoptimized font loading can delay text rendering and impact the user experience. Explore the [Fonts subchapter](../2022/fonts) for a detailed breakdown. + +{{ figure_markup( + image="cms-size-of-fonts.png", + caption="Median CMS size of fonts.", + description="Bar chart showing median font weight for popular CMSs. WordPress has a median of 182 KB on desktop and 152 KB on mobile, Wix 154 and 125 respectively,Squarespace 184 and 169, Joomla 120 and 100, and finally Drupal is 123 KB on desktop and 104 KB on mobile.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=655172650&format=interactive", + sheets_gid="1442275519", + sql_file="resource_weights.sql" + ) +}} + +This year, all top five CMSs show changes in the amount of font bytes delivered. Squarespace continues to deliver the highest amount at 169 KB (a significant decrease from 202 KB in 2022). Wix also shows a slight decrease in font file delivery, while WordPress, Joomla, and Drupal all have increased the amount of font bytes served. It would be interesting to see if the growing integration of Google-hosted fonts will impact next year's results. + +## WordPress in 2024 + +{{ figure_markup( + caption="Percentage of mobile sites using WordPress.", + content="36%", + classes="big-number", + sheets_gid="1621293918", + sql_file="top-cms-by-geo.sql" +) +}} + +Of the over 16 million mobile sites in this year's crawl, WordPress is used by 5.7 millions sites for a total of 36% of sites. By comparison, the next closest CMS is Wix, with 456,253 sites or 3% of sites. + +WordPress's global dominance stems from two main factors—a community that maintains and improves the functionality of the open-source project, and the CMS's flexibility in serving a wide range of websites and users. + +Furthermore, the availability of tens of thousands of plugins, themes, and page builders allows users from all kinds of technical backgrounds to choose WordPress as their go-to CMS option. However, these easy ways to expand functionality can be a double-edged sword, especially with regards to performance. + +In the following section, we review page builder adoption,along with improvements introduced by the Core Performance Team. + +### Page builders + +{{ figure_markup( + image="top-5-page-builders.png", + caption="Top 5 page builders.", + description="Bar chart showing the top 5 page builders used on sites. Elementor is used on 54% of desktop sites and 56% on mobile, wpBakery is 21% and 21% for both, Divi 14% for both, SiteOrigin Page Builder is 2% for both, and finally Oxygen is 1% for both desktop and mobile.", + chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1601231589&format=interactive", + sheets_gid="1497515207", + sql_file="wordpress_page_builders.sql" + ) +}} + +WordPress users often leverage a "page builder" that provides an interface within the CMS for content management. Thanks to the improvement of Wappalyzer's detection methods, we can follow page builder adoption trends compared to our 2022 results. + +We discovered that of the WordPress sites attributed to a page builder, Elementor and WPBakery remain the clear winners (13% and 12% increase for mobile, respectively), with Divi, SiteOrigin, and Oxygen trailing behind. + +As we see it today, page builders can significantly influence a site's performance. Historically, page builders have been anecdotal indicators of poor performance. As one example, our dataset indicates that it's not uncommon for websites to have multiple page builders installed, significantly increasing the resources loaded by a site. + +Thanks to native performance improvements and advancements, however, page builders tend to offer leaner alternatives, which are becoming increasingly popular among site owners. Paired with best practices when developing a website, they can now achieve better overall performance in WordPress, more of which we cover in the next section. + +### Latest performance improvements in WordPress + +The WordPress Core Performance Team monitors, enhances, and promotes performance in WordPress core and its surrounding ecosystem. The group was established in 2021 to increase the performance of WordPress Core, which in turn improved the performance of the average WordPress site. + +Fast forward to 2024, and it's safe to say the team has exceeded expectations, merging in a significant number of performance updates across each major release of WordPress. + +Furthermore, since they first kicked off the project in November 2021, WordPress's overall Core Web Vitals pass rate has surged by 12%. + +{{ figure_markup( + image="wordpress-cwv-pass-trend.png", + caption="Trend of WordPress Core Web Vitals pass rates", + description="Line graph showing the increase of WordPress origins passing Core Web Vitals from less than 15% in January 2020 and increasing fairly steadily up to 41% in July 2024.", + width=1752, + height=888 + ) +}} + +These are some of the enhancements that led to these results: + +- **WordPress 6.0**: Improvements to the WordPress Caching API, taxonomy term queries, and performance increase for sites with large user counts +- **WordPress 6.3**: More than 170 performance updates merged into the core, improvements in LCP and TTFB for block and classic themes, added support for the *fetchpriority="high"* attribute on images, introduced script loading strategies, which adds support for loading scripts with defer or async. +- **WordPress 6.4:** Merged over 100 performance updates and implemented script loading strategies for frontend scripts in core and bundled themes. +- **WordPress 6.5: **Introduced multiple performance improvements, including support for the AVIF image format and a faster localization system. + +The team also released the Performance Lab plugin, which is a collection of performance-related "feature projects" that may eventually be merged into the WordPress core software: + +- Image Placeholders +- Modern Image Formats +- Performant Translations +- Embed Optimizer (experimental) +- Enhanced Responsive Images (experimental) +- Image Prioritizer (experimental) + +Speculative Loading is another plugin that is part of the Performance Lab and has been recently made available. This plugin enables support for the [Speculation Rules API](https://developer.mozilla.org/docs/Web/API/Speculation_Rules_API), allowing the definition of rules to dynamically prefetch or prerender specific URLs based on user interactions. We discuss this [API more in the next section](#speculation-rules-api). By default, it is set to prerender WordPress frontend URLs when a user hovers over a relevant link, allowing users to experience instant page load times. + +Since its release, the plugin's adoption has steadily grown, reaching over 30,000 active installations as of this chapter's writing. + +## Emerging trends and technologies + +Although we didn't have enough data regarding adoption and real-world impact to add to this year's edition, some emerging technologies promise to boost the overall performance of all CMS platforms and the web as a whole. + +That's why we decided to include them still, keep an eye on them, and revisit their impact in 2025. + +### Speculation Rules API + +The Speculation Rules API is a JSON-defined API developed by Google to enhance the performance of subsequent page navigation, leading to faster rendering times and improved user experiences. We already saw how the [Speculative Loading WordPress plugin](#latest-performance-improvements-in-wordpress) made use of this in the previous section. + +This API enables developers to specify which URLs should be dynamically prefetched or prerendered: + +- **Prefetching**: Fetches resources (like pages or assets) in the background before they are requested by the user, reducing load time when the user eventually navigates to the prefetched content. +- **Prerendering**: Fully renders a page in the background, so it is immediately available with no load time when the user navigates to it. + +Furthermore, the API improves performance based on user behaviors, such as hovering over links or predicted navigation patterns, allowing content to load more quickly when needed. + +To fine-tune when speculations should fire, developers can adjust the "eagerness" setting: + +- **Eager**: Speculation rules are triggered immediately when conditions are met. +- **Moderate**: Speculation occurs after a short delay, such as when a user hovers over a link for at least 200 milliseconds, indicating some level of intent. +- **Conservative**: Speculation is triggered only with more definitive user actions, such as tapping or clicking on a link, signaling a higher likelihood of navigation. + +These eagerness levels allow developers to balance performance optimization with resource management, ensuring that the browser preloads or prerenders content at appropriate times. + +### Long Animation Frames API (LoAF) + +The Long Animation Frames API (LoAF) is designed to improve upon the Long Tasks API. It was shipped with Chrome 123 and provides developers with more actionable insights to address responsiveness issues and improve Interaction to Next Paint (INP). + +Responsiveness refers to how quickly a page reacts to user interactions, ensuring updates are painted without delay. For INP, a response time under 200 milliseconds is ideal, though even shorter times may be necessary for animations. + +Instead of measuring individual tasks, LoAF focuses on long animation frames, defined as frames that take longer than 50 milliseconds to render, helping identify blocking work more effectively. + +### Artificial Intelligence (AI) + +Artificial Intelligence (AI) is reshaping how users build, manage, and optimize websites. AI-driven tools and plugins are becoming more prevalent, enabling automation, personalization, and enhanced user experiences. + +Regarding the WordPress ecosystem, it seems like the community has yet to fully embrace the AI trend. In a thread from May 2023, the core WordPress team and contributors exchanged opinions about the role of AI in the CMS. + +Following the discussion, several highlights stand out: + +- **AI should remain in the plugin space:** Since AI integrations currently rely on third-party systems and pricing, it's more likely to be adopted through plugins rather than Core—at least until AI models are fast enough to run directly on servers. +- **Developer Experience (DX) as a focus for innovation:** Some suggest that addressing current DX limitations, especially in the block editor, should be a priority. Enhancing extensibility could allow plugins more freedom to experiment with AI integrations. +- **AI for collaboration:** Others propose using AI to enhance collaboration and workflows, such as adding AI chatbots as a new user type as part of Phase 3 of the Gutenberg roadmap. A bolder idea is integrating a personal AI assistant into the admin panel for business support. + +WordPress core aside, AI has been adopted by numerous plugins that offer content generation, personalization, chatbots, and more. So, it's safe to say that AI has already started changing the WordPress ecosystem. + +## Conclusion + +CMS platforms have continued their upward trajectory in 2024, becoming increasingly integral to the fabric of the internet as they support a diverse range of content creators, businesses, and users worldwide. With adoption rates steadily rising, CMSs are not only shaping how people create and manage content but also enhancing how users experience and engage with the web. + +This year, the industry-wide focus on performance and user experience has deepened, with CMS platforms showing steady improvements across Core Web Vitals and Lighthouse scores. Many CMSs have embraced optimization strategies that enhance loading speed, interactivity, and accessibility, reflecting a shared commitment to a user-first web. The adoption of Interaction to Next Paint (INP) as a Core Web Vital has given us a more comprehensive measure of responsiveness, a new standard for page load times, and higher expectations for browsing experiences across devices and network conditions. + +Challenges persist, however. As CMSs expand their capabilities and adopt new technologies, balancing added functionality with performance remains crucial. Issues such as page weight and JavaScript load continue to impact some platforms, especially on mobile, underscoring the importance of ongoing optimization and adherence to best practices. + +Looking ahead, we're excited to see how CMSs will continue to evolve, with emerging technologies like AI transforming content creation and speculative loading improving performance. Although they're still in their early stages of development, these new technologies have the potential to redefine web performance and engagement. As we expand our datasets and refine our methodologies, we'll aim to provide an even clearer picture of the state of the web — and the CMS. Here's to a faster, more accessible, and user-friendly web—let's keep making it better together. diff --git a/src/static/css/page.css b/src/static/css/page.css index 324ec2c36ea..450bf2a949e 100644 --- a/src/static/css/page.css +++ b/src/static/css/page.css @@ -292,6 +292,7 @@ } .authors, +.citation-box h2, .authors h2, .chapter-links, .chapter-links h2, @@ -382,6 +383,18 @@ margin-right: 0.25rem; } +.citation-box pre { + padding: 16px; + border: 1px solid #e0e0e0; + border-radius: 4px; + box-shadow: 0 1px 3px rgba(0, 0, 0, 0.1); + font-family: monospace; + background-color: #f9f9f9; + overflow-x: auto; + white-space: pre-wrap; /* Allow wrapping of long lines */ + margin: 0; +} + #chapter-navigation { padding: 16px 36px 50px 36px; padding: 1rem 2.25rem 3.125rem 2.25rem; diff --git a/src/static/images/2024/cms/cls-yoy.png b/src/static/images/2024/cms/cls-yoy.png new file mode 100644 index 00000000000..63ae474bfd0 Binary files /dev/null and b/src/static/images/2024/cms/cls-yoy.png differ diff --git a/src/static/images/2024/cms/cms-adoption-by-geo.png b/src/static/images/2024/cms/cms-adoption-by-geo.png new file mode 100644 index 00000000000..3ed63ee1de3 Binary files /dev/null and b/src/static/images/2024/cms/cms-adoption-by-geo.png differ diff --git a/src/static/images/2024/cms/cms-adoption-by-region.png b/src/static/images/2024/cms/cms-adoption-by-region.png new file mode 100644 index 00000000000..6885509b701 Binary files /dev/null and b/src/static/images/2024/cms/cms-adoption-by-region.png differ diff --git a/src/static/images/2024/cms/cms-adoption-by-subregion.png b/src/static/images/2024/cms/cms-adoption-by-subregion.png new file mode 100644 index 00000000000..b2cd946c9e9 Binary files /dev/null and b/src/static/images/2024/cms/cms-adoption-by-subregion.png differ diff --git a/src/static/images/2024/cms/cms-adoption-share.png b/src/static/images/2024/cms/cms-adoption-share.png new file mode 100644 index 00000000000..1a4b06362a3 Binary files /dev/null and b/src/static/images/2024/cms/cms-adoption-share.png differ diff --git a/src/static/images/2024/cms/cms-adoption.png b/src/static/images/2024/cms/cms-adoption.png new file mode 100644 index 00000000000..96f3e500b62 Binary files /dev/null and b/src/static/images/2024/cms/cms-adoption.png differ diff --git a/src/static/images/2024/cms/cms-page-weight-distribution.png b/src/static/images/2024/cms/cms-page-weight-distribution.png new file mode 100644 index 00000000000..5ee3da12f9c Binary files /dev/null and b/src/static/images/2024/cms/cms-page-weight-distribution.png differ diff --git a/src/static/images/2024/cms/cms-size-of-css.png b/src/static/images/2024/cms/cms-size-of-css.png new file mode 100644 index 00000000000..28150754750 Binary files /dev/null and b/src/static/images/2024/cms/cms-size-of-css.png differ diff --git a/src/static/images/2024/cms/cms-size-of-fonts.png b/src/static/images/2024/cms/cms-size-of-fonts.png new file mode 100644 index 00000000000..1fbe332c2c8 Binary files /dev/null and b/src/static/images/2024/cms/cms-size-of-fonts.png differ diff --git a/src/static/images/2024/cms/cms-size-of-html.png b/src/static/images/2024/cms/cms-size-of-html.png new file mode 100644 index 00000000000..7eb6144dea0 Binary files /dev/null and b/src/static/images/2024/cms/cms-size-of-html.png differ diff --git a/src/static/images/2024/cms/cms-size-of-images.png b/src/static/images/2024/cms/cms-size-of-images.png new file mode 100644 index 00000000000..04ebd3d31bf Binary files /dev/null and b/src/static/images/2024/cms/cms-size-of-images.png differ diff --git a/src/static/images/2024/cms/cms-size-of-js.png b/src/static/images/2024/cms/cms-size-of-js.png new file mode 100644 index 00000000000..a40511ba8ce Binary files /dev/null and b/src/static/images/2024/cms/cms-size-of-js.png differ diff --git a/src/static/images/2024/cms/core-web-vitals-yoy.png b/src/static/images/2024/cms/core-web-vitals-yoy.png new file mode 100644 index 00000000000..cdeb6d3f2b1 Binary files /dev/null and b/src/static/images/2024/cms/core-web-vitals-yoy.png differ diff --git a/src/static/images/2024/cms/image-format-popularity-by-cms.png b/src/static/images/2024/cms/image-format-popularity-by-cms.png new file mode 100644 index 00000000000..ece424d249b Binary files /dev/null and b/src/static/images/2024/cms/image-format-popularity-by-cms.png differ diff --git a/src/static/images/2024/cms/inp-yoy.png b/src/static/images/2024/cms/inp-yoy.png new file mode 100644 index 00000000000..a273ba6bbc3 Binary files /dev/null and b/src/static/images/2024/cms/inp-yoy.png differ diff --git a/src/static/images/2024/cms/lcp-yoy.png b/src/static/images/2024/cms/lcp-yoy.png new file mode 100644 index 00000000000..3818e86fb9b Binary files /dev/null and b/src/static/images/2024/cms/lcp-yoy.png differ diff --git a/src/static/images/2024/cms/lighthouse-a11y-score.png b/src/static/images/2024/cms/lighthouse-a11y-score.png new file mode 100644 index 00000000000..8f64aed1815 Binary files /dev/null and b/src/static/images/2024/cms/lighthouse-a11y-score.png differ diff --git a/src/static/images/2024/cms/lighthouse-best-practices-score.png b/src/static/images/2024/cms/lighthouse-best-practices-score.png new file mode 100644 index 00000000000..3d5b802f4ed Binary files /dev/null and b/src/static/images/2024/cms/lighthouse-best-practices-score.png differ diff --git a/src/static/images/2024/cms/lighthouse-mobile-a11y-yoy.png b/src/static/images/2024/cms/lighthouse-mobile-a11y-yoy.png new file mode 100644 index 00000000000..8f64aed1815 Binary files /dev/null and b/src/static/images/2024/cms/lighthouse-mobile-a11y-yoy.png differ diff --git a/src/static/images/2024/cms/lighthouse-mobile-best-practices-yoy.png b/src/static/images/2024/cms/lighthouse-mobile-best-practices-yoy.png new file mode 100644 index 00000000000..dd6455941e6 Binary files /dev/null and b/src/static/images/2024/cms/lighthouse-mobile-best-practices-yoy.png differ diff --git a/src/static/images/2024/cms/lighthouse-mobile-perf-yoy.png b/src/static/images/2024/cms/lighthouse-mobile-perf-yoy.png new file mode 100644 index 00000000000..b59e9ac07b6 Binary files /dev/null and b/src/static/images/2024/cms/lighthouse-mobile-perf-yoy.png differ diff --git a/src/static/images/2024/cms/lighthouse-mobile-seo-yoy.png b/src/static/images/2024/cms/lighthouse-mobile-seo-yoy.png new file mode 100644 index 00000000000..b5b21420e32 Binary files /dev/null and b/src/static/images/2024/cms/lighthouse-mobile-seo-yoy.png differ diff --git a/src/static/images/2024/cms/lighthouse-performance-score.png b/src/static/images/2024/cms/lighthouse-performance-score.png new file mode 100644 index 00000000000..c13a8f960c9 Binary files /dev/null and b/src/static/images/2024/cms/lighthouse-performance-score.png differ diff --git a/src/static/images/2024/cms/lighthouse-seo-score.png b/src/static/images/2024/cms/lighthouse-seo-score.png new file mode 100644 index 00000000000..a2657ad2721 Binary files /dev/null and b/src/static/images/2024/cms/lighthouse-seo-score.png differ diff --git a/src/static/images/2024/cms/median-cms-page-weight.png b/src/static/images/2024/cms/median-cms-page-weight.png new file mode 100644 index 00000000000..8b079d258d6 Binary files /dev/null and b/src/static/images/2024/cms/median-cms-page-weight.png differ diff --git a/src/static/images/2024/cms/top-5-page-builders.png b/src/static/images/2024/cms/top-5-page-builders.png new file mode 100644 index 00000000000..0a78f4e7649 Binary files /dev/null and b/src/static/images/2024/cms/top-5-page-builders.png differ diff --git a/src/static/images/2024/cms/top-cms-by-rank.png b/src/static/images/2024/cms/top-cms-by-rank.png new file mode 100644 index 00000000000..13041856034 Binary files /dev/null and b/src/static/images/2024/cms/top-cms-by-rank.png differ diff --git a/src/static/images/2024/cms/top-cms-yoy.png b/src/static/images/2024/cms/top-cms-yoy.png new file mode 100644 index 00000000000..1187f920a7d Binary files /dev/null and b/src/static/images/2024/cms/top-cms-yoy.png differ diff --git a/src/static/images/2024/cms/wordpress-cwv-pass-trend.png b/src/static/images/2024/cms/wordpress-cwv-pass-trend.png new file mode 100644 index 00000000000..9b00ed1e2f2 Binary files /dev/null and b/src/static/images/2024/cms/wordpress-cwv-pass-trend.png differ diff --git a/src/templates/base/base_chapter.html b/src/templates/base/base_chapter.html index 8fe567d6abf..d6f1a22bff3 100644 --- a/src/templates/base/base_chapter.html +++ b/src/templates/base/base_chapter.html @@ -336,6 +336,37 @@

{% endmacro %} +{% macro render_bibtex() %} +

+ {{ self.citation() }} +

+
+ BibTeX + 
+@inbook{WebAlmanac.{{ year }}.{{ metadata.get('title').replace(' ', '') }},
+author = "{% for author in metadata.get('authors') -%}
+  {%- set authordata = config.contributors.get(author, None) -%}
+  {%- if authordata %}
+    {%- set full_name = authordata.name.split(' ') -%}
+    {{ full_name[-1] }}{{ self.comma() }}{{ full_name[0] }}{% if full_name|length > 2 %} {{ full_name[1:-1]|join(' ') }}{% endif %}{% if not loop.last %}{{ self.and() }}{% endif %}
+  {%- else %}
+    {%- set full_name = author.split(' ') -%}
+    {{ full_name[-1] }}{{ self.comma() }}{{ full_name[0] }}{% if full_name|length > 2 %} {{ full_name[1:-1]|join(' ') }}{% endif %}{% if not loop.last %}{{ self.and() }}{% endif %}
+  {%- endif %}
+{%- endfor %}",
+title = "{{ metadata.get('title') }}",
+booktitle = "{{ self.citation_journal_title() }}",
+chapter = {{ chapter_config.chapter_number }},
+publisher = "HTTP Archive",
+year = "{{ year }}",
+language = "{{ language }}",
+{%- if metadata.get('doi') %}
+doi = "{{ metadata.get('doi')}}",{%- endif %}
+url = "https://almanac.httparchive.org/en/{{ year }}/{{ metadata.get('chapter') }}"
+}
+
+{% endmacro %} + {% macro render_prevnext() %} {% if prev_chapter %} {% if chapter_lang_exists(lang, year, prev_chapter['slug']) %} @@ -442,6 +473,9 @@

{{ render_authors() }}
+
+ {{ render_bibtex() }} +