Website review, no card needed

rtsports.com logo

rtsports.com website review

Visit site (opens in a new tab)Reviewed 11 October 202628 issues · 79 checks

This review found 28 issues worth fixing on rtsports.com, 6 of them high impact, across 79 checks. The most urgent: page weight: 16.3 MB in 60 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
909 ms702 msApr 18Oct 3726 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026810 ms
Apr 25, 2026796 ms
May 2, 2026785 ms
May 9, 2026781 ms
May 16, 2026780 ms
May 23, 2026776 ms
May 30, 2026779 ms
Jun 6, 2026774 ms
Jun 13, 2026773 ms
Jun 20, 2026762 ms
Jun 27, 2026764 ms
Jul 4, 2026759 ms
Jul 11, 2026749 ms
Jul 18, 2026749 ms
Jul 25, 2026768 ms
Aug 1, 2026807 ms
Aug 8, 2026843 ms
Aug 15, 2026882 ms
Aug 22, 2026885 ms
Aug 29, 2026884 ms
Sep 5, 2026852 ms
Sep 12, 2026807 ms
Sep 19, 2026760 ms
Sep 26, 2026730 ms
Oct 3, 2026726 ms
Real-visitor tap response (INP)75th percentile, phones
88 ms69 msApr 18Oct 386 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202672 ms
Apr 25, 202671 ms
May 2, 202671 ms
May 9, 202671 ms
May 16, 202671 ms
May 23, 202671 ms
May 30, 202671 ms
Jun 6, 202671 ms
Jun 13, 202671 ms
Jun 20, 202671 ms
Jun 27, 202672 ms
Jul 4, 202674 ms
Jul 11, 202676 ms
Jul 18, 202678 ms
Jul 25, 202679 ms
Aug 1, 202679 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202681 ms
Sep 5, 202686 ms
Sep 12, 202686 ms
Sep 19, 202685 ms
Sep 26, 202685 ms
Oct 3, 202686 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

Full-page screenshot of rtsports.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rtsports.com at 0.4 s0.4 s
  2. rtsports.com at 0.8 s0.8 s
  3. rtsports.com at 1.1 s1.1 s
  4. rtsports.com at 1.5 s1.5 s
  5. rtsports.com at 1.9 s1.9 s
  6. rtsports.com at 2.3 s2.3 s
  7. rtsports.com at 2.6 s2.6 s
  8. rtsports.com at 3.0 s3.0 s

Speed

8 to fix55
  • Render-blocking requests

    1.5 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Use efficient cache lifetimes

    300 ms · 10.3 MB

    3 files are served with short cache lifetimes, so returning visitors download them again (10.3 MB).

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 77). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    450 ms · 389 KiB

    10 images could be 389 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google CDN and reddit and others), adding 4.1 MB and 299 ms of main-thread time.

  • Reduce unused JavaScript

    460 ms · 134 KiB

    About 134 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 3.8 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.

  • Reduce unused CSS

    300 ms · 66 KiB

    About 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify CSS

    7 KiB

    7 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.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 254 ms of it running JavaScript. That is comfortably low.

  • Server response: 29 ms

    29 ms

    Your server sent the HTML in 29 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • First Contentful Paint: 23.7 s

    23.7 s

    The first text or image appears after 23.7 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 30.2 s

    30.2 s

    Your largest element takes 30.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “RealTime Fantasy Sports”.

  • Speed Index: 23.7 s

    23.7 s

    Visually, the page fills in at 23.7 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 30.6 s

    30.6 s

    The page becomes fully interactive after 30.6 s. Good is under 3.8 s.

  • Tap response (INP) got 20% slower for real visitors

    +20%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 72 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 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.3 s

    1.3 s

    Real visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 60 ms

    60 ms

    Real visitors wait 60 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.6 s

    0.6 s

    Real visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 380 ms

    380 ms

    Real visitors wait 380 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 16.3 MB in 60 requests

    16.3 MB

    Your homepage downloads 16.3 MB in 60 requests on a phone: media 10.4 MB (1), fonts 4.0 MB (3) and images 1.6 MB (35). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (179 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.

  • 3 images below the first screen load straight away

    3 images further down the page (148 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.6 g of CO₂ per visit

    4.62 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.62 g of CO₂e: 555.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9697
  • All page content should be contained by landmarks (16 elements)

    All page content should be contained by landmarks: 16 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 (h1 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 10077
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Fantasy Football Baseball Basketball and DFS | RealTime Fantasy Sports”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 H1 headlines

    There are 6 <h1> headlines (“DRAFT. PLAY. WIN.”, “SEASON LONG MONEY LEAGUES” and “DFS PICKEM”). One clear main headline is easier for people and search engines.

  • 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 111 internal links, 8 external

    The homepage links to 111 pages on rtsports.com and 8 external pages.

3 checks passed
  • Meta description: 109 characters

    Your meta description is 109 characters: “RealTime Fantasy Sports - Fantasy Football, Baseball, Basketball, Best Ball, plus Daily Fantasy Sports (DFS).”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://www.rtsports.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://rtsports.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,078 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 7 pages share 2 titles

    /, https://rtsports.com/free-football-mock-draft, https://rtsports.com/free-baseball-mock-draft and https://rtsports.com/free-basketball-mock-draft all use the title “Fantasy Football Baseball Basketball and DFS | RealTime Fantasy Sports”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://rtsports.com/football-draft-times, https://rtsports.com/fantasy-football-leagues, https://rtsports.com/free-football-mock-draft, https://rtsports.com/baseball-draft-times, https://rtsports.com/fantasy-baseball-leagues and https://rtsports.com/baseball/adp-aav and 9 others use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://rtsports.com/baseball/adp-aav and https://rtsports.com/dfs have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 56 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    15 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 360 words of copy

    The homepage carries about 360 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGNUP”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Signup” and “SIGNUP”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Reddit 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 rtsports.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

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on rtsports.com, including 14 speed issues and 5 SEO issues. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25