Measuring success of the test
Pages
The objectives put in place for the pages.
| Objective | Outcome |
|---|---|
| All pages serve 200-OK status code | Pass |
| Pages can be crawled | Pass |
| Not found page shown | Fail |
| Not found page serves 404-Not Found status code | Fail |
Resources
The objectives put in place for the resources.
| Objective | Outcome |
|---|---|
| Robots.txt returns 200-OK | Pass |
Robots.txt is plain/text; UTF-8 | Pass |
XML sitemap is text/xml; UTF-8 | Pass |
| Service Worker returns 200-OK | Pass |
Service Worker is application/javascript; UTF-8 | Pas |
Functionality
The objectives put in place for the functionality.
| Objective | Outcome |
|---|---|
| Service Worker is installed | Pass |
| App works offline | Pass |
| App is SPA | Pass |
Assessment
Using Lighthouse, we want these pages to score 95+ as overall score for the various categories. The page load speed (performance) will be measured by Page Speed Insights, while the other categories will be measured using Chrome DevTools Lighthouse. The tests are done on all pages
| Category | Score |
|---|---|
| Performance | 99 |
| Progressive Web App (PWA) | 14 / 14 |
| Best practices | 100 |
| Accessibility (a11y) | 100 |
| SEO | 100 |
| W3c Validator: Errors | 0 |
| W3c Validator: Warnings | 0 |