How we check a website
The score from 0 to 100 shows what share of the weight of the checked items the website achieved. Items that could not be determined are not included in the score. If less than half of the total item weight could be checked, we do not show a score.
Resolution No. 480
Applies to state and municipal bodies.
| Item | Weight | Basis |
|---|---|---|
| Easy-to-read language | 15 | Resolution No. 480, Description para. 9 |
| Lithuanian Sign Language | 15 | Resolution No. 480, Description para. 9 |
| Content updates | 10 | Resolution No. 480 requires updates at least every 3 months |
| Site search | 10 | Resolution No. 480, Description para. 30 |
| Organisation details | 10 | Resolution No. 480, Description para. 9 |
| Information in English | 10 | Resolution No. 480, Description para. 12 |
Basics
| Item | Weight | Basis |
|---|---|---|
| Secure connection (HTTPS) | 10 | Good practice |
| Mobile-friendly | 5 | Good practice |
Security
| Item | Weight | Basis |
|---|---|---|
| Browser security headers | 5 | Good practice |
| E-mail protection: SPF | 5 | Good practice |
| E-mail protection: DMARC | 5 | Good practice |
What we check and what we don’t
The quick check reads only the public home page, the sitemap and the domain’s DNS records. In total we make no more than 6 requests to the website. This has no effect on the website: we change nothing on it and do not attempt to break in.
Once you order the report, we also check the home page with Google PageSpeed Insights: we measure accessibility and mobile speed. We also check how long the SSL certificate remains valid.
We write “not found” because an automated check can miss things that are on the website, for example content shown only by a script running in the browser. The check does not assess design or content quality and does not confirm full compliance with the law or WCAG.