Internal · not linked from the main navigation

Site reference

Audit results, the theme system and the analytics plan for corproadie, in one place for review. Last built Nov 14, 2026.

Performance audit

Measured with Chromium on a throttled connection (1.6 Mbps, 150 ms latency, cache off). Mobile also has 4x CPU slowdown. Same pages, same content, before and after the changes below.

Page · deviceFirst paintLargest paint (LCP)Bytes at loadLayout shiftDOM nodes
Home · mobile548 ms → 256 ms3,592 ms → 1,132 ms671 KB → 167 KB0.000 → 0.000229 → 266
Home · desktop432 ms → 256 ms6,056 ms → 1,012 ms1,174 KB → 146 KB0.000 → 0.000229 → 266
Venue Guide · mobile448 ms → 280 ms448 ms → 280 ms63 KB → 72 KB0.000 → 0.0007,024 → 1,333
Venue Guide · desktop388 ms → 244 ms388 ms → 264 ms63 KB → 72 KB0.116 → 0.0027,024 → 1,333

What the audit found

AreaFindingImpact
Uncompressed assetsNine photos shipped as single large JPEGs (1.98 MB total; the hero alone was 452 KB at 2400 px), with no AVIF or WebP and no responsive sizes. Phones downloaded desktop-size files.Highest
Synchronous loadingstyle.css was a separate render-blocking request on both pages. Every image except the hero was below the fold, but the hero had no priority hint, so it competed with tiles for bandwidth.High
Layout stabilityNo width/height on images. On the Venue Guide, the location menu and footer moved once the list rendered (CLS 0.116 on desktop).Medium
DOM sizeThe Venue Guide rendered all 124 venues with full detail panels up front: 7,024 elements, most hidden inside closed panels.Medium
Unused CSSSmall. Coverage showed about 20% of rules unused on first paint, almost all state rules (open, hover, empty). One dead rule (.tag, the old testimonial placeholder) was removed. The bigger waste was shipping one shared stylesheet as an extra request.Low
Redundant JavaScriptNone. The homepage had no JavaScript and the Venue Guide had one inline script with no imports. The only new script, analytics.js, loads with defer and pulls in gtag with async.None

Top five changes, implemented

  1. Modern image formats. Every photo is now served as AVIF with WebP and JPEG fallbacks through <picture>. The hero is 452 KB → 54 KB at the size a laptop actually shows (AVIF, 1200 px). This is the single biggest win because images were over 95% of the bytes.
  2. Responsive sizes. Each image has a srcset (480–2400 px) and a sizes rule matching the layout, so a phone picks a 480–800 px file and a retina laptop picks 1600–2400 px. Before, every device got 2400 px.
  3. Hero priority and lazy loading below the fold. The hero has fetchpriority="high" and loads eagerly; everything else is loading="lazy" and decoding="async". Every image carries its real width/height, so the browser reserves space and nothing jumps.
  4. CSS inlined, no render-blocking request. The theme tokens, shared components and page styles are minified and inlined into each page by the build (about 4 KB gzipped). First paint no longer waits on a second round trip. Below-the-fold bands use content-visibility:auto to skip their layout until scrolled near.
  5. Lighter Venue Guide. Venue data moved into a JSON block (parsed faster than a JS literal), and each venue's detail panel is built only when it is first opened. DOM nodes dropped from 7,024 to about 1,300. The location menu has a fixed width and the list reserves height, so layout shift is gone.

Still recommended when the site moves to its own host: serve HTML and JS with Brotli or gzip, set long cache headers on /img/ (file names are versioned by size), and add a CDN. The claude.ai artifact host controls those headers today.

UX review

Ranked by likely effect on a visitor, with design-focused producers and planners in mind. Items marked Fixed were addressed in this round.

#ProblemWhy it mattersFix
1Fixed: no menu on phones. Under 760 px the header shows only the logo, theme button and Contact. AV, Work, About and the Venue Guide can't be reached from the header.Most first visits from a shared link are on a phone. The Venue Guide, the most useful page for crews, becomes invisible.Fixed: a menu button at the top right (phones and tablets up to 1024 px) opens a full-width sheet with the five links, the main button, email and phone. Built on <details>, so it works without JavaScript.
2Contact depends on mailto/tel. "Email Corp Roadie" opens a mail app; on desktops without one, or inside embedded viewers, nothing happens and there is no feedback.The main conversion action fails silently for part of the audience.Keep the link, and add a "Copy email" button next to the visible address that confirms with "Copied". Track it as contact_click.
3Fixed: photo placeholders. All slots now have real show photos.Design-savvy visitors read visible placeholders as unfinished work, which undercuts a pitch built on attention to detail.Until photos arrive, hide those cards or use a plain brand-color panel with no caption. Swap in real photos when ready.
4Venue rows are hard to read as expandable. The chevron is 9 px at the far right; nothing says "details".Users skim the list, see "Updated" dates, and miss the dock, rigging and permit details that make the guide valuable.Larger chevron with a "Details" label, and make the whole row hover and focus visibly. Show 2–3 key facts (union, dock, airport) in the collapsed row.
5Venue state can't be shared. Search, location filter and the open venue are lost on refresh, and a single venue can't be linked.Producers forward venue info to crew; a link that opens the right venue saves a step and brings return visits.Give each venue an id and support #venue-name links; mirror the location filter in the hash (for example #loc-az).
6Work cards look clickable but aren't. Large image cards with titles are the standard pattern for links to case studies.Taps that do nothing feel broken and end exploration.Either link each card to a short show story (challenge, what we did, result) or drop card styling and present them as captioned photos.
7Repeated "Ask on advance". Empty fields fill the open venue panel with the same phrase.Noise hides the real details and makes entries feel thin.Hide empty fields and add one line: "Not listed yet: parking, largest room."
8No "where am I" on the long homepage. The header doesn't show the current section.On a one-page site, orientation comes from the header; without it the nav feels static.Use an IntersectionObserver to set aria-current on the matching header link as sections enter the viewport.
9Empty search result is a dead end. It says no venues match but gives no way out.Users have to find and clear the field and the filters themselves.Add a "Clear search and filters" button in the empty state. The result count is now announced to screen readers (Fixed).
10Anchor jumps hid headings under the sticky header.Clicking "AV" landed with the heading cut off.Fixed: scroll-padding-top now matches the header height.
11No dark mode. The site ignored the visitor's system setting.Expected on a modern, Apple-inspired site, and kinder to crews reading at night.Fixed: the site follows the system setting without JavaScript and has a header toggle that remembers the choice.
12Three CTA labels for one action ("Contact", "Talk about your show", "Email Corp Roadie").Minor, but consistent labels build confidence about what happens next.Use "Talk about your show" in the hero and header, and "Email Corp Roadie" only where the email address is visible.
13Footer email and phone are plain text.Visitors who scroll to the bottom expect to tap them.Make them links, or link to the contact section.

Theme system

All colors are CSS custom properties with semantic names (what a color is for, never what hue it is). Themes are generated from one Python dictionary by the build, which also checks every text and UI pairing against WCAG AA and refuses to build if any pairing fails.

How a theme is chosen

  1. No JavaScript needed on first load. :root holds the light theme. A prefers-color-scheme: dark media query swaps in the dark tokens when the visitor's system is dark.
  2. Host setting. If the page sits in a viewer that sets data-theme on the root (claude.ai does), that wins over the system setting.
  3. Root class toggle. A theme-<name> class on <html> overrides both. The header button adds it and saves the choice; a one-line inline script restores it on the next visit. Without JavaScript, steps 1 and 2 still work.

Three layers

Contrast checks (generated at build)

PairingLightDarkNeeds

Add a theme

Copy an entry in src/themes.py, change the values and rebuild. The build emits a .theme-<name> block and checks contrast. Add the name to data-themes on <html> and the header button will cycle through it. Nothing else changes.

THEMES["high-contrast"] = {
    **THEMES["light"],            # start from light
    "text-muted": "#3a3a3c",      # stronger secondary text
    "border-base": "#8e8e93",
    "link-base": "#3410c8",
    "action-bg": "#3410c8",
}
# then: python3 src/build.py
# and:  <html data-themes="light dark high-contrast">

Use the tokens in new CSS

/* Put the component on any band; it adapts automatically */
.callout{
  background: var(--card);
  color: var(--fg);
  border: 1px solid var(--border);
}
.callout a{ color: var(--link); }
.callout .hint{ color: var(--fg-muted); }

Analytics (GA4)

Tracking lives in one deferred file, analytics.js. It uses delegated listeners on the document, so it adds no handlers to existing elements and changes no behavior. Event names follow GA4 rules: lowercase snake_case, under 40 characters, and GA4's recommended names where one exists (search, select_content).

To go live: replace G-XXXXXXXXXX in analytics.js with your Measurement ID. Until then, events are still built and pushed to dataLayer and shown in the log below, but nothing is sent. Pages viewed on claude.ai can't reach Google's servers (the artifact host blocks outside scripts), so live data starts when the site is on its own domain.

Event dictionary

EventFires whenParameters
page_viewEvery page load (GA4 default)page_location, page_title
nav_clickAny header, footer or in-page link that isn't a buttonlink_text, link_url, link_location (header · menu · footer · hero · section_*), link_type (in_page · page · outbound)
cta_clickButtons and "›" text links (Contact, Talk about your show, See the work, Open the Venue Guide)link_text, link_url, link_location, link_type
contact_clickEmail or phone linkscontact_method (email · phone), link_location. No address is sent.
searchVenue search, 0.9 s after typing stops, once per new termsearch_term, results_count, listing
filter_listingLocation menu or "Has special notes" changesfilter_name, filter_value, results_count, listing
select_contentA venue or FAQ answer is openedcontent_type (venue · faq), item_id
scroll_depth25, 50, 75 and 100% of a long page (pages at least 1.5 screens tall), once eachpercent_scrolled
copy_codeA Copy button on a code samplecode_id, code_language
menu_openThe phone/tablet menu is openedlink_location
theme_changeThe header theme buttontheme

Every event also carries page_name. In GA4, register link_location, link_type, listing, filter_name, filter_value, content_type, contact_method, percent_scrolled and page_name as event-scoped custom dimensions to use them in reports. Mark contact_click as a key event.

Install snippet (already in analytics.js)

<!-- Loaded at the end of <body>, never blocks rendering -->
<script src="analytics.js" defer></script>

// inside analytics.js
var GA_MEASUREMENT_ID = "G-XXXXXXXXXX";   // your ID here
window.dataLayer = window.dataLayer || [];
function gtag(){ dataLayer.push(arguments); }
gtag("js", new Date());
gtag("config", GA_MEASUREMENT_ID);
// gtag.js itself is injected with async

Track something new

// Any page script can call the shared helper.
// It adds page_name, trims strings to 100 characters and sends to GA4.
window.crTrack("download_brochure", { file_name: "corproadie-capabilities.pdf" });

To check events in GA4, add ?ga_debug to the page URL and open Admin → DebugView.

Live event log

Every event this page sends shows here as it fires. Try a header link, a Copy button, the theme switch, or scrolling.

0 events
  1. Waiting for events…