Talk:Omnibus List

From GodWiki
Jump to navigation Jump to search

This is the talk page for discussing improvements to the Omnibus List article.
This is not a forum for general discussion about the article's subject.

Article policies
  • Opinionated research if possible
  • Neutral point of view when appropriate
  • Humour
  • Verifiability
  • Be polite
  • Assume good faith
  • No personal attacks
  • Do not bite the newcomers
  • Respond in a mature manner
  • Be welcoming
  • Maintain civility at all times

This page has an archive

Old and/or inactive discussions have been moved to the /Archive subpage.

New, flexible Omnibus List with responsive formatting (large- and small-screen friendly!)

A little surprise I wasn't expecting to get around to this weekend, but it all just fell into place. After applying a little bit of code cleanup and reworking of the Omnibus List, I decided to just roll up my sleeves, dive in, and modernize the code.

(Note that I didn't change anything about the data, or the way it's formatted β€” the article is just as easy to view, to find information in, and to edit as it's always been. The only changes are to the structure around the lists, which isn't anything list editors really need to concern themselves with too much.)

Thanks to those preliminary structural changes, I was able to make a more sweeping update (again, still not changing anything about the information contained in the article), and produce a version of the Omnibus List with a completely flexible, adaptive layout. It'll reformat itself to fit your screen even on a mobile device (rearranging the list columns so they're all stacked vertically, single-file), and it'll also adapt to larger screens than before β€” now, if your browser is wide enough, you can see all five columns side-by-side, with no stacking at all. And all possibilities in between, which it should automatically adjust for pretty smoothly. (Fingers crossed, anyway.)

A testing/demo version of the new Omnibus List can be found at: User:FeRDNYC/Sandbox

Please test it out and let me know of any issues, concerns, suggestions, or thoughts you may have. Even if you hate it and think it's a stupid idea, please tell me that! (In fact, please especially tell me, if that's your reaction. I'd like to make this the new structure for the real Omnibus List, going forward, but certainly not if it's going to cause problems for anyone or make their life more difficult.)

Any any all feedback welcomed and encouraged. Thanks! -- FeRDNYC (talk) 00:56, 22 October 2018 (UTC)

Tick.png Done The new version is now live. Happy listing! (Happy omni bussing?) -- FeRDNYC (talk) 13:40, 29 October 2018 (UTC)

Omnibus List is now linkified

I've made every item in the Omnibus List a link now. The rationale is this: it may encourage exploration of the wiki by folks who just use it for reference purposes; it may encourage expansion of the wiki by highlighting pages that are missing; and it will provide an easier way (via "What links here" to rapidly check if an existing page is included in the Omnibus.

However, there's a bit of a downside: the HTML source before the change was 183.54K. After the change it is a whopping 932.76K. I expected it to perhaps double or triple, but quintupling is a bit much. I'm pretty worried about the impact this will have on mobile users, particularly as I know that Godville is valued by many players for being such a data-lightweight game.

I will leave as an almost-1MB page for now, with a finger hovering over the undo button. --Djonni (talk) 10:18, 3 November 2018 (UTC)

Whelp, I was right to be worried. The fully linkified Omnibus crashed the Android Godville app's in-app browser, and the browser on my upper-mid-range Android device. So, reverted. Without some clever trickery that's well beyond me (and probably requires a Hypothetical Future Admin's intervention), the Omnibus List must remain unlinked. -- Djonni (talk) 11:51, 3 November 2018 (UTC)

Adjective %monsters%

There are 41 examples in the omnibus monsters list of "Adjective %monster%. E.g., Bricked %monster%, Brutal %monster%, Enlightened %monster%, etc. Most of these are historical and no longer in the game (see paragraph below the table at Monsters#Special monster prefixes).

My understanding of the Omnibus List's raison d'Γͺtre is mostly for crossword solutions, with a sideline in ideabox dupe discovery. I don't think having all the %monster% varieties in the Omnibus list really helps anyone, does it? I'd like to remove them from the list, but I just want to be sure nobody objects, and that I haven't missed some obvious reason why they should stay. At the very least, I'd like to remove all the obsolete ones.

Objections or comments? -- Djonni (talk) 07:13, 3 August 2020 (UTC)

No objections -- WardPhoenix (talk) 09:12, 3 August 2020 (UTC)
Late to the party on this, but rip 'em out. -- S624 (talk) 14:35, 8 October 2020 (UTC)
Done, along with removing Mini-%Boss% while I was there. -- Djonni (talk) 09:34, 10 October 2020 (UTC)

Experiment with fixed-floating mini-index

Following up on WardPhoenix's wildly successful introduction of the {{floatable index}}, I have an experimental fixed-floating version of the omnibus section index ready to try at {{omnibus-index}} (example currently live on the template page). Implementing this on the Omnibus would simply require adding {{omnibus-index|float}} to the page header and probably removing the {{omnibus-index|mini}}s from each section, though that's a matter for testing.

The Omnibus page is an absolute beast to render, especially on low-memory mobile devices, and I'm hoping that moving to a fixed-floating index will alleviate that at least a little bit, as well as help with navigation. I suggest that we should all try this by opening the Omnibus for editing on every device we can (different screen sizes and rendering engines etc), insert {{omnibus-index|float}}, and preview the results. Bear in mind that editing the page is much harder on your device than just viewing it, so some especially low-powered devines may simply crash when we try this, but nonetheless it's worth a try, and reporting results/suggestions/criticism here before we go ahead with the change to this major page. -- Djonni (talk) 08:08, 30 October 2020 (UTC)

Hey, {{floatable index}} was more your work than mine but let's say it was a collaborative work.
Anyway the floating version of the index works properly on my mobile phone (mobile phone being probably the most used device).
Another solution to help rendering the omnibus list would be to not have a omnibus list at all because all other lists exist! (How so I am being extremist?πŸ˜‚) -- WardPhoenix (talk) 09:45, 30 October 2020 (UTC)
Ooh, I like {{omnibus-index|float}}! It took me a minute to put the code in the right place πŸ™„ , but it worked well on my iPhone XS (what I’ve been using).
I had to remove the {{omnibus-index|mini}} from the sections for the UI to β€œlook” right since the floating index overlaps, but floating is much more useful (on mobile at least) than scrolling to find each section. -- Bibliophile (talk) 14:59, 31 October 2020 (UTC)
Okay, responses seem to be positive so I'm going to make this change today. PLEASE HELP by keeping an eye on Special: RecentChanges and the forums (especially Crossword Hints) for signs that people are having issues with it. I'll make the edit as easy as possible to reverse; instead of deleting the {{omnibus-index|mini}}s I'll comment them out and they can be fully removed at a later date. -- Djonni (talk) 08:01, 1 November 2020 (UTC)
Sounds good. Will do πŸ‘πŸΌ -- Bibliophile (talk) 21:10, 1 November 2020 (UTC)

Omnibus is becoming (or has become) unusable on mobile

Okay, it's time. 😊

Unless you happen to have a higher-end mobile device with lots and lots of memory (and your operating system actually allows your applications to use enough of that memory, but I digress), the Omnibus list has grown to a point where, on most mobile devices, in most browsers (including the Godville in-app browser), it simply freezes and/or crashes. This is a pretty challenging problem to solve, as the page is already quite simple in terms of the code and rendering, but I'd like to try to tackle it nonetheless.

I've just done two edits culling bad entries out of skills and equipment lists (please feel free to check my working and replace entries I've removed in error, it took a really long time and I tried my best to be as accurate as possible with all available information, but it's possible I made changes that weren't correct). The raison d'Γͺtre of the Omnibus has always been for crossword solvers. They want a single, searchable page where they can quickly find solutions. So, I want make a few choices oriented towards that very specific use case, as any other user is really best off using the appropriate "List of" page.

  • Since they don't change, I think we should remove the towns from the page. Even the most beginner of players can find those with trivial ease, I would have thought, no?
  • I've done some analysis of a fairly large chunk of crosswords going back a while, and I've concluded that they only use a fairly limited subset of the game's content.. Specifically, crossword solutions consist of items which:
    • Only include unaccented English letters A-Z, spaces, and hyphens. So this means we can cut out a pretty big chunk of the Omnibus list in one slice, by removing all entries with:
      • Any punctuation, quotation or apostrophe marks, in angled or unangled forms
      • Any numerical digit in the name (e.g., 128-bit encryption, etc)
      • Any emoji or other special characters
    • None of the crossword patterns allow for items longer than 25 characters in length. So all items longer than that can be safely removed.

While it's certainly possible that these conditions may change in future, especially the condition of length if new crossword patterns are ever introduced, I believe that's something we should only worry about if it happens. Because, in the meantime, this page is becoming very close to unusable.

My suggestion is that I can make this change quite easily (I'll use a proper offline editor and simply strip out the lines that don't match a very simple pattern, ^\* ([A-Z,a-z,- ]{1-25})$ depending on your regex implementation), and replace the redundant navigation bar across the top of the page with a brief note about the page's contents and intention. I'll also post a notice to the crossword hints forum, as well as probably the ideaboxers union; since the other major users of this page are those who want a quick check for dupes in the included categories, and they will be adversely affected (though I imagine most of them will agree the page was becoming unusable for that purpose as well).

This is a pretty huge change to a pretty major page, though, so I'd like to be sure others think this is wise before going ahead. 😊 -- Djonni (talk) 11:24, 29 November 2020 (UTC)

Honestly, I'd vote once more for the removing of the omnibus list entirely. All it's content is supposed to be on the other lists and it's a mess to have to edit both lists everytime. Plus those complaining about how things are missing on the lists are those who never contribute, so... -- WardPhoenix (talk) 12:01, 29 November 2020 (UTC)
Yeah, a part of me would love to agree with you, but the main problem I see with this is that if we remove it, I guarantee you that sooner or later someone will just create a new one with a huge, messy, ugly dump of all the other lists, and we'll be back to square one again. What we have here in the Omnibus list is a quintessential desire path; we, the "architects" and "landscapers" of the wiki, might think it should work a certain way... but the footfalls of hundreds or thousands of users simply disagree. 😊
The Omnibus is. I think it's best to manage it in such a way that it isn't broken, than throw it out entirely. -- Djonni (talk) 12:20, 29 November 2020 (UTC)
As someone who regularly contributes to the Omnibus list, I totally agree with the idea to streamline it. Its main use really is for the crosswords.
So when I have a list of new things to add, do I use the criterias listed here on what to add, or do I just add it all in?
When will you be starting the overhaul? -- Lakefire Arrow (talk) 15:11, 30 November 2020 (UTC)
So when I have a list of new things to add, do I use the criterias listed here on what to add, or do I just add it all in? This is an excellent question, especially as most future contributors to the list won't pay any attention to this. Hmm.
Perhaps this is the solution: I'll make it as easy as I possibly can for (almost) anyone in future to strip invalid entries from the list. I'll have to think about the best way to actually do that; perhaps I put a PowerShell script somewhere that's easy to find which can be run on any windows computer...? πŸ€” Or... Hmm. A greasemonkey script that runs in a browser...? I really don't know the best approach for that right now, I'll have to give it some serious thought. None of the options that come to mind immediately are really that easy, they all require some specific platform or technical skills that many or most editors won't have. Thinking cap time.
And as for when; when I've got a round to-it spare, maybe the weekend coming, maybe sooner. I'd like a chance for any significant objections, or corrections to my assumptions above, to come up first. -- Djonni (talk) 15:27, 30 November 2020 (UTC)
So should I hold off adding to the list until after you've done the changes? -- Lakefire Arrow (talk) 05:16, 1 December 2020 (UTC)

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ Oh, no no, go ahead and add everything right away. A handful more entries won't make a difference either way, and we may as well have as accurate a list as possible! 😊 -- Djonni (talk) 06:21, 1 December 2020 (UTC)

Oh that's a shame. I honestly never thought it requires a "high-end" device to browse through words on a page. But if many users(?) having this issue then I also support all the above mentioned ideas. I do the crosswords every day for over a year and the omnibus is a great help indeed, but I must add that I mostly use that page for ideaboxing, even just to help with voting for other ideas. X Emantribble
Mmm, I'll take that as a vote against the change, Emantribble, and it's noted. I share your concerns about using it for ideabox dupes.
I personally have an upper-midrange mobile device (Pixel 3a), and I'm not able to load the page at all, in the Godville app nor in a separate browser (admittedly I've only tried Chrome, which is not famous for memory optimisation). At least two other regular Wiki users/editors have raised the issue privately with me. That, for me, usually signals the tip of an iceberg when it comes to Godwiki usability issues: I've learnt that most people who have problems with some aspect of the wiki don't bring it up until someone else does. Even regular, active, communicative users and editors.
As we all know, Godville is a game that runs brilliantly on cheap, low-end, crappy phones with cheap, slow, crappy internet. It's those users that I try hardest to keep in mind when thinking through anything to do with Godwiki usability. (Those, and players with accessibility needs, which is another topic entirely. If anyone with accessibility concerns about the Omnibus or anything to do with the Godwiki has something to share, we are very interested to hear your input.) Now, I could actually be quite wrong in my feeling that a large proportion of players are having trouble with the Omnibus list — perhaps I'm overestimating where my device and the devices of my friends fall in the user device spectrum — but I feel that it's a bit of an access justice issue, even if a fairly small one. I'd much rather make sure that the maximum possible number of users can use the Omnibus, even if it's for a smaller set of uses. As already mentioned elsewhere, the "List of" articles are still there, and have always been more accurate than the Omnibus anyway. Searching the Godwiki for a word is going to give close to the same results as searching the text in this list, if somewhat less convenient.
If anyone has a suggestion of how to optimise this page without losing content, we're happy to hear it. In technical terms, I'm aware that having every section rendered as a bullet list places a bit of a burden on the rendering engine, but if you're familiar with Mediawiki behaviour you'll probably agree that it's the most reasonable approach to these lists (especially as the Omnibus list really must be easily editable by folks with zero knowledge of web, wiki, or code).
Some quick stats, for current and future readers of this thread:
  • Right now, the Omnibus list holds exactly 6,900 items (6,940 lines, including the formatting and technical code, of which there's not much), and weighs in at over 140,000 characters.
  • Removing Towns would remove 33 items (about 620 characters), with the benefit of removing a section of rendering
  • Removing items of length > 25 characters would remove 373 items (over 9,300 characters)
  • Removing items with punctuation not used in crosswords (e.g., β€œβ€"β€˜β€™'()%, all emoji) would remove 555 items
  • Removing items with numerical digits [0-9] would remove 93 items
Some of those are overlapping, of course. (The very first Omnibus item, 0% discount coupon, falls into two of these.) Altogether, removing all the items I propose will reduce the list by 884 items, or around 13% of its current size. So, what I suggest is neither a panacea that will solve the issue for everyone, nor an indiscriminate slash-and-burn that will make the list completely useless for Ideaboxers. Hopefully, it's a reasonable compromise that will extend the usable lifespan of the Omnibus for a while, before we really do have to burn it all down and try something else. 😊 -- Djonni (talk) 08:57, 1 December 2020 (UTC)
I've never thought of my phone as high-end, I use a 4G Samsung Galaxy A10, but I've never had issues accessing the Omnibus page. But, if even one person is experiencing problems accessing the page, it's probably a safe bet that there are others having the same problem too.
And whatever that can be done to help those people out, we should at least try, like what Djonni is trying to do.😊 I know if I was experiencing problems with it, I would hope that the people running Wikigod would at least try something to correct the problem, even if it wasn't successful. -- Lakefire Arrow (talk) 10:05, 1 December 2020 (UTC)

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ Agreed with Lakefire Arrow. I'm so glad you posted about this in the crossword forum, Djonni, since I apparently wasn't watching this Talk page. Plus, I didn't realize from the discussion on the List of Equipment that a such a big Omnibus overhaul was planned. I have no major objections, though. Loading pages isn't a problem for me, but I'm always a big advocate for broader mobile accessibility πŸ‘πŸΌ I honestly don't have a good frame of reference of what are considered "low-end" mobile devices nowadays. There are so many different devices and versions. Learning about your problems on an upper-midrange mobile device (Pixel 3a) where you aren't able to load the page at all, in the Godville app nor in a separate browser helped put it in perspective more.

Frankly, as far as editing the wiki goes, it would be easier to focus on adding/updating equipment, artifacts, and monsters (and related values) to their respective "List of..." pages. I'll get into an editing groove, then think, "Oh, yeah, better check the Omnibus, too."

A potential Omnibus List problem might occur when both an artifact and equipment exist with the same name. I don't know if the crossword always uses one type as the clue for the word. Then again, there likely aren't many crossword-only words that fit that criteria.

If the "List of..." pages are kept reasonably up-to-date, I don't think it's a big deal to click on each separate category to check for Ideabox idea dupes.

Finally, I leave the ultimate technical WikiMedia decisions to those of you who understand how it affects device resources, browsers, etc. That's way beyond my skills or knowledge. Will happily will offer more general opinions 😊 --Bibliophile (talk) 00:25, 2 December 2020 (UTC)

It's really interesting to me how many people are consistently saying "Nah, I'm not having this issue at all." Interesting and genuinely surprising. I just tried the Omnibus again on my phone, in-app, and couldn't scroll or search in page without significant pauses and "Godville isn't responding" popups.
So. Perhaps it's an issue that doesn't affect so many people as I imagined after all. Perhaps it's more about my usage patterns, and the usage patterns of the others who brought this up with me — I do switch between quite a few apps quite often, and keep tabs open in browsers, and so my OS may simply not be giving my Godville app as much memory to use as most people.
I don't think that anybody objects to the removal of the towns from the Omnibus though, they really aren't useful for any of the use cases discussed (crosswords and ideaboxing). So, my current plan is to go ahead with snipping those off (and the corresponding adjustment to the {{omnibus-index}} template). I'll leave the scrubbing of non-crossword entries aside for now... with a little hesitation.
I think I've said it before, above, but my fear is that those who are impacted by issues like this simply don't bring them up. So, I'm going to keep my eyes and ears peeled for people expressing issues with the page's usability or accessibility, and I'd appreciate if others did the same.
Here on the Godwiki we have a very strong preference for public discourse; having all our Godwiki discussions on talk pages pushes us towards consensus and compromise, keeps us cooperating and collaborating towards shared goals, and (usually) helps prevents misunderstandings and working at cross-purposes. However, in the rest of Godville, the fraction of the player base that interact in public ways (forums, and even guild councils) is actually pretty small. It happens a lot that I get private messages about forum posts or talk page topics, because people just don't want to speak "publicly".
So: if you are struggling with the Omnibus List, or any other aspect of the Godwiki, we really need to hear about it. Of course I'd love it if you said so out loud so that I'm not the only person who knows, but if you simply don't want to do that, then that's fine. You can PM me or, if you don't like me, pick someone else who's actively participating in this conversation and share your experience with us. Alright? 😊 Good.
In summary: shortly I'll remove Towns from the Omnibus list, but the rest of the changes are paused until someone other than me raises the issue. πŸ‘ -- Djonni (talk) 06:04, 2 December 2020 (UTC)
I do switch between quite a few apps quite often, and keep tabs open in browsers, and so my OS may simply not be giving my Godville app as much memory to use as most people. This might be one of the reasons why you're having trouble. The game of Godville may be able to run on a crappy phone with crappy internet, but Wikigod is a whole other matter. I only recently realized just how much memory Wikigod takes up when it's opened in-app or in a browser.
When I want to use Wikigod, I usually only have about 3 apps open including Godville or a browser (whichever one I opened Wikigod in), just to be on the safe side because my phone only has 1GB of memory. But I've opened Wikigod in Chrome, Firefox as well as Samsung's Browser without any issues.
Maybe a bit of friendly advice could be put at the top of the Omnibus page asking users to close unneccessary apps if they want to view that page. I don't know if that would actually help anyone, but it's worth a try. -- Lakefire Arrow (talk) 10:41, 2 December 2020 (UTC)
πŸ€” That is really not such a bad idea, Lakefire Arrow. Gonna do that. -- Djonni (talk) 11:42, 2 December 2020 (UTC)
Tick.png Done Note added, though if the wording can be improved please go ahead and do so. -- Djonni (talk) 11:47, 2 December 2020 (UTC)

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ I usually only use the Godwiki on desktop, but having just checked it on the mobile app, it turns out I'm one of the people for whom the Omnibus works poorly. I notice three problems. For reference, I'm using a Redmi Note 7 Pro.

  • 1. Scrolling. If I scroll too fast (in either direction), the page turns blank and I have to wait (at most) a few seconds for it to 'catch up' to my current position and load that section of the page. Overall, not a big issue, just need to wait a bit; the app doesn't freeze or crash.
  • 2. Navigating. On mobile, there's two sets of buttons that can be used to navigate to different sections of the Omnibus: those at the top and those on the side. The ones at the top work fine, but the ones on the side will often freeze the app. Navigating to the 'Skills' section rarely, if ever, freezes the app, while going to the other sections is pretty much guaranteed to freeze the app. Sometimes it unfreezes after a while, sometimes not. So I guess that means the problem is related to the length of the lists, since the Skills list is shortest and at the bottom of the page? I don't know.
  • 3. Searching. If I try to use the search function on the Omnibus, the app freezes. If I'm patient enough (like, really patient), the app might unfreeze after a while. Until the next search, that is. Moving between search results is a bit sluggish too.

This all happens even if I don't have any other apps open. Scrolling and navigating the Omnibus list using DuckDuckGo works perfectly fine; but I get the same navigating issues in Chrome. (Neither browser has a search function that I'm aware of, unfortunately.)

Having said all that, even if I had no issues accessing the Omnibus list, I would still vastly prefer accessing the Omnibus list on desktop when solving crosswords, just for the simple reason that it is (for me, at least) a lot easier to switch back and forth between tabs on desktop. In the app, every time I want to switch from the newspaper to the Omnibus list, I have to reaccess it through the main page, which is a bit tedious. (The 'Last Web Page' button just sends me back to the newspaper, so it's not very useful in this case.) And if I have to visit the main page anyway, I might as well access the specific list I need directly, instead of the Omnibus list, right? I know I can also access the Omnibus list on an external browser, but without the search function, this option feels a bit impractical to me. I know this is not something that can be solved by restructuring the Omnibus list, but I thought I'd mention it anyway.

Lastly, since the towns have been removed from the Omnibus list, might it be a good idea to add a link to the Towns article at the top of the main page? Maybe instead of the Geography page, if one doesn't want to change the total number of links at the top. --Dream Summoner (talk) 12:23, 2 December 2020 (UTC)

I'm not voting against it, I was just surprised that this could be an issue. Previously I used a Pixel 1, opened omnibus in Chrome, run Spotify, WhatsApp and Godville without an issue even when the phone was nearing its end for other reasons. Recently I swapped to a Redmi with half the memory of the pixel, but still no issue. Now, I'm not good at computer sciences, I don't know how exactly these things work, I just assumed that browsing through a page with nothing but words on it isn't a hard task. Also, how comes a Pixel 3 has troubles with it, maybe you have more apps running in the background than you think?
Anyways, the reason I joined the talk is because I prefer to get to the end of things, rather than brainlessly jump to conclusions. Herd mentality isn't my vibe.
Few thoughts: I don't know how many people are reading this, maybe not enough, but I think it would be great to know if many users experiencing this problem, or only a fraction. I'll ask around friends who regularly do the crossword, maybe ask them to ask around too. I have a suspicion that this is more about how you use your phone rather than having a cheap one. If it's only a few people, then it would be a shame to rip apart a page that is used by hundreds. As it was mentioned before, there are the "list of..." pages with even more content.
However, if this is really happening to a number of players, I'm totally supporting the stripping! Getting rid of towns was a great move, and the other ideas are also very clever, if they need to be done! I wonder how long it would be a help though, to remove a small percentage, after all, the list is always growing.

Some data on page loading time

I don't know exactly to whom this data will be beneficial and how exactly this will be beneficial but here's some rough estimates on loading time via Chrome Dev Tools. Note: these are really really rough estimates and some elements may be cached when I tested so real speed is likely a bit slower.

  • At Fast 3G setting it looks like this: The whole page finished loading in 2.66s. If my understanding of this is correct, the green bars indicate the time it takes for the server to prepare the thing the browser is requesting and the blue bar is the time it takes for the browser to download it. The first item is the loading of the omnibus itself which looks like this: So it looks like it took 0.57 seconds for the server to prepare the omnibus and 0.37 seconds for the browser to download it, bringing the total to around 0.98 seconds. The second and third items are the skin styles and JavaScript respectively. There's also the DOMContentLoad at the bottom right which is the HTML elements loaded without the styles, images, etc. (More info here about DOMContentLoad.) Here it's at 1.86s.
  • At Slow 3G setting it looks like this: The whole page now took 7.77s to load. Again, if my understanding is correct, the yellow and purple bar is for the time the browser is trying to establish connection with the server. The connection is slow so they're showing up here. Now, the green bar is at 2.02s and the blue bar is at 1.32s, bringing the total loading time of the omnibus list itself at 4.04s. The DOMContentLoad is also slower here at 5.60s.
  • Here's the Google PageSpeed Insights report: -- Zoombie (talk) 10:18, 6 March 2021 (UTC)