okeeffemuseum.org website review

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

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

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

287 KiB could be saved by minifying JavaScript.

Your mobile performance score is 43 (desktop: 77). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

Google Tag Manager costs a phone 189 ms of main-thread work and 327 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.

3 third-party services load with your homepage (Google Tag Manager, New Relic and Google Analytics), adding 387 KiB and 229 ms of main-thread time.

1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

Desktop scores 77 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

8 KiB could be saved by minifying CSS.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Discover the Art & Life of Georgia O'Keeffe”.

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

The layout shifts by 0.677 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

The first text or image appears after 2.0 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-17, real Chrome visitors' tap response (inp) went from 83 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.3 MB in 38 requests on a phone: images 3.1 MB (11), scripts 998 KiB (8) and fonts 117 KiB (3). Under 2 MB keeps phones on slow connections fast.

CR1022_CCCR.jpg weighs 2.4 MB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example CR1022_CCCR.jpg at 2,000 px wide, shown at 353 px. Resized copies would save about 2.0 MB.

7 images (3.1 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.

6 images further down the page (714 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 1.23 g of CO₂e: 147.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is only 27 characters: “The Georgia O'Keeffe Museum”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 51 characters: “The Georgia O'Keeffe Museum in Santa Fe New Mexico.”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 74 pages on okeeffemuseum.org and 10 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.okeeffemuseum.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://www.okeeffemuseum.org/visit, https://www.okeeffemuseum.org/frequently-asked-questions, https://www.okeeffemuseum.org/art-and-research, https://www.okeeffemuseum.org/collections-loans-artwork-research-support, https://www.okeeffemuseum.org/homes and https://www.okeeffemuseum.org/library-and-archive and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.okeeffemuseum.org/tickets-tours and https://www.okeeffemuseum.org/visitor-information use the same meta description. A description written for each page earns more clicks.

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

10 images failed to load on a phone, for example https://www.okeeffemuseum.org/.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 611 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 11 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.