Ok this time I HAVE fixed it, I'm about 68% sure :-D
No seriously, I got my hands on a Crapple Mini, very old one, and did some testing. I noticed when opening Jinx's profile it was slooowwww. But, it did work, just slowly, very slowly.
I then edited the code to show only a maximum of 200 photos. Then when I refreshed the page, it worked fine.
The problem seems to be that Apple is just crap, as always. It cannot handle Jinx's 1,000 or so photos. Downloading that many thumbnails just killed caused it to struggle.
But... the browser (Safari) should not even be downloading ALL the photos. Or so it was programmed. It should only download the thumbnails for the profile photos album. Then thumbnails for other albums should only download when you select them albums.
Buuuuuut, as usual, Safari/Apple don't support web features that are over a year old. Even in the very latest Safari version. So I could advise to update your browser, but it would make no difference.
I have, however, been able to change some of the scripts to give a similar effect. It's no miracle solution and on Safari you're always going to get a poorer experience (not my fault, it's just Safari doesn't support modern web standards).
On this Crapple Mini (from about 6 or 7 years ago) I can now browse profiles ok, even Jinx's. However, it's still a poor quality device, so if I was to open every single album on Jinx's profile then it would start to get slower and slower until it's not usable.
The ultimate solution: Install Chrome!!!!!!
But for those who have been having problems opening Jinx's profile, please can you try again for me? Note: I've only fixed the NEW website. And that took me long enough. I cannot simple copy/paste the fix over to the old website sadly. Direct link: http://beta.bikermatch.co.uk/profiles/view-profile.asp?user_id=48472
If they can view all the gory details, i may have considerably fewer 'happy bunny' fan-ettes...perhaps it's the 'Man Of Mystery ' bit they go for....hmmm
555byker - not every browser supports it yet. I've just realised that it's only supported in Firefox, Chrome and Opera. You can follow the status here: http://caniuse.com/#=serviceworkers
Well, that's kinda gonna help. Service Workers are not entirely it. Your browser could support service workers and still not give you the button for "progressive web app" installation.
It's just that Apple is behind with everything as usual (link above demonstrates it nicely. Chrome has had this feature on Android for years).
Google "Progressive Web App IOS" for news. For example: https://cloudfour.com/thinks/apple-starts-work-on-progressive-web-apps/
Seems Apple started work on it in August haha.
Tip: Stop using Apple ;-)
She11 - Did you upgrade to IOS? I'm curious if anyone with IOS 10 can view Jinx's profile.
FYI, 2.97% of people on BikerMatch use IOS 11, 1.33% use IOS 10, and 1.64% use IOS 9. So there's no need to panic, Jinx.
Me? Panic?Nah?Rant ,stamp feet maybe...but negatory on the panicky stuff...i reserve that for 1st dates....heehee :)...oh by the way,the emoticons link i have won't let me copy/paste onto forum posts on here....poo :(
Right.... I've spent at least 10 hours today investigating this damn Apple issue. Going around in circles, completely not understanding what the hell is going on. I have an iPhone which works fine and an iPad which doesn't.
After finally giving up I decided to search online. And, low and behold.... it's a BUG!!
https://bugs.webkit.org/show_bug.cgi?id=173719
In Apple/Safari/IOS.
More info here: https://forums.iis.net/t/1235574.aspx?Response+Flush+not+working+on+SSL+site+in+classic+ASP
I am trying to find a workaround. But, basically, IOS cannot handle large pages. :-( Pathetic
Good news: I can 'fix' all our profiles by disabling compression on the ENTIRE site.
Bad news: Doing that causes Google to punish us for not having an efficient site :-( Drops our Google rating from 95% mobile-friendly to just 52% (with a big red warning saying to enable compression).
Dammit, now I have to choose between the lesser of 2 evils. And why? Because Apple is a pile of shit as always!
Yea I'm seeing the same thing - I just don't know how. The fix I implemented really should have fixed it. The problem was clear to me that IOS 9 and IOS 10 didn't support dynamic compression on large pages... so I disabled it. I'll investigate some more