How Funeral Home Obituary Pages Work
Most local funeral homes run obituary pages through simple CMS platforms. The slideshow you see on these sites is usually just a basic JavaScript carousel pulling images from the photographer or family's uploads. Asper Funeral Home in Pennsylvania operates this way, with families submitting photos and text that get reviewed before going live. I spent time tracking down how these pages are actually built. The "sliders" people ask about aren't a special proprietary product. They're standard HTML5 sliders — Slick, Swiper, or similar — embedded into whatever template the funeral home uses. The obituary content itself lives in the CMS, and the slider is a separate widget. What confuses most people is the formatting. Images get cached, text gets truncated at weird character counts, and the whole thing breaks if someone uploads a 4000-pixel photo that loads slowly on mobile. I once worked with a family who wanted their service program scanned and added to the obituary page. The scan came in as a full PDF. The funeral home's system accepted image uploads only, so I converted each page to a compressed JPG, resized to 1200 pixels wide, and uploaded them individually. The slider handled them fine after that. Taking the PDF approach would have been rejected outright or caused layout issues for visitors.
What You Need to Know Before Building One
The technical setup is straightforward. Most funeral home software packages like FuneralTech, Legacy, or even WordPress with the right theme will handle the slider portion. The real work is in the obituary content itself — biographical accuracy, surviving family listing, service details, and getting the photo resolution right. Text should run between 200 and 600 words. Anything longer gets skimmed. Anything shorter feels incomplete to readers who are already in a grieving headspace. One thing nobody tells you upfront: the photo filename matters more than you'd expect. If the file is named IMG_8472.jpg, the page loads fine but it looks unprofessional. Renaming to something like jane-doe-memorial.jpg before uploading makes the page cleaner and helps with any future archive work. Also, make sure the obituary and slider load in the same color temperature. Warmer photos on a cold white background looks unintentional and cheap.
Common Problems and How to Fix Them
Mobile layout breaks are the number one issue. Sliders often don't auto-scale properly on smaller screens, which means images get cut off or the navigation arrows disappear. Testing on an actual phone before publishing catches this 90% of the time. The second issue is broken image links after migration. If the funeral home ever changes their web host or CMS platform, old slider image URLs die unless you update them all. Keep a backup spreadsheet of every image URL and its corresponding obituary. Speed is another factor people overlook. A slider with five high-res photos can add several seconds to page load time. That matters because many visitors are on cellular data at 2 AM when someone they know passes away. Compressing images to under 200KB each without losing visible quality keeps the page fast. Tools like Squoosh or ShortPixel do this automatically during upload.
Get the Full Details
Where to Find Existing Obituaries
If you're looking for records from Asper Funeral Home specifically, the obituaries are typically hosted on the funeral home's own website under the obituaries section. They may also appear on memorial sites like Legacy.com if the family chose to cross-post. Some records are also available through local newspaper archives, particularly for older entries. The exact archive date depends on how far back the funeral home has digitized their records. For anyone trying to access historical obituaries that may have been lost during a website redesign, checking the Wayback Machine at archive.org is worth a try. Funeral home sites don't always keep perfect backups of old pages.
