Homepage malfunctioning in Chrome on android

[SnowingSilently]

When I go to the homepage, no manga title images load, drop down menus are missing their frame, the announcement is only in white and missing the green, and there's some other issues too. https://imgur.com/a/Qa20KN2. I've tried closing my app, restarting my device, and it's still persisting.

 

[Pika]

@SnowingSilently
Tried clearing cache yet?

 

[SnowingSilently]

@Pika
I tried it to no avail. When I load the page I'll sometimes see the images for a quick moment before they all disappear. I'm using Chrome on Android version 75.0.3770.67 if that helps.

 

[Pika]

@SnowingSilently
Do you have an anti-virus that's eehhh "doing its job"?
From what I can see, it seems to be a common issue with Kaspersky

If you do, try disabling it

 

[Teasday]

_{@SnowingSilently posted:}

When I load the page I'll sometimes see the images for a quick moment before they all disappear.

This certainly makes no sense to me without some external application or extension interfering. Pika's suggestion seems about right, especially if this happens on other browsers as well.

 

[SnowingSilently]

@Teasday

Nope, no antivirus. Unless a Samsung Galaxy Tab S2 comes with it, but I'm pretty sure I'd have disabled it already if it did. It only affects Chrome too, Firefox is just fine.

The images are also working as hyperlinks too, it just seems to be that the image isn't loading. Obviously the CSS isn't loading in some places, but I'm pretty sure the JavaScript is intact. I don't think I can inspect elements in Android.

I downloaded the Chrome Beta app and tried Mangadex, and it's also failing there. I also cleared all cached and residual files on my device with an external app, which may or may not have actually done anything (since it's by CleanMaster and I don't really trust it), but it doesn't seem to have done anything for the site.

 

[Teasday]

@SnowingSilently If both Chrome and a new installation of Chrome Beta fail, but not Firefox, then unfortunately I really have no idea. Clearly it seems like it must have something to do with Chrome, but I can't replicate it on the same Chrome version and I haven't heard of this particular issue before either. If you could use remote debugging to see if there's any clues as to what's happening, that would be great, but with the information you've given I don't know what else I could suggest.