Tools & Wizards About Us
thefootballhistorydude.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

thefootballhistorydude.com

The Football History Dude podcast - Sports History Network

Page Load Speed

4.6 sec in total

First Response

81 ms

Resources Loaded

4.3 sec

Page Rendered

183 ms

thefootballhistorydude.com screenshot

About Website

Welcome to thefootballhistorydude.com homepage info - get ready to check The Football History Dude best content right away, or after learning these important things about thefootballhistorydude.com

The Football History Dude podcast takes the listener back in time to the yesteryear of the gridiron. This podcast is part of The Sports History Network.

Visit thefootballhistorydude.com

Key Findings

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

Performance Metrics

thefootballhistorydude.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value2,620 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.422

23/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

thefootballhistorydude.com

81 ms

3090 ms

js

65 ms

shortcode-min.css

19 ms

secondline-psb-styles.css

36 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Thefootballhistorydude.com, 69% (54 requests) were made to Sportshistorynetwork.com and 6% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Sportshistorynetwork.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.0 kB (12%)

Content Size

1.0 MB

After Optimization

892.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Thefootballhistorydude.com main page is 1.0 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. Javascripts take 755.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 96.0 kB

  • Original 124.0 kB
  • After minification 124.0 kB
  • After compression 28.0 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 96.0 kB or 77% of the original size.

JavaScript Optimization

-3%

Potential reduce by 24.8 kB

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

CSS Optimization

-0%

Potential reduce by 227 B

  • Original 134.2 kB
  • After minification 134.2 kB
  • After compression 134.0 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. Thefootballhistorydude.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (88%)

Requests Now

73

After Optimization

9

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

thefootballhistorydude.com

thefootballhistorydude.com

81 ms

3090 ms

js

js

65 ms

shortcode-min.css

shortcode-min.css

19 ms

secondline-psb-styles.css

secondline-psb-styles.css

36 ms

all.min.css

all.min.css

44 ms

font-icons.min.css

font-icons.min.css

36 ms

frontend.min.css

frontend.min.css

37 ms

general.min.css

general.min.css

36 ms

eael-38.css

eael-38.css

108 ms

elementor-icons.min.css

elementor-icons.min.css

104 ms

swiper.min.css

swiper.min.css

57 ms

post-28.css

post-28.css

106 ms

frontend.min.css

frontend.min.css

90 ms

post-38.css

post-38.css

166 ms

sticky.min.css

sticky.min.css

106 ms

css

css

170 ms

fontawesome.min.css

fontawesome.min.css

115 ms

solid.min.css

solid.min.css

113 ms

jquery.min.js

jquery.min.js

114 ms

frontend-gtag.min.js

frontend-gtag.min.js

119 ms

jquery-migrate.min.js

jquery-migrate.min.js

118 ms

adsbygoogle.js

adsbygoogle.js

321 ms

adsbygoogle.js

adsbygoogle.js

393 ms

email-decode.min.js

email-decode.min.js

113 ms

loader.js

loader.js

499 ms

stub.js

stub.js

102 ms

iubenda_cs.js

iubenda_cs.js

103 ms

all.min.css

all.min.css

118 ms

v4-shims.min.css

v4-shims.min.css

118 ms

wpforms-full.min.css

wpforms-full.min.css

117 ms

sticky.min.js

sticky.min.js

118 ms

lazysizes.min.js

lazysizes.min.js

119 ms

player-api-min.js

player-api-min.js

161 ms

modal.min.js

modal.min.js

163 ms

menu.min.js

menu.min.js

161 ms

general.min.js

general.min.js

163 ms

eael-38.js

eael-38.js

163 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

236 ms

webpack.runtime.min.js

webpack.runtime.min.js

163 ms

frontend-modules.min.js

frontend-modules.min.js

237 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

236 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

236 ms

wp-polyfill.min.js

wp-polyfill.min.js

237 ms

api.js

api.js

112 ms

hooks.min.js

hooks.min.js

235 ms

i18n.min.js

i18n.min.js

229 ms

frontend.min.js

frontend.min.js

212 ms

waypoints.min.js

waypoints.min.js

210 ms

core.min.js

core.min.js

205 ms

frontend.min.js

frontend.min.js

203 ms

elements-handlers.min.js

elements-handlers.min.js

203 ms

underscore.min.js

underscore.min.js

191 ms

wp-util.min.js

wp-util.min.js

145 ms

frontend.min.js

frontend.min.js

144 ms

jquery.validate.min.js

jquery.validate.min.js

145 ms

mailcheck.min.js

mailcheck.min.js

138 ms

punycode.min.js

punycode.min.js

137 ms

utils.min.js

utils.min.js

137 ms

wpforms.min.js

wpforms.min.js

136 ms

recaptcha__en.js

recaptcha__en.js

109 ms

generatepress.woff

generatepress.woff

105 ms

fa-solid-900.woff

fa-solid-900.woff

92 ms

fa-regular-400.woff

fa-regular-400.woff

92 ms

show_ads_impl.js

show_ads_impl.js

330 ms

zrt_lookup.html

zrt_lookup.html

48 ms

iubenda.js

iubenda.js

18 ms

ads

ads

201 ms

sodar

sodar

92 ms

ads

ads

373 ms

iubenda_i_badge.js

iubenda_i_badge.js

13 ms

iubenda_badge.css

iubenda_badge.css

13 ms

ads

ads

208 ms

sodar2.js

sodar2.js

18 ms

runner.html

runner.html

10 ms

aframe

aframe

21 ms

O8T1Km08OhS5_Tz58jKeajrFynp-IyfJlJwKv1268Sc.js

O8T1Km08OhS5_Tz58jKeajrFynp-IyfJlJwKv1268Sc.js

6 ms

ca-pub-4493598206275044

ca-pub-4493598206275044

66 ms

Accessibility Review

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

thefootballhistorydude.com best practices score

92

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

Page has valid source maps

SEO Factors

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

thefootballhistorydude.com

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