Website review, no card needed

shawfest.com logo

shawfest.com website review

Visit site (opens in a new tab)Reviewed 4 November 202641 issues · 89 checks

This review found 41 issues worth fixing on shawfest.com, 15 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
1.0 s841 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026863 ms
May 23, 2026882 ms
May 30, 2026881 ms
Jun 6, 2026893 ms
Jun 13, 2026899 ms
Jun 20, 2026886 ms
Jun 27, 2026875 ms
Jul 4, 2026870 ms
Jul 11, 2026896 ms
Jul 18, 2026922 ms
Jul 25, 2026933 ms
Aug 1, 2026952 ms
Aug 8, 2026951 ms
Aug 15, 2026957 ms
Aug 22, 2026979 ms
Aug 29, 20261.0 s
Sep 5, 2026994 ms
Sep 12, 2026964 ms
Sep 19, 2026927 ms
Sep 26, 2026911 ms
Oct 3, 2026917 ms
Oct 10, 2026943 ms
Oct 17, 20261.0 s
Oct 24, 2026993 ms
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
128 ms79 msMay 16Oct 31122 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202686 ms
May 23, 202685 ms
May 30, 202686 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202688 ms
Jun 27, 202688 ms
Jul 4, 202689 ms
Jul 11, 202692 ms
Jul 18, 202694 ms
Jul 25, 202694 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202697 ms
Aug 29, 202699 ms
Sep 5, 2026101 ms
Sep 12, 202698 ms
Sep 19, 2026102 ms
Sep 26, 2026105 ms
Oct 3, 2026112 ms
Oct 10, 2026119 ms
Oct 17, 2026121 ms
Oct 24, 2026121 ms
Oct 31, 2026122 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 shawfest.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix42
  • Reduce unused JavaScript

    2.1 s · 410 KiB

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

  • Mobile performance score: 42

    42/100

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

  • Improve image delivery

    450 ms · 1.5 MB

    11 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 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.2 MB and 1.5 s of main-thread time.

  • Render-blocking requests

    900 ms

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Google Tag Manager adds 805 ms

    805 ms

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

  • Use efficient cache lifetimes

    600 ms · 248 KiB

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 82 KiB

    About 82 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.

  • Main-thread work: 2.9 s

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

  • Legacy JavaScript

    150 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Font display

    100 ms

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

  • Minify CSS

    8 KiB

    8 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: 4 ms

    4 ms

    Your server sent the HTML in 4 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.88

    0.88

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

  • Largest Contentful Paint: 27.2 s

    27.2 s

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

  • Time to Interactive: 29.1 s

    29.1 s

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

  • Speed Index: 14.1 s

    14.1 s

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

  • First Contentful Paint: 5.2 s

    5.2 s

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

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

    +42%

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

  • Total Blocking Time: 556 ms

    556 ms

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

  • 29 images without width and height

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 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 s

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

  • Real-user INP: 102 ms

    102 ms

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 440 ms

    440 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix28
  • Page weight: 6.9 MB in 147 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 147 requests on a phone: images 5.1 MB (44), scripts 1.3 MB (51) and fonts 340 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1,007 KiB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    1.1 MB

    12 images are downloaded at several times the size a phone draws them, for example Purple_2027-Plays-600-x-900.jpg at 1,200 px wide, shown at 375 px. Resized copies would save about 1.1 MB.

  • 18 images below the first screen load straight away

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

  • About 2.0 g of CO₂ per visit

    1.97 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 7788
  • 1 button without a name

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

  • 2 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 52 form fields without a label

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

  • 19 links without text

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

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 39 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: 39 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Title is short (28 characters)

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

  • 9 links with vague text

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

  • 223 internal links, 15 external

    The homepage links to 223 pages on shawfest.com and 15 external pages.

7 checks passed
  • Meta description: 96 characters

    Your meta description is 96 characters: “World-class theatre in blissful Niagara wine country, plus countless events & activities. Ready?”.

  • One H1 headline

    Your main headline reads: “Home - Shaw Festival Theatre”.

  • Canonical URL set

    The canonical URL is https://www.shawfest.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.shawfest.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.shawfest.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.

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 (1,272 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.shawfest.com/contact-us, https://www.shawfest.com/donate, https://www.shawfest.com/2027-season, https://www.shawfest.com/playbill/rodgers-hammersteins-south-pacific, https://www.shawfest.com/playbill/arsenic-and-old-lace and https://www.shawfest.com/playbill/the-color-purple and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.shawfest.com/contact-us, whose canonical is https://www.shawfest.com/about/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 64 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 7391
  • 5 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix86
  • No social proof

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

  • About 593 words of copy

    The homepage carries about 593 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

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

  • 23 calls to action

    The homepage has 23 calls to action, for example “Contact Us”, “Contact Info” and “BUY TICKETS”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 of them by other companies (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.

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

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 shawfest.com, 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
Vue.js
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
1962

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on shawfest.com, including 19 speed issues, 2 SEO issues and 1 conversion gap. 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