It's like they used to say "the problem is not with the station, it's with your tv set"
Finding the issue was easy using the developer tools in your browser (for Firefox, a control-shift-K will open them). Reload the page with the developer tools enabled, and the Console view will show all the requests/XHR accesses.
Browse the one for the page and look at the Response headers. Most servers provide both:
Date: and
Last-modified:
with timestamps. Both your Date and Last-modified headers were showing the 2012 dates (wayback machine???).
Now they're showing properly:
HTTP/1.1 200 OK
Date: Mon, 06 May 2019 18:51:23 GMTServer: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 5500
Keep-Alive: timeout=5, max=98
Connection: Keep-Alive
Content-Type: text/html; charset=ISO-8859-1
It's missing the Last-modified header (no biggie), but the Date: header is there.
For your realtime.txt, it does include (correctly) a Last-modified: header too.
HTTP/1.1 200 OK
Date: Mon, 06 May 2019 18:55:06 GMT
Server: Apache
Last-Modified: Mon, 06 May 2019 18:54:43 GMT
ETag: "112-5883ca22725bb-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 183
Keep-Alive: timeout=5, max=97
Connection: Keep-Alive
Content-Type: text/plain