The project goal is to help identify and improve the web over time, one improvment at a time. It tries to do this by giving you a weighted list of improvment you can (and probably should do) to your website.
- Run same test(s) used by WebPerf.se without WebPerf Premium
- Verify that you have done the basics for your website in:
- Security
- User Integrity
- Performance
- Accessibility
- Accessibility statement
- SEO
- Code Quality
- Networking
- World Wide Web Standards
- Email Standards
- Software being used
- Validate new release before going into production
- Test other/more pages then WebPerf.se do
Easiest setup for testing public websites are by using GitHub Actions but you can run this project in many ways and what you choose depends on your needs.
Read more about how to get started
Webperf Core consists of many different tests. Read general information about our tests or go directly to a specific test below.
- Accessibility (Pa11y)
- Website performance (SiteSpeed)
- Validate 404 page (by default checks for Swedish text, though)
- Security, data-protecting & Integrity (Webbkoll)
- Energy Efficiency
- Standard files
- HTTP and Network
- Tracking & Integrity
- Email (Beta)
- Software
- Accessibility Statement (Alpha)
- CSS (StyleLint)
- HTML (html-validate)
- Javascript (ESlint)
- Accessibility, Best practice, Performance, SEO (Google Lighthouse)
Do you want to contribute?
Read more about how to contribute
It is often worthwhile to google/dockduckgo the error messages you get. If you give up the search then you can always check if someone on our Slack channel have time to help you, but don’t forget to paste your error message directly in the first post. Or, if you think your error are common for more people than yourself, post an issue here at Github.
Think this is cool and want to see more? Why not look at third parties.
We could not do this without all help from contributors and other projects we use.