ccmuseum.com website review

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Facebook and TVSquared and others), adding 925 KiB and 546 ms of main-thread time.

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

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

A phone's processor spends 2.5 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

13 KiB could be saved by minifying CSS.

10 long tasks block the main thread while loading, the longest for 108 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).

1 image could be 37 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Corpus Christi Museum of Science and History”.

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

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

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

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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-31, real Chrome visitors' tap response (inp) went from 108 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.1 MB in 143 requests on a phone: scripts 1.2 MB (55), fonts 399 KiB (11) and stylesheets 272 KiB (64). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example BZ-6704-scaled.webp at 2,560 px wide, shown at 330 px. Resized copies would save about 154 KiB.

1 image further down the page (181 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

9 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

3 links have no real href, so search engines can't follow them.

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

The homepage links to 44 pages on ccmuseum.com and 8 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) 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.

/visit, /museum-exhibits, /events, /education-programs, /education-programs/teachers-and-students and /education-programs/scouts and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

/visit, /museum-exhibits, /education-programs, /membership and /support-your-museum have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

5 links from your homepage to your own site are broken, for example https://www.ccmuseum.com/?page_id=23757 (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example http://instagram.com/corpuschristimuseum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ccmuseum.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

ccmuseum.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

ccmuseum.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

The homepage has only about 141 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

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.

ccmuseum.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 6 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.