Website review, no card needed

goldenvoice.com logo

goldenvoice.com website review

Visit site (opens in a new tab)Reviewed 29 October 202651 issues · 95 checks

This review found 51 issues worth fixing on goldenvoice.com, 25 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.4 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.0 s
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.5 s
Aug 8, 20261.6 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
121 ms96 msMay 9Oct 24112 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202699 ms
May 16, 2026102 ms
May 23, 2026104 ms
May 30, 2026100 ms
Jun 6, 2026104 ms
Jun 13, 2026100 ms
Jun 20, 202699 ms
Jun 27, 2026101 ms
Jul 4, 2026101 ms
Jul 11, 2026104 ms
Jul 18, 2026100 ms
Jul 25, 2026102 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026107 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026111 ms
Sep 12, 2026112 ms
Sep 19, 2026118 ms
Sep 26, 2026114 ms
Oct 3, 2026112 ms
Oct 10, 2026113 ms
Oct 17, 2026113 ms
Oct 24, 2026112 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of goldenvoice.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. goldenvoice.com at 0.4 s0.4 s
  2. goldenvoice.com at 0.8 s0.8 s
  3. goldenvoice.com at 1.1 s1.1 s
  4. goldenvoice.com at 1.5 s1.5 s
  5. goldenvoice.com at 1.9 s1.9 s
  6. goldenvoice.com at 2.3 s2.3 s
  7. goldenvoice.com at 2.6 s2.6 s
  8. goldenvoice.com at 3.0 s3.0 s

Speed

14 to fix2
  • Use efficient cache lifetimes

    21.3 s · 6.6 MB

    67 files are served with short cache lifetimes, so returning visitors download them again (6.6 MB).

  • Reduce unused JavaScript

    7.2 s · 2.3 MB

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

  • Improve image delivery

    5.1 s · 3.5 MB

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

  • Render-blocking requests

    7.5 s

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

  • Google Tag Manager adds 2.5 s

    2.5 s

    Google Tag Manager costs a phone 2.5 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    1.9 s · 565 KiB

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

  • Mobile performance score: 2

    2/100

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

  • Main-thread work: 7.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, spotifycdn.com and Azure Web Services and others), adding 16.7 MB and 4.2 s of main-thread time.

  • Azure Web Services adds 457 ms

    457 ms

    Azure Web Services costs a phone 457 ms of main-thread work and 13.2 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.

  • spotifycdn.com adds 573 ms

    573 ms

    spotifycdn.com costs a phone 573 ms of main-thread work and 789 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.

  • Font display

    500 ms

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

  • 20 long tasks on the main thread

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

  • 1,711 HTML elements

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

  • Document request latency

    101 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    41 KiB

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 40 ms

    40 ms

    Your server sent the HTML in 40 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 0.86

    0.86

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

  • First Contentful Paint: 8.5 s

    8.5 s

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

  • Largest Contentful Paint: 48.4 s

    48.4 s

    Your largest element takes 48.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Knocked Loose & Denzel Curry”.

  • Speed Index: 17.4 s

    17.4 s

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

  • Time to Interactive: 96.9 s

    96.9 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

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

  • Cumulative Layout Shift: 0.764

    0.764

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

  • 18 images without width and height

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

  • Tap response (INP) got 12% slower for real visitors

    +12%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 99 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 571 ms

    571 ms

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

  • Largest content (LCP) got 29% faster for real visitors

    -29%

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

Images and page weight

5 to fix18
  • Page weight: 18.5 MB in 238 requests

    18.5 MB

    Your homepage downloads 18.5 MB in 238 requests on a phone: other files 7.2 MB (82), scripts 5.5 MB (66) and images 4.8 MB (66). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    1.6 MB

    8 images are downloaded at several times the size a phone draws them, for example image-splatter.png at 2,772 px wide, shown at 251 px. Resized copies would save about 1.6 MB.

  • 30 images in older formats

    30 images (4.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.

  • 21 images below the first screen load straight away

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

  • About 5.3 g of CO₂ per visit

    5.25 g

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

Accessibility

9 to fixGoogle 7686
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 15 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 11 images without alt text

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

  • All page content should be contained by landmarks (73 elements)

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

  • 22 links without text

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

  • 3 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 7569
  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (300 characters)

    Your meta description is 300 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • No robots.txt

    There is no robots.txt at goldenvoice.com/robots.txt, the first file search crawlers ask for.

  • 2 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 33 internal links, 20 external

    The homepage links to 33 pages on goldenvoice.com and 20 external pages.

2 checks passed
  • Title: 60 characters

    Your title is a healthy 60 characters: “Goldenvoice - California Concert and Music Festival Promoter”.

  • XML sitemap found

    Your XML sitemap is reachable at https://goldenvoice.com/sitemap.xml.

AI search readiness

1 to fix81
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://goldenvoice.com/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.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (1,691 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 16 pages share a title

    /, https://goldenvoice.com/shows, https://goldenvoice.com/venues, https://goldenvoice.com/festivals, https://goldenvoice.com/faq and https://goldenvoice.com/cool-stuff and 10 others all use the title “Goldenvoice - California Concert and Music Festival Promoter”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://goldenvoice.com/shows, https://goldenvoice.com/venues, https://goldenvoice.com/festivals, https://goldenvoice.com/faq, https://goldenvoice.com/cool-stuff and https://goldenvoice.com/app and 9 others use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://goldenvoice.com/faq, https://goldenvoice.com/cool-stuff, https://goldenvoice.com/el-rey-theatre, https://goldenvoice.com/fonda-theatre, https://goldenvoice.com/fox-theater-pomona and https://goldenvoice.com/frost-amphitheater have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) null”.

2 checks passed
  • Tap targets are thumb-sized

    59 of 60 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • Phone number is not tap-to-call

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

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 817 words of copy

    The homepage carries about 817 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BUY TICKETS”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Learn More”, “SIGN UP NOW” and “Contact Goldenvoice”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 13 cookies set on arrival

    13

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

  • 32 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at goldenvoice.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Azure

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on goldenvoice.com, including 23 speed issues, 7 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25