sfsymphony.org website review

About 268 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

9 images could be 471 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

About 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 570 ms faster on a phone.

7 third-party services load with your homepage (Optanon, Hotjar and Cloudflare CDN and others), adding 1.8 MB and 354 ms of main-thread time.

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

imgix costs a phone 0 ms of main-thread work and 917 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

rsms.me costs a phone 1 ms of main-thread work and 348 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

34 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

9 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-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.0 MB in 77 requests on a phone: fonts 1.3 MB (11), images 930 KiB (22) and scripts 581 KiB (26). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (93 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

6 visible links have no text or label, so screen readers cannot say where they go.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 29 characters: “San Francisco Symphony - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.sfsymphony.org/sitemap.xml, so Google discovers your pages only by following links.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 95 pages on sfsymphony.org and 7 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://www.sfsymphony.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.

Your homepage links to https://www.sfsymphony.org/Subscribe/Renewals, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.sfsymphony.org/Calendar and https://www.sfsymphony.org/calendar all use the title “San Francisco Symphony - Calendar”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.sfsymphony.org/Home/Help, https://www.sfsymphony.org/Calendar, https://www.sfsymphony.org/calendar, https://www.sfsymphony.org/Discover-the-Music/festival-pages/Films, https://www.sfsymphony.org/Buy-Tickets/Gift-Certificates and https://www.sfsymphony.org/Subscribe and 3 others use the same meta description. A description written for each page earns more clicks.

https://www.sfsymphony.org/Calendar, https://www.sfsymphony.org/Donate, https://www.sfsymphony.org/calendar, https://www.sfsymphony.org/Discover-the-Music/festival-pages/Holiday, https://www.sfsymphony.org/Discover-the-Music/festival-pages/Films and https://www.sfsymphony.org/Subscribe and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 405 words of visible text.

Before a visitor clicks anything, the page loads Hotjar (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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