Tools & Wizards About Us
fantasyranker.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

fantasyranker.com

Free Fantasy Draft Rankings | Cheat Sheets | Auction Values | ADPs

Page Load Speed

22.6 sec in total

First Response

1.2 sec

Resources Loaded

21.2 sec

Page Rendered

149 ms

fantasyranker.com screenshot

About Website

Click here to check amazing Fantasy Ranker content. Otherwise, check out these important facts you probably never knew about fantasyranker.com

The most complete listing of free fantasy content. Customize your draft prep by creating your own player rankings and draft cheat sheets for your baseball, football, basketball or hockey league.

Visit fantasyranker.com

Key Findings

We analyzed Fantasyranker.com page load time and found that the first response time was 1.2 sec and then it took 21.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

fantasyranker.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value730 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

fantasyranker.com

1169 ms

analytics.js

248 ms

banner-styles.css

256 ms

style_BLS.css

393 ms

addthis_widget.js

14 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 62% of them (32 requests) were addressed to the original Fantasyranker.com, 12% (6 requests) were made to Securepubads.g.doubleclick.net and 6% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Fsru.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.1 kB (16%)

Content Size

829.9 kB

After Optimization

698.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fantasyranker.com main page is 829.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 485.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 30.5 kB

  • Original 38.0 kB
  • After minification 31.9 kB
  • After compression 7.6 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. This page needs HTML code to be minified as it can gain 6.1 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 30.5 kB or 80% of the original size.

Image Optimization

-14%

Potential reduce by 36.8 kB

  • Original 265.4 kB
  • After minification 228.6 kB

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, Fantasy Ranker needs image optimization as it can save up to 36.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 25.7 kB

  • Original 485.0 kB
  • After minification 485.0 kB
  • After compression 459.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-92%

Potential reduce by 38.2 kB

  • Original 41.4 kB
  • After minification 30.2 kB
  • After compression 3.2 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. Fantasyranker.com needs all CSS files to be minified and compressed as it can save up to 38.2 kB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (13%)

Requests Now

46

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fantasyranker.com

fantasyranker.com

1169 ms

analytics.js

analytics.js

248 ms

banner-styles.css

banner-styles.css

256 ms

style_BLS.css

style_BLS.css

393 ms

addthis_widget.js

addthis_widget.js

14 ms

HomeMenuTabs.txt

HomeMenuTabs.txt

281 ms

Side-SportLink.txt

Side-SportLink.txt

270 ms

Side-Version.txt

Side-Version.txt

273 ms

Side-DateSlash.txt

Side-DateSlash.txt

301 ms

Football-WeekNumber.txt

Football-WeekNumber.txt

257 ms

Baseball-DateYear.txt

Baseball-DateYear.txt

356 ms

Football-DateYear.txt

Football-DateYear.txt

355 ms

Basketball-DateYear.txt

Basketball-DateYear.txt

358 ms

Hockey-DateYear.txt

Hockey-DateYear.txt

394 ms

show_ads.js

show_ads.js

75 ms

gpt.js

gpt.js

94 ms

pubads_impl.js

pubads_impl.js

25 ms

ppub_config

ppub_config

112 ms

headernew.jpg

headernew.jpg

460 ms

lg-share-en.gif

lg-share-en.gif

30 ms

1_b.gif

1_b.gif

19583 ms

FDRMainLogoHeader.jpg

FDRMainLogoHeader.jpg

447 ms

contact_new.jpg

contact_new.jpg

171 ms

0c89d805-f7f2-48ae-bed3-ce737b9e31ebfft125new.jpg

0c89d805-f7f2-48ae-bed3-ce737b9e31ebfft125new.jpg

221 ms

menuover.gif

menuover.gif

201 ms

menu.gif

menu.gif

199 ms

banner002big.jpg

banner002big.jpg

271 ms

contentbg.jpg

contentbg.jpg

296 ms

exportsbgbottom_new.jpg

exportsbgbottom_new.jpg

295 ms

loginboxlogosmall_new.jpg

loginboxlogosmall_new.jpg

295 ms

leftlinkbg_new.jpg

leftlinkbg_new.jpg

373 ms

ads

ads

52 ms

container.html

container.html

60 ms

exportsbg_newbigger.jpg

exportsbg_newbigger.jpg

336 ms

exportimg.jpg

exportimg.jpg

337 ms

exportimg002.jpg

exportimg002.jpg

335 ms

exportimg003.jpg

exportimg003.jpg

424 ms

exportimg004.jpg

exportimg004.jpg

455 ms

contentbg_new_ad.jpg

contentbg_new_ad.jpg

450 ms

right.jpg

right.jpg

452 ms

ads

ads

71 ms

adsbygoogle.js

adsbygoogle.js

120 ms

ads

ads

62 ms

aci.js

aci.js

551 ms

ads

ads

48 ms

footer.jpg

footer.jpg

371 ms

ga.js

ga.js

7 ms

__utm.gif

__utm.gif

13 ms

show_ads_impl.js

show_ads_impl.js

372 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

21 ms

ads

ads

284 ms

ads

ads

294 ms

Accessibility Review

fantasyranker.com accessibility score

63

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

fantasyranker.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fantasyranker.com SEO score

58

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fantasyranker.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fantasyranker.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

fantasyranker.com

Open Graph description is not detected on the main page of Fantasy Ranker. 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: