Website review, no card needed
ballet.org.uk website review
Visit site (opens in a new tab)Reviewed 31 October 202642 issues · 79 checks
This review found 42 issues worth fixing on ballet.org.uk, 14 of them high impact, across 79 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
63D- #114,936 of 120,981 reviewed websitesbeats 4%
- #66,960 of 68,471 online storesbeats 2%
- #2,646 of 2,803 WooCommerce storesbeats 4%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 118 ms |
| May 16, 2026 | 116 ms |
| May 23, 2026 | 115 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 115 ms |
| Jun 13, 2026 | 118 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 144 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 156 ms |
| Oct 24, 2026 | 164 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.7 s
1.4 s
2.1 s
2.9 s
3.6 s
4.3 s
5.0 s
5.7 s
Speed
Reduce unused JavaScript
2.6 s · 478 KiBAbout 478 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Render-blocking requests
1.6 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.5 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, TikTok and cloudflare.com and others), adding 1.0 MB and 1.3 s of main-thread time.
Google Tag Manager adds 992 ms
992 msGoogle Tag Manager costs a phone 992 ms of main-thread work and 682 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 381 ms. During a long task the page ignores taps.
Minify JavaScript
300 ms · 37 KiB37 KiB could be saved by minifying JavaScript.
TikTok adds 265 ms
265 msTikTok costs a phone 265 ms of main-thread work and 271 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,732 HTML elements
The page has 1,732 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 39 KiB1 file is served with short cache lifetimes, so returning visitors download them again (39 KiB).
Reduce unused CSS
150 ms · 28 KiBAbout 28 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.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
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: 178 ms
178 msYour server sent the HTML in 178 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 LCP: 4.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 15.4 s
15.4 sYour largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Come behind the scenes with us for our World Ballet Day str…”.
Time to Interactive: 15.4 s
15.4 sThe page becomes fully interactive after 15.4 s. Good is under 3.8 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.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Tap response (INP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 118 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 164% slower for real visitors
+164%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.2 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.177
0.177The layout shifts by 0.177 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Images and page weight
Page weight: 2.3 MB in 70 requests
2.3 MBYour homepage downloads 2.3 MB in 70 requests on a phone: scripts 1.2 MB (23), other files 630 KiB (25) and HTML 231 KiB (2). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 77.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
23 tap targets too small
23 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (23 characters)
Your title is only 23 characters: “English National Ballet”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
143 internal links, 12 external
The homepage links to 143 pages on ballet.org.uk and 12 external pages.
6 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “We open up the possibilities of ballet - to move more people, in more ways. Discover our upcoming performances, dance c…”.
Canonical URL set
The canonical URL is https://www.ballet.org.uk/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, 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.ballet.org.uk/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.ballet.org.uk/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,207 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a meta description
https://www.ballet.org.uk/whats-on, https://www.ballet.org.uk/move-with-us, https://www.ballet.org.uk/move-with-us/dance-classes, https://www.ballet.org.uk/move-with-us/dance-for-health, https://www.ballet.org.uk/whats-on-classes and https://www.ballet.org.uk/move-with-us/schools-colleges and 6 others 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 69 found) and read each the way a search engine does.
6 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.
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
15 small tap targets
15 of 72 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 “%c%d font-size:0;color:transparent NaN”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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.
A 12-field form
Your longest form asks for 12 fields (3 required). Every extra field lowers completion.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 791 words of copy
The homepage carries about 791 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Online Shop”.
7 calls to action
The homepage has 7 calls to action, for example “Online Shop”, “Learn more” and “Sign up”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before 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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
14 other companies contacted
Loading the homepage contacts 14 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 ballet.org.uk, 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
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- Freethought
Company
- Employees
- 237
- Founded
- 1950
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on ballet.org.uk, including 24 speed issues, 3 SEO issues and 5 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.