# lighthouse ## scores the lighthouse scores as of now: | performance | 100 | |---------------- |----- | | accessibility | 92 | | best practices | 95 | | SEO | 95 | ## lighthouse recommendations ### performance - [ ] ['Save 43 KiB by minifying the JavaScript'](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript) - [ ] ['Serve static assets with an efficient cache policy'](https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl) > thats `main.js` and both 'no chromium' and 'null cookies' badge images, currently they have no set cache at all(?) - [ ] Images do not have explicit `width` and `height` > thats both badge images ### accessibility - [ ] Background and foreground colors do not have a sufficient contrast ratio. > Lighthouse doesnt like the [`#865DD3` and `#1E2021` color combo](https://webaim.org/resources/contrastchecker/?fcolor=865DD3&bcolor=1E2021), which are the background and accent color. ### best practices - [ ] Serve images with low resolution - [ ] should be fixed by setting a explicit `width` and `height` from the [performance optimalization](#performance) > | url | displayed size | actual size | expected size | > |--------------------------------------- |---------------- |------------- |--------------- | > | /img/nochromium-badge.png(squel.xyz) | 80 x 15 | 80 x 15 | 120 x 23 | > | /img/nullcookies-badge.png(squel.xyz) | 80 x 15 | 80 x 15 | 120 x 23 | - [ ] ['Ensure CSP is effective against XSS attacks'](https://developer.chrome.com/docs/lighthouse/best-practices/csp-xss/) > we dont allow for user input at all, but it might be worth looking at it for the future ### SEO - [ ] Tap targets are not sized appropriately > Lighthouse does not like the links of the service list on the homepage. They want an 48x48px size or have 'enough' space around them. The current size of the links in the list are 43x23px each. # [web accessibility evaluation tool](https://wave.webaim.org/report#/https%3A%2F%2Fsquel.xyz) - [ ] `<label id="currentPage" (...)` is an 'orphaned form label, just like `<label id="quote" (...)` - [ ] they [also](#accessibility) dont like the low accent contrast - [x] neither do they like the redundant links to the homepage, and example.com. however since they are placeholders and safe to ignore imo - [ ] iamges have a title, but no alt value for screen readers

Squel commented

(Migrated from codeberg.org)

lighthouse

scores

the lighthouse scores as of now:

performance	100
accessibility	92
best practices	95
SEO	95

lighthouse recommendations

performance

thats main.js and both 'no chromium' and 'null cookies' badge images, currently they have no set cache at all(?)

Images do not have explicit width and height

thats both badge images

accessibility

Background and foreground colors do not have a sufficient contrast ratio.

Lighthouse doesnt like the #865DD3 and #1E2021 color combo, which are the background and accent color.

best practices

Serve images with low resolution
should be fixed by setting a explicit width and height from the performance optimalization

url displayed size actual size expected size

/img/nochromium-badge.png(squel.xyz) 80 x 15 80 x 15 120 x 23

/img/nullcookies-badge.png(squel.xyz) 80 x 15 80 x 15 120 x 23

url	displayed size	actual size	expected size
/img/nochromium-badge.png(squel.xyz)	80 x 15	80 x 15	120 x 23
/img/nullcookies-badge.png(squel.xyz)	80 x 15	80 x 15	120 x 23

'Ensure CSP is effective against XSS attacks'

we dont allow for user input at all, but it might be worth looking at it for the future

SEO

Tap targets are not sized appropriately

Lighthouse does not like the links of the service list on the homepage. They want an 48x48px size or have 'enough' space around them. The current size of the links in the list are 43x23px each.

web accessibility evaluation tool

<label id="currentPage" (...) is an 'orphaned form label, just like <label id="quote" (...)
they also dont like the low accent contrast
neither do they like the redundant links to the homepage, and example.com. however since they are placeholders and safe to ignore imo
iamges have a title, but no alt value for screen readers

Commenting is not possible because the repository is archived.

Rows
Columns

accessibility and other lighthouse improvements #13