coc.ca website review

About 355 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

23 images could be 950 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

7 third-party services load with your homepage (Google Tag Manager, cloudfront.net and TikTok and others), adding 2.7 MB and 925 ms of main-thread time.

68 KiB could be saved by minifying JavaScript.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

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

cloudfront.net costs a phone 222 ms of main-thread work and 579 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.

Cloudinary costs a phone 0 ms of main-thread work and 1.5 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.

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

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

Polyfills for old browsers add 17 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.

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.

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Turn of the Screw”.

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

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

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

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

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

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-24, real Chrome visitors' tap response (inp) went from 101 ms to 99 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.8 MB in 60 requests on a phone: images 1.5 MB (24), scripts 863 KiB (9) and fonts 368 KiB (5). Under 2 MB keeps phones on slow connections fast.

9 images further down the page (291 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

1 image has no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

Your title is only 22 characters: “Canadian Opera Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

32 links have no real href, so search engines can't follow them.

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

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

The homepage links to 129 pages on coc.ca and 11 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.

/tickets/2627-season, /tickets/2627-season/la-traviata, /tickets/2627-season/cosi-fan-tutte, /tickets/2627-season/the-turn-of-the-screw, /tickets/2627-season/ariadne-auf-naxos and /tickets/2627-season/empire-of-wild and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

/tickets, /tickets/2627-season, /tickets/2627-season/cosi-fan-tutte, /tickets/2627-season/empire-of-wild, /tickets/2627-season/the-elixir-of-love and /tickets/2627-season/come-closer and 1 other took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Executing inline script violates the following Content Security Policy directive 'script-src 'self' 'unsafe-eval' 'unsa…”.

Chrome logged issues while loading the page (“Content security policy”).

1 link to other sites is dead, for example https://bsky.app/profile/canadianopera.bsky.social (404).

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

1 link go through two or more redirects, for example https://www.coc.ca/tickets/.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

coc.ca 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.

coc.ca'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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

DMARC is set to p=none, so mail pretending to be coc.ca 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 TikTok 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 15 cookies (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.