Website review, no card needed
houstondynamofc.com website review
Visit site (opens in a new tab)Reviewed 29 October 202651 issues · 93 checks
This review found 51 issues worth fixing on houstondynamofc.com, 22 of them high impact, across 93 checks. The most urgent: use efficient cache lifetimes. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 155 ms |
| May 16, 2026 | 159 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 159 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 156 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 170 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 174 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 174 ms |
| Sep 12, 2026 | 176 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 187 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 179 ms |
| Oct 24, 2026 | 160 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.9 s
3.9 s
5.8 s
7.8 s
9.7 s
11.6 s
13.6 s
15.5 s
Speed
Use efficient cache lifetimes
12.8 s · 8.8 MB183 files are served with short cache lifetimes, so returning visitors download them again (8.8 MB).
Reduce unused JavaScript
6.8 s · 6.7 MBAbout 6.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.
Render-blocking requests
4.9 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.9 s.
Minify JavaScript
2.2 s · 464 KiB464 KiB could be saved by minifying JavaScript.
Main-thread work: 18.9 s
A phone's processor spends 18.9 s on main-thread work while loading, 9.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
1.4 s · 334 KiBAbout 334 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Duplicated JavaScript
1.1 s · 104 KiB104 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 1.1 s faster on a phone.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 864 KiB 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: 25
25/100Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, gofevo.com and Google/Doubleclick Ads and others), adding 10.6 MB and 4.4 s of main-thread time.
Improve image delivery
100 ms · 2.6 MB13 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.7 s. During a long task the page ignores taps.
gofevo.com adds 844 ms
844 msgofevo.com costs a phone 844 ms of main-thread work and 5.9 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.
Google/Doubleclick Ads adds 506 ms
506 msGoogle/Doubleclick Ads costs a phone 506 ms of main-thread work and 615 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.
Facebook adds 460 ms
460 msFacebook costs a phone 460 ms of main-thread work and 423 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.
zip.co adds 424 ms
424 mszip.co costs a phone 424 ms of main-thread work and 441 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,758 HTML elements
The page has 1,758 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 30 KiB30 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: 43 ms
43 msYour server sent the HTML in 43 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 CLS: 0.52
0.52For real visitors the layout shifts by 0.52 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 44.9 s
44.9 sYour largest element takes 44.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners use cookies, pixels, and similar tracki…”.
Speed Index: 40.0 s
40.0 sVisually, the page fills in at 40.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 5.2 s
5.2 sScripts block taps and scrolling for 5.2 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 114.3 s
114.3 sThe page becomes fully interactive after 114.3 s. Good is under 3.8 s.
First Contentful Paint: 7.0 s
7.0 sThe first text or image appears after 7.0 s on a phone. Good is under 1.8 s.
Real-user INP: 209 ms
209 msReal visitors wait 209 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 155 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 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 FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 730 ms
730 msReal visitors wait 730 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 19.7 MB in 473 requests
19.7 MBYour homepage downloads 19.7 MB in 473 requests on a phone: scripts 13.3 MB (188), images 3.6 MB (82) and other files 1.1 MB (136). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
dnlsblfxemkbzomklx5w is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images far larger than shown
87 KiB2 images are downloaded at several times the size a phone draws them, for example dnlsblfxemkbzomklx5w at 1,280 px wide, shown at 358 px. Resized copies would save about 87 KiB.
3 images in older formats
3 images (285 KiB) 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 5.6 g of CO₂ per visit
5.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.58 g of CO₂e: 670.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
[role="img"] and [role="image"] elements must have alternative text (12 elements)
[role="img"] and [role="image"] elements must have alternative text: 12 elements on the page fail this check, rated serious by axe-core.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 6 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 (17 characters)
Your title is only 17 characters: “Houston Dynamo FC”. 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.
Meta description is long (165 characters)
Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
97 internal links, 59 external
The homepage links to 97 pages on houstondynamofc.com and 59 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.houstondynamofc.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.houstondynamofc.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://www.houstondynamofc.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 (532 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share a title
/, https://www.houstondynamofc.com/video/latest/index, https://www.houstondynamofc.com/youthprograms, https://www.houstondynamofc.com/club/partners/houston-dynamo-partners, https://www.houstondynamofc.com/club/partners/associatepartners and https://www.houstondynamofc.com/mediaresources all use the title “Houston Dynamo FC”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
https://www.houstondynamofc.com/tickets, https://www.houstondynamofc.com/news/topics/dynamo-fc, https://www.houstondynamofc.com/video/latest/index, https://www.houstondynamofc.com/charities, https://www.houstondynamofc.com/youthprograms and https://www.houstondynamofc.com/academy and 4 others use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.houstondynamofc.com/schedule, whose canonical is https://www.houstondynamofc.com/schedule/matches. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.houstondynamofc.com/dynamo2 has no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.houstondynamofc.com/news/topics/dynamo-fc, https://www.houstondynamofc.com/video/latest/index, https://www.houstondynamofc.com/shell-energy-stadium, https://www.houstondynamofc.com/charities, https://www.houstondynamofc.com/youthprograms and https://www.houstondynamofc.com/dynamo2 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
4 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.
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
11 small tap targets
11 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “ErrorUtils caught an error: Cannot read properties of undefined (reading 'id') Subsequent non-fatal errors won't be log…”.
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
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 508 words of copy
The homepage carries about 508 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Schedule”.
13 calls to action
The homepage has 13 calls to action, for example “Schedule”, “Book Diesel” and “Shop”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
26 cookies set on arrival
26Opening the homepage sets 26 cookies, 1 of them by other companies (measured from a US location before any click).
66 other companies contacted
Loading the homepage contacts 66 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 houstondynamofc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Akamai
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on houstondynamofc.com, including 26 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.