calstart.org website review

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

28 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

The page has 1,832 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

6 third-party services load with your homepage (Google Tag Manager, Cookiebot and LinkedIn Ads and others), adding 618 KiB and 278 ms of main-thread time.

About 187 KiB of JavaScript is downloaded but never used on this page.

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

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

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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.

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

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

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

Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”. Most of its time is element render delay (2.3 s).

1 image 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 79 ms to 95 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 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.8 MB in 126 requests on a phone: images 5.8 MB (36), scripts 719 KiB (68) and fonts 197 KiB (7). Under 2 MB keeps phones on slow connections fast.

9 images (1.2 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.

11 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example events-section-panel-photo.jpg at 1,800 px wide, shown at 342 px. Resized copies would save about 251 KiB.

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

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 55 pages on calstart.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 /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.

/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /home all use the title “Home - CALSTART”. Search engines can't tell which page to show for a search, so each competes with the others.

/about, /contact, /membership, /mission, /national-influence and /global-influence and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

/calstart-rebrands-as-catalyst-mobility, /home, /contact, /board-members and /leadership have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “missing ) after argument list”.

2 links to other sites are dead, for example https://twitter.com/calstart (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.

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.

calstart.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.

calstart.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.

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

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

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

DMARC is set to p=none, so mail pretending to be calstart.org is still delivered. Reports are on, so moving to quarantine is the next step.

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 LinkedIn Insight (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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