Website review, no card needed
operacolorado.org website review
Visit site (opens in a new tab)Reviewed 24 October 202644 issues · 91 checks
This review found 44 issues worth fixing on operacolorado.org, 19 of them high impact, across 91 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 80 ms |
| May 9, 2026 | 83 ms |
| May 16, 2026 | 85 ms |
| May 23, 2026 | 85 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 89 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 92 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 85 ms |
| Jul 11, 2026 | 83 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 80 ms |
| Aug 8, 2026 | 85 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 85 ms |
| Aug 29, 2026 | 80 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 109 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 117 ms |
| Oct 17, 2026 | 116 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
How it loaded on a phone
0.8 s
1.7 s
2.5 s
3.4 s
4.2 s
5.0 s
5.9 s
6.7 s
Speed
Improve image delivery
2.1 s · 2.3 MB12 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
3.3 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Reduce unused JavaScript
2.4 s · 648 KiBAbout 648 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Accessibe Accessibility Overlay and others), adding 1.3 MB and 2.0 s of main-thread time.
Use efficient cache lifetimes
900 ms · 398 KiB9 files are served with short cache lifetimes, so returning visitors download them again (398 KiB).
Google Tag Manager adds 983 ms
983 msGoogle Tag Manager costs a phone 983 ms of main-thread work and 645 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.
Facebook adds 575 ms
575 msFacebook costs a phone 575 ms of main-thread work and 307 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 461 ms. During a long task the page ignores taps.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Accessibe Accessibility Overlay adds 270 ms
270 msAccessibe Accessibility Overlay costs a phone 270 ms of main-thread work and 243 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
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need.
Minify CSS
11 KiB11 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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.34
0.34For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 22.8 s
22.8 sYour largest element takes 22.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.3 s
23.3 sThe page becomes fully interactive after 23.3 s. Good is under 3.8 s.
First Contentful Paint: 6.7 s
6.7 sThe first text or image appears after 6.7 s on a phone. Good is under 1.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 43% slower for real visitors
+43%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 80 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 123 ms
123 msReal visitors wait 123 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 459 ms
459 msReal visitors wait 459 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 145 requests
5.0 MBYour homepage downloads 5.0 MB in 145 requests on a phone: images 2.7 MB (24), scripts 1.4 MB (38) and fonts 700 KiB (10). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.5 MB3 images are downloaded at several times the size a phone draws them, for example Banners-4.png at 2,000 px wide, shown at 390 px. Resized copies would save about 1.5 MB.
6 images in older formats
6 images (338 KiB) 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.
About 1.4 g of CO₂ per visit
1.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.43 g of CO₂e: 171.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
9 buttons without a name
9 buttons have no accessible name, so screen readers announce just “button”.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (21 characters)
Your title is only 21 characters: “Home - Opera Colorado”. Between 30 and 65 characters leaves room to say what you do and for whom.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
83 internal links, 20 external
The homepage links to 83 pages on operacolorado.org and 20 external pages.
7 checks passed
Meta description: 113 characters
Your meta description is 113 characters: “Bringing world-class operatic performances and educational arts programs to the Rocky Mountain region since 1981.”.
One H1 headline
Your main headline reads: “Experience the Magic of Opera”.
Canonical URL set
The canonical URL is https://www.operacolorado.org/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.operacolorado.org/sitemap_index.xml.
AI search readiness
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://www.operacolorado.org/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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (372 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.operacolorado.org/subscribe-to-newsletter is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages without a meta description
https://www.operacolorado.org/subscribe-to-newsletter, https://www.operacolorado.org/tickets-events, https://www.operacolorado.org/tickets-events/ways-to-save/group-sales, https://www.operacolorado.org/tickets-events/ways-to-save, https://www.operacolorado.org/tickets-events/seat-map and https://www.operacolorado.org/tickets-events/gift-certificates have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
41 small tap targets
41 of 65 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “jQuery(...).live is not a function”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 331 words of copy
The homepage carries about 331 words of visible text.
5 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Contact Us”, “Buy Tickets | Calendar” and “Join Our E-Mail List”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
No consent tool detected
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.
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 operacolorado.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Company
- Founded
- 1981
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on operacolorado.org, including 21 speed issues, 3 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.