Tools & Wizards About Us
fanstarpro.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

fanstarpro.com

Scout.com - College Sports, Football Recruiting, NFL, Fantasy Advice & More

Page Load Speed

1.4 sec in total

First Response

143 ms

Resources Loaded

518 ms

Page Rendered

785 ms

fanstarpro.com screenshot

About Website

Visit fanstarpro.com now to see the best up-to-date Fanstarpro content and also check out these interesting facts you probably never knew about fanstarpro.com

Breaking news and expert analysis on college sports, recruiting, fantasy football, NFL, outdoors, military, and more.

Visit fanstarpro.com

Key Findings

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

Performance Metrics

fanstarpro.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value29.5 s

0/100

10%

TBT (Total Blocking Time)

Value21,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value66.8 s

0/100

10%

Network Requests Diagram

fanstarpro.com

143 ms

247sports.com

37 ms

8677.css

101 ms

bundle.css

99 ms

homepageWrapper.css

102 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fanstarpro.com, 85% (63 requests) were made to S3media.247sports.com and 3% (2 requests) were made to 247sports.com. The less responsive or slowest element that took the longest time to load (311 ms) relates to the external source At.cbsi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 337.5 kB (19%)

Content Size

1.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fanstarpro.com main page is 1.8 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 888.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 257.3 kB

  • Original 320.4 kB
  • After minification 318.8 kB
  • After compression 63.2 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 257.3 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 898 B

  • Original 888.4 kB
  • After minification 887.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. Fanstarpro images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 79.3 kB

  • Original 550.4 kB
  • After minification 550.4 kB
  • After compression 471.1 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 79.3 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (54%)

Requests Now

72

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fanstarpro.com

fanstarpro.com

143 ms

247sports.com

247sports.com

37 ms

8677.css

8677.css

101 ms

bundle.css

bundle.css

99 ms

homepageWrapper.css

homepageWrapper.css

102 ms

homepage.css

homepage.css

102 ms

aws-sdk-2.176.0.min.js

aws-sdk-2.176.0.min.js

17 ms

jquery-3.6.4.min.js

jquery-3.6.4.min.js

248 ms

otSDKStub.js

otSDKStub.js

78 ms

bidbarrel-247sports.min.js

bidbarrel-247sports.min.js

311 ms

MIN-300300.js

MIN-300300.js

296 ms

utag.js

utag.js

87 ms

optanon-v1.1.0.js

optanon-v1.1.0.js

91 ms

a-016u.min.js

a-016u.min.js

92 ms

runtime~bundle.js

runtime~bundle.js

181 ms

lodash.bundle.js

lodash.bundle.js

241 ms

core-js.bundle.js

core-js.bundle.js

242 ms

date-fns.bundle.js

date-fns.bundle.js

237 ms

react-dom.cjs.bundle.js

react-dom.cjs.bundle.js

240 ms

react-router.bundle.js

react-router.bundle.js

235 ms

postcss.bundle.js

postcss.bundle.js

240 ms

@sentry.bundle.js

@sentry.bundle.js

277 ms

lib.bundle.js

lib.bundle.js

271 ms

winston.bundle.js

winston.bundle.js

258 ms

cheerio.bundle.js

cheerio.bundle.js

266 ms

sanitize-html.bundle.js

sanitize-html.bundle.js

267 ms

stream-http.bundle.js

stream-http.bundle.js

269 ms

stream-browserify.bundle.js

stream-browserify.bundle.js

270 ms

7943.js

7943.js

293 ms

5898.js

5898.js

272 ms

3444.js

3444.js

273 ms

9597.js

9597.js

270 ms

1776.js

1776.js

273 ms

8677.js

8677.js

277 ms

bundle.js

bundle.js

277 ms

homepageWrapper.js

homepageWrapper.js

275 ms

1941.js

1941.js

285 ms

9611.js

9611.js

277 ms

1876.js

1876.js

280 ms

9581.js

9581.js

277 ms

homepage.js

homepage.js

279 ms

late-kick-show-watch-live.jpg

late-kick-show-watch-live.jpg

108 ms

12542742.jpg

12542742.jpg

112 ms

12483619.JPG

12483619.JPG

111 ms

12343726.jpg

12343726.jpg

108 ms

11472904.jpg

11472904.jpg

114 ms

11805775.JPG

11805775.JPG

115 ms

12543048.jpeg

12543048.jpeg

116 ms

12312759.jpg

12312759.jpg

112 ms

12523987.JPG

12523987.JPG

60 ms

12525226.png

12525226.png

62 ms

12542472.png

12542472.png

63 ms

12532939.jpg

12532939.jpg

57 ms

12532916.jpg

12532916.jpg

60 ms

12542377.jpeg

12542377.jpeg

59 ms

1587620b-5536-4ad4-8186-7b11a4508dc1.json

1587620b-5536-4ad4-8186-7b11a4508dc1.json

75 ms

8456487.png

8456487.png

66 ms

12001313.jpeg

12001313.jpeg

66 ms

12541348.JPG

12541348.JPG

54 ms

12511730.jpg

12511730.jpg

57 ms

12542392.jpeg

12542392.jpeg

55 ms

12533261.JPEG

12533261.JPEG

55 ms

12536168.jpeg

12536168.jpeg

55 ms

12532507.jpg

12532507.jpg

55 ms

12528613.jpeg

12528613.jpeg

54 ms

12527136.jpeg

12527136.jpeg

55 ms

12341871.jpg

12341871.jpg

53 ms

12483080.png

12483080.png

59 ms

12541144.jpeg

12541144.jpeg

56 ms

10510794.png

10510794.png

54 ms

12539465.jpg

12539465.jpg

54 ms

12539881.png

12539881.png

55 ms

12537813.png

12537813.png

54 ms

shamanNotifier.js

shamanNotifier.js

29 ms

Accessibility Review

fanstarpro.com accessibility score

91

Accessibility Issues

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.

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

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

fanstarpro.com best practices score

75

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

fanstarpro.com SEO score

76

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

fanstarpro.com

Open Graph data is detected on the main page of Fanstarpro. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: