|Resolved||kzimmerman||T234695 Measure % of edits and pvs coming from users without JS|
|Resolved||MNeisler||T253033 Measure % of pageviews coming from users without JS|
As described in T234865#5628008, I used the compatibility table to compare pageviews from browsers we actively test and support JS (Grade A Browsers) vs. ones we do not (all below Grade A browsers). Pageview data came from the pageview_hourly table.
Results were split by desktop vs mobile web and views from all spider or automated traffic were removed. For this analysis, I reviewed data from the last week in May.
Based on this approach, here is an estimate of the percent of pageviews from browsers that are JS-supported and tested and browsers without JS support. Further details available in the report and repo.
|access_method||category||pageviews||percent of pageviews|
|desktop||no JS support||204958640||13.84%|
|desktop||JS-tested and supported||1275500218||86.16%|
|mobile web||no JS support||872734397||36.48%|
|mobile web||JS-tested and supported||1519426793||63.52%|
- This does not include information for modern (grade A) browsers where users have turned off JS.
- Pageviews and pageview percentages are different from devices, which is the most similar measure we have to users.
- Data reflects traffic from browsers where we actively test and surface JS features. Based on the information described on the Compatability page, some below Grade A browsers may have JS functionality but we do not actively test and support these.
- Data assumes that the information in the Compatability Table is currently up to date.
These percentages are higher than anticipated and may not reflect the actual percentage of pageviews from users without JS support due to the caveats listed above. Similar to the recommendation proposed in the non-js edit analysis done in T240697, we may want to look at adding instrumentation or using a different approach if a more accurate estimate of the % pageviews coming from users without JS is needed.