Tools & Wizards About Us
fantistics.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fantistics.com

Fantasy Football 2025 | Draft Software, Rankings, Cheat Sheets

Page Load Speed

1.6 sec in total

First Response

43 ms

Resources Loaded

1.1 sec

Page Rendered

375 ms

fantistics.com screenshot

About Website

Visit fantistics.com now to see the best up-to-date Fantistics content for United States and also check out these interesting facts you probably never knew about fantistics.com

Fantasy

Visit fantistics.com

Key Findings

We analyzed Fantistics.com page load time and found that the first response time was 43 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

fantistics.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value80.6 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

fantistics.com

43 ms

fantistics.com

96 ms

wp-emoji-release.min.js

167 ms

dashicons.min.css

24 ms

jquery-ui-dialog.min.css

35 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 79% of them (84 requests) were addressed to the original Fantistics.com, 13% (14 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Insiderbaseball.com. The less responsive or slowest element that took the longest time to load (746 ms) belongs to the original domain Fantistics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.9 MB (56%)

Content Size

5.2 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fantistics.com main page is 5.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 50.5 kB

  • Original 63.8 kB
  • After minification 61.5 kB
  • After compression 13.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.5 kB or 79% of the original size.

Image Optimization

-38%

Potential reduce by 1.2 MB

  • Original 3.1 MB
  • After minification 1.9 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Fantistics needs image optimization as it can save up to 1.2 MB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 342.1 kB

  • Original 496.9 kB
  • After minification 461.1 kB
  • After compression 154.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 342.1 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 1.4 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 177.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Fantistics.com needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (74%)

Requests Now

84

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fantistics. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fantistics.com

fantistics.com

43 ms

fantistics.com

fantistics.com

96 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

167 ms

dashicons.min.css

dashicons.min.css

24 ms

jquery-ui-dialog.min.css

jquery-ui-dialog.min.css

35 ms

font-lineicons.css

font-lineicons.css

50 ms

styles.css

styles.css

40 ms

prettyPhoto.min.css

prettyPhoto.min.css

51 ms

js_composer.min.css

js_composer.min.css

142 ms

bootstrap.min.css

bootstrap.min.css

57 ms

animate.css

animate.css

78 ms

prettyPhoto.css

prettyPhoto.css

52 ms

revolution-styles.css

revolution-styles.css

62 ms

style.css

style.css

62 ms

theme-options.css

theme-options.css

64 ms

css

css

20 ms

css

css

37 ms

font-awesome.min.css

font-awesome.min.css

68 ms

font-lineicons.css

font-lineicons.css

82 ms

vivaco-animations.css

vivaco-animations.css

111 ms

jquery.js

jquery.js

106 ms

jquery-migrate.min.js

jquery-migrate.min.js

79 ms

edd-ajax.min.js

edd-ajax.min.js

88 ms

vivaco-animations.js

vivaco-animations.js

90 ms

platform.js

platform.js

62 ms

font-awesome.min.css

font-awesome.min.css

92 ms

js_composer_tta.min.css

js_composer_tta.min.css

156 ms

core.min.js

core.min.js

100 ms

widget.min.js

widget.min.js

103 ms

mouse.min.js

mouse.min.js

115 ms

resizable.min.js

resizable.min.js

116 ms

draggable.min.js

draggable.min.js

116 ms

button.min.js

button.min.js

120 ms

position.min.js

position.min.js

122 ms

dialog.min.js

dialog.min.js

125 ms

wpdialog.min.js

wpdialog.min.js

127 ms

jquery.form.min.js

jquery.form.min.js

132 ms

scripts.js

scripts.js

133 ms

comment-reply.min.js

comment-reply.min.js

153 ms

EasePack.min.js

EasePack.min.js

153 ms

bootstrap.min.js

bootstrap.min.js

154 ms

jquery.nav.js

jquery.nav.js

138 ms

social-share.js

social-share.js

128 ms

custom-mailing-list.js

custom-mailing-list.js

122 ms

jquery.parallax.js

jquery.parallax.js

123 ms

custom-parallax.js

custom-parallax.js

114 ms

jquery.isotope.min.js

jquery.isotope.min.js

113 ms

custom-isotope-portfolio.js

custom-isotope-portfolio.js

113 ms

modal-box.js

modal-box.js

104 ms

style.css

style.css

137 ms

headhesive.min.js

headhesive.min.js

104 ms

platform.js

platform.js

53 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

106 ms

custom.js

custom.js

103 ms

wp-embed.min.js

wp-embed.min.js

94 ms

js_composer_front.min.js

js_composer_front.min.js

96 ms

waypoints.min.js

waypoints.min.js

94 ms

vc-accordion.min.js

vc-accordion.min.js

92 ms

vc-tta-autoplay.min.js

vc-tta-autoplay.min.js

93 ms

vc-tabs.min.js

vc-tabs.min.js

91 ms

tabs.min.js

tabs.min.js

85 ms

jquery-ui-tabs-rotate.min.js

jquery-ui-tabs-rotate.min.js

83 ms

custom-contact-form7.js

custom-contact-form7.js

87 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

78 ms

custom-content-slider.js

custom-content-slider.js

79 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

183 ms

ProgressCircle.js

ProgressCircle.js

183 ms

custom-pie.js

custom-pie.js

179 ms

custom-counter.js

custom-counter.js

178 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

312 ms

sportsdataio_light_ss_300.png

sportsdataio_light_ss_300.png

113 ms

insiderbaseball-logo.png

insiderbaseball-logo.png

56 ms

insiderbaseball-logo-retina.png

insiderbaseball-logo-retina.png

56 ms

insiderbaseball-logo-sticky.png

insiderbaseball-logo-sticky.png

57 ms

insiderbaseball-logo-retina.png

insiderbaseball-logo-retina.png

57 ms

background-home.jpg

background-home.jpg

312 ms

insiderbaseball-fantistics-projections.png

insiderbaseball-fantistics-projections.png

746 ms

fantasy-sports-radio.png

fantasy-sports-radio.png

57 ms

bullet.png

bullet.png

58 ms

fantasy-baseball-draft-advisory.png

fantasy-baseball-draft-advisory.png

110 ms

player-projection-accuracy-matters-2018.png

player-projection-accuracy-matters-2018.png

338 ms

season-management-tools2.jpg

season-management-tools2.jpg

226 ms

sabermetric-player-projections.png

sabermetric-player-projections.png

224 ms

custom-rankings-auction-values.png

custom-rankings-auction-values.png

225 ms

draft-day-management.png

draft-day-management.png

309 ms

background-photos.jpg

background-photos.jpg

225 ms

3-stars.png

3-stars.png

226 ms

tw.png

tw.png

226 ms

fb.png

fb.png

227 ms

fantasy-sports-radio-footer.png

fantasy-sports-radio-footer.png

309 ms

jizaRExUiTo99u79P0U.ttf

jizaRExUiTo99u79P0U.ttf

100 ms

jizfRExUiTo99u79B_mh4Ok.ttf

jizfRExUiTo99u79B_mh4Ok.ttf

99 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

66 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

66 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

66 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

65 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

98 ms

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

98 ms

S6u-w4BMUTPHjxsIPx-oPCc.ttf

S6u-w4BMUTPHjxsIPx-oPCc.ttf

160 ms

S6u8w4BMUTPHjxsAXC-v.ttf

S6u8w4BMUTPHjxsAXC-v.ttf

97 ms

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

98 ms

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

159 ms

line-icons.woff

line-icons.woff

250 ms

jizdRExUiTo99u79D0e8fOytKA.ttf

jizdRExUiTo99u79D0e8fOytKA.ttf

258 ms

jizYRExUiTo99u79D0eEwA.ttf

jizYRExUiTo99u79D0eEwA.ttf

274 ms

hln55FEspG0

hln55FEspG0

179 ms

Accessibility Review

fantistics.com accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fantistics.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fantistics.com SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fantistics.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fantistics.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

fantistics.com

Open Graph description is not detected on the main page of Fantistics. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: