Website review, no card needed
ensembleartsphilly.org website review
Visit site (opens in a new tab)Reviewed 29 October 202639 issues · 82 checks
This review found 39 issues worth fixing on ensembleartsphilly.org, 13 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 950 ms |
| May 16, 2026 | 938 ms |
| May 23, 2026 | 947 ms |
| May 30, 2026 | 958 ms |
| Jun 6, 2026 | 969 ms |
| Jun 13, 2026 | 972 ms |
| Jun 20, 2026 | 966 ms |
| Jun 27, 2026 | 962 ms |
| Jul 4, 2026 | 952 ms |
| Jul 11, 2026 | 976 ms |
| Jul 18, 2026 | 965 ms |
| Jul 25, 2026 | 976 ms |
| Aug 1, 2026 | 949 ms |
| Aug 8, 2026 | 921 ms |
| Aug 15, 2026 | 923 ms |
| Aug 22, 2026 | 924 ms |
| Aug 29, 2026 | 949 ms |
| Sep 5, 2026 | 959 ms |
| Sep 12, 2026 | 947 ms |
| Sep 19, 2026 | 936 ms |
| Sep 26, 2026 | 934 ms |
| Oct 3, 2026 | 937 ms |
| Oct 10, 2026 | 944 ms |
| Oct 17, 2026 | 954 ms |
| Oct 24, 2026 | 967 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 118 ms |
| May 16, 2026 | 117 ms |
| May 23, 2026 | 114 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 101 ms |
| Oct 17, 2026 | 102 ms |
| Oct 24, 2026 | 104 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
1.4 s
2.7 s
4.1 s
5.4 s
6.8 s
8.1 s
9.5 s
10.9 s
Speed
Reduce unused JavaScript
2.5 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
1.6 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 1.2 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.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 3.0 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, YouTube and reddit and others), adding 2.7 MB and 2.4 s of main-thread time.
Improve image delivery
900 ms · 1.3 MB19 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 121 KiB22 files are served with short cache lifetimes, so returning visitors download them again (121 KiB).
YouTube adds 440 ms
440 msYouTube costs a phone 440 ms of main-thread work and 987 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.
reddit adds 412 ms
412 msreddit costs a phone 412 ms of main-thread work and 38 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.
cloudfront.net adds 355 ms
355 mscloudfront.net costs a phone 355 ms of main-thread work and 378 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.
Legacy JavaScript
300 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
1,564 HTML elements
The page has 1,564 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 157 KiBAbout 157 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.
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.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.5 s
14.5 sYour largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 28.4 s
28.4 sThe page becomes fully interactive after 28.4 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, 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).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 106 ms
106 msReal visitors wait 106 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 658 ms
658 msReal visitors wait 658 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 118 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.08
0.08The layout barely moves while loading (CLS 0.08, good is under 0.1).
Images and page weight
Page weight: 4.8 MB in 153 requests
4.8 MBYour homepage downloads 4.8 MB in 153 requests on a phone: scripts 2.4 MB (29), images 1.9 MB (56) and fonts 168 KiB (5). Under 2 MB keeps phones on slow connections fast.
11 images below the first screen load straight away
11 images further down the page (484 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
15 KiB1 image is downloaded at several times the size a phone draws it, for example phantom_of_the_opera at 1,000 px wide, shown at 282 px. Resized copies would save about 15 KiB.
About 1.3 g of CO₂ per visit
1.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.35 g of CO₂e: 161.6 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (57 elements)
All page content should be contained by landmarks: 57 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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (20 characters)
Your title is only 20 characters: “Ensemble Arts Philly”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
114 internal links, 21 external
The homepage links to 114 pages on ensembleartsphilly.org and 21 external pages.
3 checks passed
One H1 headline
Your main headline reads: “Ensemble Arts Philly”.
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.ensembleartsphilly.org/sitemap.
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.ensembleartsphilly.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 (923 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.ensembleartsphilly.org/support-ensemble-arts-philly/donate is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
12 pages without a meta description
https://www.ensembleartsphilly.org/meta/privacy-policy, https://www.ensembleartsphilly.org/meta/terms-of-use, https://www.ensembleartsphilly.org/support-ensemble-arts-philly/donate, https://www.ensembleartsphilly.org/tickets-and-events/ensemble-arts-philly-presents, https://www.ensembleartsphilly.org/tickets-and-events/philadelphia-orchestra and https://www.ensembleartsphilly.org/tickets-and-events/free-events and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages slow to respond
https://www.ensembleartsphilly.org/tickets-and-events/ensemble-arts-philly-presents, https://www.ensembleartsphilly.org/tickets-and-events/free-events and https://www.ensembleartsphilly.org/tickets-and-events/group-sales took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 86 found) and read each the way a search engine does.
5 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
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 12 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 third-party cookies
6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 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' 'nonc…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 574 words of copy
The homepage carries about 574 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: “Learn more in our Privacy Policy”.
10 calls to action
The homepage has 10 calls to action, for example “Learn more in our Privacy Policy”, “Curtain Call” and “Contact Us”.
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Pinterest Tag 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
27 other companies contacted
Loading the homepage contacts 27 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 ensembleartsphilly.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
- Silverstripe CMS 5.1
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on ensembleartsphilly.org, including 18 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.