Website review, no card needed
angelcityfc.com website review
Visit site (opens in a new tab)Reviewed 3 November 202640 issues · 88 checks
This review found 40 issues worth fixing on angelcityfc.com, 9 of them high impact, across 88 checks. The most urgent: page weight: 22.1 MB in 182 requests. 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
86BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 105 ms |
| May 30, 2026 | 108 ms |
| Jun 6, 2026 | 109 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 114 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 111 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 118 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 119 ms |
| Oct 24, 2026 | 119 ms |
| Oct 31, 2026 | 121 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
Speed
Main-thread work: 20.5 s
A phone's processor spends 20.5 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
7.4 MB24 images could be 7.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
2.3 MB81 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google/Doubleclick Ads, hubspotusercontent-na1.net and Google Tag Manager and others), adding 1.5 MB and 1.6 s of main-thread time.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Google/Doubleclick Ads adds 841 ms
841 msGoogle/Doubleclick Ads costs a phone 841 ms of main-thread work and 1.2 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.
Render-blocking requests
950 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused JavaScript
456 KiBAbout 456 KiB of JavaScript is downloaded but never used on this page.
hubspotusercontent-na1.net adds 418 ms
418 mshubspotusercontent-na1.net costs a phone 418 ms of main-thread work and 1 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.
2,344 HTML elements
The page has 2,344 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 194 ms. During a long task the page ignores taps.
Reduce unused CSS
15 KiBAbout 15 KiB of CSS is downloaded but never applied on this page.
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: 45 ms
45 msYour server sent the HTML in 45 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.
Time to Interactive: 22.3 s
22.3 sThe page becomes fully interactive after 22.3 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 689 ms
689 msScripts block taps and scrolling for 689 ms in total while the page loads. Good is under 200 ms.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
24 images without width and height
24 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “2027 Season Tickets on Sale Now”. Most of its time is element render delay (3.4 s).
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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 2.3 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user TTFB: 302 ms
302 msReal visitors wait 302 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.034
0.034The layout barely moves while loading (CLS 0.034, good is under 0.1).
Images and page weight
Page weight: 22.1 MB in 182 requests
22.1 MBYour homepage downloads 22.1 MB in 182 requests on a phone: images 19.8 MB (61), scripts 1.3 MB (37) and fonts 732 KiB (9). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
1.3 MB5 images are downloaded at several times the size a phone draws them, for example BAY-Primary.png at 1,920 px wide, shown at 20 px. Resized copies would save about 1.3 MB.
6 images in older formats
6 images (1.3 MB) 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 6.3 g of CO₂ per visit
6.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.26 g of CO₂e: 751.5 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (14 elements)
ARIA role should be appropriate for the element: 14 elements on the page fail this check, rated minor by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
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 93 images in the HTML carry an alt attribute.
46 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: 46 passed and 6 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
183 internal links, 67 external
The homepage links to 183 pages on angelcityfc.com and 67 external pages.
6 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Angel City Football Club - Los Angeles' professional women's soccer team in the NWSL. Your destination for tickets, new…”.
One H1 headline
Your main headline reads: “Quarterfinal Watch Party”.
Title: 31 characters
Your title is a healthy 31 characters: “Angel City Football Club | NWSL”.
Canonical URL set
The canonical URL is https://angelcity.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://angelcity.com/sitemap.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://angelcity.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,328 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://angelcity.com/tickets/season-tickets and https://angelcity.com/tickets/seasontickets all use the title “Season Tickets | Angel City”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://angelcity.com/tickets/season-tickets and https://angelcity.com/tickets/seasontickets use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://angelcity.com/tickets/seasontickets, whose canonical is https://angelcity.com/tickets/season-tickets. 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 59 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://angelcity.com/styles.css' because its MIME type ('text/html') is not a supported s…”.
Pasting is blocked
A form field blocks pasting, which frustrates password managers and people on phones.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
59 of 61 tappable elements near the top are at least 24 px.
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: 29 customer or partner logos. 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 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.
About 1,145 words of copy
The homepage carries about 1,145 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ANGEL CITY FC Download the app! GET” and “Shop”.
21 calls to action
The homepage has 21 calls to action, for example “Angel City FC Download the app! GET”, “BUY TICKETS” and “Next Match: vs BUY TICKETS”.
4 short forms
4 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
31 other companies contacted
Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 angelcityfc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Hiring
- Hiring
- 4 open roles
- Teams
- Data (1), FC Medical Team (1), FC Performance Team (1), Revenue (1)
- Job board
- greenhouse
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on angelcityfc.com, including 18 speed issues, 3 SEO issues and 4 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.