150 Song Limit?

Hi Guys,

Up to Song 160 Today - 20 Songs a day added.

There seems to be a limit? of 150 songs allowed on one page?

I tried clearing caches, reloading, etc

Playing gets disabled after 150 Songs…

Any Ideas?

Eventually want the whole 365 Songs on one page… (like it was in 2006)

Now is seems to be random - some have the blue dot - and are prepared to play - and others don’t…

content blockers off
allowed media player

Latest version of Safari

Well - sites down… Safari can’t handle the page?

Not sure what’s going on now…

DreamHost?
Safari?
Song Limit?

Looks like I’m going to have to split it up….

3 pages?

120? 120? 125?

I “sucessfully” opened your page https://onesongeveryday.com in Google Chrome 142.0 , Mozilla Firefox 14.2 AND Apple Safari 18.6.
However Safari took a while to show all of the 160 (!) songs, whereas Chrome and Firefox seem to display everything almost immediately.

So there is webbrowser-dependency for sure. And it might be a local memory (I am using an Apple M1 with 16GB RAM running Mac OS 15.6.1) thing as well plus maybe internet access bandwidth (150MBit/s here).

As I already learned: Safari is not the most performant webbrowser - but it is my default one.

There obviously is no limit of 150!

However I would suggest in splitting your songs up into several pages… may I suggest to have one “song of the day” on your homepage?
And a list of months with each month have its own page and ech of these pages has 29, 30 or 31 songs included.
Or just have the list of 365 songtitles on your homepage and clicking on the title or the song number opens a new page or a modal with just this one song?
JMHSs…
Note: if Elements CMS would be an option for you one day, you could use the batch-option with “Load more…” and suitable batchsizes.

I hope not to be too confusing…

Thank You for checking! That was very nice of you…

I’ve gone to four pages

Page 1 Songs 1 - 100 (color red)

Page 2 Songs 101 - 200 (color blue)

Page 3 Songs 201 - 300 (color green)

Page 4 Songs 301 - 365 (color grey)

This seems to work a lot better…

We do need a kind of Lazy loading for this like with the images

2 Likes

Lol I looked at this thread and thought the exact same thing, if there was lazy loading available for audio files. :joy:

Great idea!

HTML’s

<audio controls preload="none" src="song.mp3"></audio>

with
preload=none browser does not fetch the audio until the user interacts (e.g., presses play).|

  • preload=metadata only fetches enough to get duration and basic info.|
  • preload=auto downloads the file proactively (eager load).|

This should work, if the Elements’ Audio Component respectively onesongeveryday,com would use the HTML >audio>-tag.

1 Like

Thank You!

That’s interesting… does it go at the top of the page?

Or into each song?

Chat GPT is also suggesting this with some code…

Shouldn’t the lazy loading be the default for audio player? Or no?