Website review, no card needed
theufl.com website review
Visit site (opens in a new tab)Reviewed 31 October 202640 issues · 78 checks
This review found 40 issues worth fixing on theufl.com, 15 of them high impact, across 78 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 178 ms |
| May 16, 2026 | 179 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 176 ms |
| Jun 13, 2026 | 169 ms |
| Jun 20, 2026 | 164 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 152 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 158 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 182 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 174 ms |
| Oct 17, 2026 | 175 ms |
| Oct 24, 2026 | 180 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
Reduce unused JavaScript
1.1 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 21
21/100Your mobile performance score is 21. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.9 s
A phone's processor spends 7.9 s on main-thread work while loading, 5.3 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, Facebook and TikTok and others), adding 2.7 MB and 1.5 s of main-thread time.
Google Tag Manager adds 747 ms
747 msGoogle Tag Manager costs a phone 747 ms of main-thread work and 1.4 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.
Use efficient cache lifetimes
450 ms · 443 KiB28 files are served with short cache lifetimes, so returning visitors download them again (443 KiB).
Render-blocking requests
850 ms25 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Improve image delivery
300 ms · 78 KiB3 images could be 78 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Facebook adds 342 ms
342 msFacebook costs a phone 342 ms of main-thread work and 215 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 266 ms. During a long task the page ignores taps.
Google CDN adds 88 ms
88 msGoogle CDN costs a phone 88 ms of main-thread work and 352 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
52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need.
Reduce unused CSS
31 KiBAbout 31 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: 12 ms
12 msYour server sent the HTML in 12 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.30
0.30For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.
Time to Interactive: 33.6 s
33.6 sThe page becomes fully interactive after 33.6 s. Good is under 3.8 s.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.324
0.324The layout shifts by 0.324 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 178 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 184 ms
184 msReal visitors wait 184 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 668 ms
668 msReal visitors wait 668 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.6 MB in 398 requests
5.6 MBYour homepage downloads 5.6 MB in 398 requests on a phone: scripts 4.3 MB (179), other files 700 KiB (130) and HTML 253 KiB (15). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 191.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 7 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. 1 more 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 (7 characters)
Your title is only 7 characters: “The UFL”. Between 30 and 65 characters leaves room to say what you do and for whom.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected end of JSON input)”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.theufl.com/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
59 internal links, 15 external
The homepage links to 59 pages on theufl.com and 15 external pages.
2 checks passed
One H1 headline
Your main headline reads: “The UFL Home Page”.
robots.txt in place
robots.txt is in place.
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.
Some text only appears after JavaScript runs
44%The HTML your server sends has 317 of the 728 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.theufl.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.
1 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.
Other pages
15 pages without a meta description
https://www.theufl.com/schedule, https://www.theufl.com/teams/columbus/schedule, https://www.theufl.com/teams/dallas/schedule, https://www.theufl.com/teams/dc/schedule, https://www.theufl.com/teams/louisville/schedule and https://www.theufl.com/teams/orlando/schedule and 9 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 40 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
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”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
66 of 70 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 728 words of copy
The homepage carries about 728 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: “SCHEDULE” and “OPEN SCHEDULE TICKER”.
7 calls to action
The homepage has 7 calls to action, for example “Schedule”, “League Schedule” and “Sign Up”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta 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.
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.
11 other companies contacted
Loading the homepage contacts 11 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 theufl.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
- Nuxt
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Google Cloud
Company
- Founded
- 2023
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 theufl.com, including 21 speed issues, 7 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.