Tools & Wizards About Us
theprodigyfanboy.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

theprodigyfanboy.com

The Prodigy Fanboy - Liam Howlett Keith Flint Maxim

Page Load Speed

3.8 sec in total

First Response

526 ms

Resources Loaded

1.7 sec

Page Rendered

1.7 sec

theprodigyfanboy.com screenshot

About Website

Visit theprodigyfanboy.com now to see the best up-to-date The Prodigy Fanboy content for Russia and also check out these interesting facts you probably never knew about theprodigyfanboy.com

GL0WKiD pres. RIP KEITH FLINT Radio Tribute (Kniteforce Radio - 16th March 2019) MESSAGE FROM DANNY FANBOY (05/04/17): Danny Fanboy here. Taking a break, might not come back actually... If there'...

Visit theprodigyfanboy.com

Key Findings

We analyzed Theprodigyfanboy.com page load time and found that the first response time was 526 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

theprodigyfanboy.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.563

12/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

theprodigyfanboy.com

526 ms

validationEngine.jquery.css

120 ms

sbi-styles.min.css

138 ms

style.min.css

199 ms

style.css

139 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 80% of them (51 requests) were addressed to the original Theprodigyfanboy.com, 8% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (615 ms) belongs to the original domain Theprodigyfanboy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.7 MB (30%)

Content Size

12.5 MB

After Optimization

8.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Theprodigyfanboy.com main page is 12.5 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 12.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 47.5 kB

  • Original 62.3 kB
  • After minification 61.4 kB
  • After compression 14.8 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 47.5 kB or 76% of the original size.

Image Optimization

-29%

Potential reduce by 3.5 MB

  • Original 12.1 MB
  • After minification 8.6 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, The Prodigy Fanboy needs image optimization as it can save up to 3.5 MB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 24.7 kB

  • Original 153.6 kB
  • After minification 153.6 kB
  • After compression 128.9 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 24.7 kB or 16% of the original size.

CSS Optimization

-62%

Potential reduce by 110.0 kB

  • Original 177.9 kB
  • After minification 177.7 kB
  • After compression 67.9 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. Theprodigyfanboy.com needs all CSS files to be minified and compressed as it can save up to 110.0 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (59%)

Requests Now

56

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

theprodigyfanboy.com

theprodigyfanboy.com

526 ms

validationEngine.jquery.css

validationEngine.jquery.css

120 ms

sbi-styles.min.css

sbi-styles.min.css

138 ms

style.min.css

style.min.css

199 ms

style.css

style.css

139 ms

social_widget.css

social_widget.css

131 ms

polls-css.css

polls-css.css

135 ms

style.css

style.css

181 ms

jquery.fancybox.css

jquery.fancybox.css

195 ms

css

css

21 ms

flexslider.css

flexslider.css

200 ms

font-awesome.min.css

font-awesome.min.css

15 ms

jquery.min.js

jquery.min.js

269 ms

jquery-migrate.min.js

jquery-migrate.min.js

201 ms

style.css

style.css

194 ms

dashicons.min.css

dashicons.min.css

267 ms

thickbox.css

thickbox.css

207 ms

polls-js.js

polls-js.js

210 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

214 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

261 ms

jquery.superfish-1.4.8.min.js

jquery.superfish-1.4.8.min.js

273 ms

core.min.js

core.min.js

275 ms

tabs.min.js

tabs.min.js

282 ms

jquery.fitvids.js

jquery.fitvids.js

280 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

332 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

334 ms

periodic.js

periodic.js

338 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

346 ms

new-tab.js

new-tab.js

357 ms

front_end_js.js

front_end_js.js

356 ms

thickbox.js

thickbox.js

397 ms

style.css

style.css

288 ms

132 ms

mainbg.jpg

mainbg.jpg

113 ms

mainbg.jpg

mainbg.jpg

148 ms

Banner-1.png

Banner-1.png

375 ms

Logo-7.png

Logo-7.png

317 ms

IMG_1861.jpg

IMG_1861.jpg

125 ms

IMG_1856-2-150x150.jpg

IMG_1856-2-150x150.jpg

110 ms

52498864_643294436140967_5167187429744753002_n-2-1024x767.jpg

52498864_643294436140967_5167187429744753002_n-2-1024x767.jpg

252 ms

Danny-Liam.jpg

Danny-Liam.jpg

399 ms

Banner-001.jpg

Banner-001.jpg

305 ms

Banner-002.jpg

Banner-002.jpg

270 ms

Banner-003-1.jpg

Banner-003-1.jpg

440 ms

Banner-005.png

Banner-005.png

507 ms

Banner-006.jpg

Banner-006.jpg

426 ms

Banner-007.png

Banner-007.png

498 ms

Banner-008.jpg

Banner-008.jpg

443 ms

Banner-009.png

Banner-009.png

582 ms

Banner-010.jpg

Banner-010.jpg

494 ms

NewEraBanner-5.png

NewEraBanner-5.png

615 ms

Banner-011.png

Banner-011.png

564 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

24 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

24 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

25 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

26 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

25 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

26 ms

loadingAnimation.gif

loadingAnimation.gif

450 ms

player-widget.mixcloud.com

player-widget.mixcloud.com

293 ms

css

css

41 ms

polyfills-legacy-DrPoZund.js

polyfills-legacy-DrPoZund.js

23 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

67 ms

print.css

print.css

68 ms

Accessibility Review

theprodigyfanboy.com accessibility score

79

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

theprodigyfanboy.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

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

theprodigyfanboy.com SEO score

86

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

High

Image elements do not have [alt] attributes

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

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

theprodigyfanboy.com

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