N+1 queries are OK in SQLite
SQLite’s own documentation says so: 200 SQL statements per web page is excessive for MySQL, PostgreSQL or SQL Server, but not a problem with SQLite. (N+1 is the pattern of one query for a list, then one more query per item in it.)
It comes down to where the database runs. With a client/server database every statement is a message round-trip from the application to the server and back, and 200 of those in sequence add up. SQLite runs in the same process as the application, so a query is just a function call (no round-trip at all).
The figures on that page come from sqlite.org itself. Its dynamic pages are generated by Fossil (the version control system SQLite is developed in) and typically run about 200 statements each: one query for the timeline, then more queries per entry. A 50-entry timeline usually renders in under 25 milliseconds (few of those milliseconds are spent inside the database engine). So with SQLite, a handful of large queries and many small ones are both fine.