How quickly does the page appear? What do automated accessibility checks find? Here are the measurements from the 2026 website, with the original reports open for inspection.
Choose a page and a device. The four scores and timings below belong to one actual Lighthouse run: the middle performance score of three. The full range and all original reports follow.
A separate axe scan checks the initial page against automated WCAG 2.0, 2.1 and 2.2 A/AA rules. A score of 100 or zero detected failures does not establish full accessibility.
Full axe results (JSON)Actual browser capture from the separate accessibility scan. It is taken after the performance runs.
Screenshot of the original Lighthouse renderer for the displayed run. Open the HTML report to inspect every audit.
A separate axe scan checks the initial page against automated WCAG 2.0, 2.1 and 2.2 A/AA rules. A score of 100 or zero detected failures does not establish full accessibility.
Full axe results (JSON)Actual browser capture from the separate accessibility scan. It is taken after the performance runs.
Screenshot of the original Lighthouse renderer for the displayed run. Open the HTML report to inspect every audit.
A separate axe scan checks the initial page against automated WCAG 2.0, 2.1 and 2.2 A/AA rules. A score of 100 or zero detected failures does not establish full accessibility.
Full axe results (JSON)Actual browser capture from the separate accessibility scan. It is taken after the performance runs.
Screenshot of the original Lighthouse renderer for the displayed run. Open the HTML report to inspect every audit.
A separate axe scan checks the initial page against automated WCAG 2.0, 2.1 and 2.2 A/AA rules. A score of 100 or zero detected failures does not establish full accessibility.
Full axe results (JSON)Actual browser capture from the separate accessibility scan. It is taken after the performance runs.
Screenshot of the original Lighthouse renderer for the displayed run. Open the HTML report to inspect every audit.
A separate axe scan checks the initial page against automated WCAG 2.0, 2.1 and 2.2 A/AA rules. A score of 100 or zero detected failures does not establish full accessibility.
Full axe results (JSON)Actual browser capture from the separate accessibility scan. It is taken after the performance runs.
Screenshot of the original Lighthouse renderer for the displayed run. Open the HTML report to inspect every audit.
A separate axe scan checks the initial page against automated WCAG 2.0, 2.1 and 2.2 A/AA rules. A score of 100 or zero detected failures does not establish full accessibility.
Full axe results (JSON)Actual browser capture from the separate accessibility scan. It is taken after the performance runs.
Screenshot of the original Lighthouse renderer for the displayed run. Open the HTML report to inspect every audit.
Six measured cases. Each score and LCP belongs to the selected actual run. Performance range includes all three runs.
Page
Device
Performance
Performance across three runs
Accessibility
Main content (LCP)
axe failures
Homepage
Mobile
60
60–61
97
9.75 s
1
Education centre
Mobile
54
52–63
77
6.83 s
4
Contact
Mobile
63
63–63
85
5.84 s
3
Homepage
Desktop
66
64–68
97
3.18 s
1
Education centre
Desktop
65
57–73
82
2.45 s
4
Contact
Desktop
74
73–77
88
2.61 s
3
How we measured
The public 2026 website
These results describe the deployed website, including its content, plugins, hosting and external services. They do not isolate the theme’s contribution. The tested pages are in Estonian. The report’s English translation uses the same measurements.
Three fresh runs per case
Lighthouse runs sequentially in fresh Chrome profiles, with browser storage reset and its standard simulated mobile and desktop throttling. It uses the browser’s default colour scheme; the separate axe scans use light mode. Server caches may be warm. No cookie choices or form submissions are made. Results are lab observations, not visitor analytics.
One separate accessibility scan per case
axe scans the default light-mode page after a five-second settling period. Menus are closed. Keyboard flows, screen readers, dark mode, open menus and forms still need manual testing. Incomplete checks are retained in the JSON reports. Counts of affected nodes are rule–element occurrences, not unique elements.
Dates, sources and reproducibility
The manifest records source URLs, exact settings, timestamps, tool versions and SHA-256 checksums. The served 2026 stylesheet was checked before and after collection. The server does not expose a deployment commit; the local source reference is not a verified production revision.
Scores can change as content, networks and external services change. These automated checks are not a WCAG certification or a complete accessibility audit.
