I'm considering uploading my uncompressed music album on my website, which consists of about 10 songs. Each song can be up to 30mb—some are around 8mb and others around 25mb. I'm worried if this is a mistake and if it might cause loading issues for visitors.
5 Answers
It really depends on what you want to achieve. If these are high-quality downloads for users, then go ahead with something like .flac. But if they're background tracks that autoplay, consider converting them to Ogg Vorbis for better compression and less hassle.
Honestly, at 25mb per song, I’d be more concerned about the impact on mobile data use. Playing a full album could eat up a quarter of a gig, which isn't ideal for many users!
If you're planning to autoplay these, consider whether they'll be lazy loaded or not. Remember, if you’re paying for bandwidth, those file sizes can add up quickly! Just something to keep in mind.
Are you just hosting these for downloads, or will they be directly included on the page? If it’s the former, it won’t affect your page load times. Just don’t forget to check your data egress charges if you’re not using your own server!
Another option is to convert your tracks into videos, upload them to YouTube, and embed them on your site. This can save on bandwidth and make it easier for users to access the music.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads