You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the logic of EcoIndex, it should be great to audit more than the home page:
5 most visited pages => Average 5 most visited pages: 72
Home (score: 70)
About (score: 75)
Some landing page 1 (score: 70)
Contact (score: 65)
Some landing page 2 (score: 80)
Most visited courses, for instance:
Home (score: 70) → About (score: 75) → Contact (score: 65) => Course average score: 70
Some landing page (score: 70) → Blog article (score: 80) → Newsletter subscription (score: 66) => Course average score: 72
etc.
=> Site average score: 71,33
Carbon Footprint should have a setting page, where different front pages or courses can be registered. Scores will be individual and averages, and be saved in database, or JSON file (or WP REST API).
The text was updated successfully, but these errors were encountered:
Thanks!
The goal of this plugin is, first and foremost, to raise awareness about digital sustainability and to help to improve ones site in general. Tools like ExoIndex are then great way to get more insight into the details of what could and should be improved, after a first nudge by this plugin.
So, IMHO, it is not an essential part of the plugin to start with, but definitely something to think about. Maybe, indeed by providing a more general score, not only based on the homepage, but some kind of an average, for example for the pages in the main navigation? On the other side, we tend to keep the impact of this plugin itself as low as possible (by not checking too many pages). :-)
Following the logic of EcoIndex, it should be great to audit more than the home page:
=> Site average score: 71,33
Carbon Footprint should have a setting page, where different front pages or courses can be registered. Scores will be individual and averages, and be saved in database, or JSON file (or WP REST API).
The text was updated successfully, but these errors were encountered: