creativityexplored.org website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.5 s faster on a phone.

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

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

8 third-party services load with your homepage (Squarespace, Google Tag Manager and fundraiseup.com and others), adding 2.8 MB and 1.2 s of main-thread time.

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

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

Squarespace costs a phone 526 ms of main-thread work and 1.3 MB 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 81 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.

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

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

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

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

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

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.

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

Your largest element takes 23.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By using this website, you agree to our use of cookies. We …”.

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

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

Real visitors wait 845 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 3.8 MB in 135 requests on a phone: scripts 2.6 MB (77), images 786 KiB (14) and stylesheets 203 KiB (22). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example CE+artist+Hung+Kei+Shiu,+a+man+of+Asian+descent,++drawing+in at 1,500 px wide, shown at 390 px. Resized copies would save about 35 KiB.

1 image further down the page (24 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 1.09 g of CO₂e: 130.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

Your title is only 19 characters: “Creativity Explored”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“\ Art changes lives” and “CE Residency@ Yerba Buena Center for the Arts”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5efcf0787e8ae42dfd7…”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 74 pages on creativityexplored.org and 7 external pages.

Your Organization JSON-LD is missing name, url, logo and description. 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 /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.

/camp-imaginate and /youth all use the title “Camp Imaginate ∖ Creativity Explored”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/camp-imaginate, /imaginate-yay, /imaginate-teen, /ways-to-partner, /become-a-community-partner and /partner-individuals and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /youth, whose canonical is /camp-imaginate. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/camp-imaginate, /become-a-community-partner, /partner-individuals, /shop-homepage, /youth and /visit-us have no <h1> headline, so visitors and search engines get no clear main topic.

/partner-individuals and /shop-homepage have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'replace')”.

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.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

2 links go through two or more redirects, for example http://www.facebook.com/creativityexplored.

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.

creativityexplored.org 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.

creativityexplored.org'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.

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

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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 13 cookies, 1 of them by other companies (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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.