mountauburn.org website review

13 images could be 10.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.

About 639 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.3 s faster on a phone.

Your mobile performance score is 54 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

About 139 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

119 KiB could be saved by minifying CSS.

5 long tasks block the main thread while loading, the longest for 274 ms. During a long task the page ignores taps.

5 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and AddToAny and others), adding 476 KiB and 169 ms of main-thread time.

3 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 40.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 43.5 s. Good is under 3.8 s.

The first text or image appears after 6.9 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 230 ms in total while the page loads. Good is under 200 ms.

4 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 76 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.8 MB in 44 requests on a phone: images 11.2 MB (18), scripts 676 KiB (10) and stylesheets 661 KiB (9). Under 2 MB keeps phones on slow connections fast.

4 images weigh 10.1 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example DSC01177.jpg at 6,000 px wide, shown at 390 px. Resized copies would save about 8.6 MB.

11 images (11.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 3.62 g of CO₂e: 434.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h5, h1 → h5 and h1 → h5), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 21 characters: “Mount Auburn Cemetery”. 70 to 160 characters is enough to sell the click.

There are 8 <h1> headlines (“Home Page”, “Welcome to Mount Auburn” and “Locate a Grave”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 67 pages on mountauburn.org and 9 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://mountauburn.org/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://mountauburn.org/locate-a-grave, https://mountauburn.org/about, https://mountauburn.org/mission-vision, https://mountauburn.org/leadership, https://mountauburn.org/press and https://mountauburn.org/careers and 9 others use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.

15 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 695 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.