Baskollen
Submit your project.
Get the tech reviewed — and a clear path to improve it.
- Free technical review of security, performance, accessibility and discoverability — included when the project is added to the catalog.
- A new measurement whenever you want. Verified owners can run one with the click of a button, and a failed measurement can never erase a successful one.
- One ready-made fix per finding — phrased as a prompt to paste into Claude Code or your AI tool. Apply it, run a new measurement, and see the difference.
Baskollen so far
Latest sweep: 26 August- 201
- measurements made
- 165
- projects measured
- 82 / 100
- catalog average
- +21
- largest improvement so far
Where the catalog stands right now
87 % of projects measured more than once have improved — by +10 points on average. Baskollen doesn't just score projects. It helps improve them.
Four areas, one number
The overall score from 0 to 100 is weighted. No opinions, no jury — the same checks are applied to every project.
Securityaverage 73
Security headers, vulnerable JavaScript libraries, exposed configuration. What makes your project safe to visit.
Speedaverage 85
How fast the page actually becomes usable — measured in a real browser, not estimated.
Accessibilityaverage 88
Contrast, touch targets, structure. What determines whether everyone can use what you've built.
Discoverabilityaverage 84
Titles, descriptions, structured data. What helps people find it.
The report doesn't just tell you what to fix. It shows you how.
Every finding is explained in plain language and comes with a ready-made prompt for your AI tool. Here's what a row looks like for the project's owner:
Set a Content-Security-Policy
Your site is missing the CSP header, which limits what the browser may load and run. Without it, injected code can do more damage.
Ready-made prompt — paste into your AI tool
Add a Content-Security-Policy for my site. Start in report-only mode, list which sources are actually used, and then propose a strict policy.
Apply the fix, request a new measurement, and see how the score changes.
Numbers you can trust
- Only measured projects count. Every average shows its sample size. Never a guess.
- A failed measurement never counts against the project. It reflects the scoring system, not the project — the score and history remain unchanged.
- The details are yours. The score is public — the exact findings are visible only to you as the verified owner. A weakness shouldn't be a map for others.
- The scoring system keeps evolving. New checks are reviewed against the whole catalog before they count — a rule that would unfairly punish good builds is rejected.