The slowness getting to Site settings on Android might be related to  Issue 732907 . Hesitant to mark as a duplicate since I'm not familiar with the code on the Android side and can't say for sure, but marking as blocked for visibility.

As for the larger issue here (no easy way to get to all the site settings on Android), I think there is a plan to do some UI changes on Android in Project Jewelbox ( Issue 601177 ), CCing dominickn.

Longer term we're going to be showing all non-default settings in Page Info. What that would mean is that if JavaScript was disabled by default, you would be able to easily enable it but not the other way around. That doesn't exactly satisfy your use case but the challenge is that we don't want to show uncommon settings in Page Info because for most users they will not be used and be confusing.

Re #3: thanks for the linking the related issues.

Re #4: can't we just have a "show all" or "advanced settings" button at the bottom of the page to satisfy all use cases: keeping it short and clean for casual users but allowing direct access for advanced ones?

Oh I forgot to mention the other part of the plan which might be satisfactory for you. When you click the lock icon, even though JavaScript won't appear directly, you will be able to click "Site Settings" and then toggle it on the next screen that appears. So it will require 1 extra tap or so.

Re #7: Yes! That's precisely what I was looking for. From your previous answer it seemed that the current rather empty page would be kept that way (WAI).

To make sure this is clear, I understand that:

* Page Info is the dialog that is presented when the user taps on the security chip (or long presses the Omnibox). It will eventaully present the non-default settings for the current site.

* The Site Settings page -- reachable from tapping on the "site settings" button from the Page Info dialog -- will eventually present all existing site settings (the same list presented on desktop Chrome when clicking on the security chip).

* "Eventually" in these two previous statements means "this is a planned feature and it will be implemented, we're just not there yet".

Are these 3 points all true and correct? :)

Yep, #9 is correct :) We should reach that state on desktop sooner than mobile unfortunately. But that is the end state that we have in mind for both. 

SGTM then. Is there an issue I can CC myself to keep updated on this?

It seems to me that the "hard to access site settings" part (1/2) is covered by the upcoming work raymes@ described.

Now for the "site settings page is loading without user feedback" part (2/2) I'm unsure about. patricialor@, would you like this issue to be kept open as a reminder for when  issue 732907  is resolved?

I filed issue 764199 to track 1/2. 

Hopefully resolving  issue 732907  fixes 2/2. So I'm going to close this now. But please let us know if there's something missing :)

(didn't meant to change the title)