optimise homepage #112

New issue

Closed

opened 2025-12-13 01:29:52 +01:00 by Moiety · 2 comments

Moiety commented

2025-12-13 01:29:52 +01:00

(Migrated from codeberg.org)

have homepage specific CSS?
don’t load the now-playing module?
optimise ~~images~~ icons further?

Findings

splitting out the icons isn’t helpful: aim for having fewer files rather than more smaller ones

Homepage CSS

name	size	time on 3G	note
core.min.css	28.008 bytes	3.66s	-
home.min.css	13.770 bytes	2.85s	this is including all components as they are
home.min.css	11.682 bytes	2.67s	this has a trimmed down typography file

- [ ] have homepage specific CSS? - [x] don’t load the now-playing module? - [x] optimise ~~images~~ icons further? ## Findings - splitting out the icons isn’t helpful: aim for having fewer files rather than more smaller ones ## Homepage CSS | name | size | time on 3G | note | | ------|-----|------------|----- | | core.min.css | 28.008 bytes | 3.66s | - | | home.min.css | 13.770 bytes | 2.85s | this is including all components as they are | | home.min.css | 11.682 bytes | 2.67s | this has a trimmed down typography file |

Moiety commented

2025-12-13 20:18:51 +01:00

(Migrated from codeberg.org)

might go with just importing a custom homepage CSS file, the extra 200ms saving would be nice but might require some further splitting of files. can be done in the future.

Moiety commented

2025-12-14 01:27:56 +01:00

(Migrated from codeberg.org)

decided against separate CSS for now. it might save a second loading the homepage over 3G, but it adds the full 3.66s to the next page load; that’s a net loss.