Tools & Wizards About Us
fighting-fathers.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fighting-fathers.com

Fighting Fathers Member site

Page Load Speed

8.6 sec in total

First Response

1.7 sec

Resources Loaded

6.8 sec

Page Rendered

131 ms

fighting-fathers.com screenshot

About Website

Welcome to fighting-fathers.com homepage info - get ready to check Fighting Fathers best content right away, or after learning these important things about fighting-fathers.com

Fighting for Things Worth Fighting For

Visit fighting-fathers.com

Key Findings

We analyzed Fighting-fathers.com page load time and found that the first response time was 1.7 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

fighting-fathers.com performance score

0

Network Requests Diagram

fighting-fathers.com

1709 ms

spcjs.php

1408 ms

js.php

3903 ms

spc.php

764 ms

fl.js

484 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 14% of them (4 requests) were addressed to the original Fighting-fathers.com, 69% (20 requests) were made to Igroops.com and 17% (5 requests) were made to Openx.fatherdave.org. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Fighting-fathers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.9 kB (8%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fighting-fathers.com main page is 1.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. Only 10% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 3.2 kB

  • Original 5.1 kB
  • After minification 4.9 kB
  • After compression 1.9 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 3.2 kB or 63% of the original size.

Image Optimization

-7%

Potential reduce by 85.6 kB

  • Original 1.2 MB
  • After minification 1.1 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. Fighting Fathers images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 6.1 kB

  • Original 8.6 kB
  • After minification 8.2 kB
  • After compression 2.6 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 6.1 kB or 70% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

28

After Optimization

28

  • AJAX
  • Images
  • JavaScript

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fighting Fathers. According to our analytics all requests are already optimized.

Network Requests Diagram

fighting-fathers.com

fighting-fathers.com

1709 ms

spcjs.php

spcjs.php

1408 ms

js.php

js.php

3903 ms

spc.php

spc.php

764 ms

fl.js

fl.js

484 ms

slideshow.html

slideshow.html

254 ms

splashPageHeader.jpg

splashPageHeader.jpg

1412 ms

29f7d9e71f35950f3acc3baa1c214a43.jpg

29f7d9e71f35950f3acc3baa1c214a43.jpg

928 ms

lg.php

lg.php

582 ms

01.T-shirt-1.jpg

01.T-shirt-1.jpg

203 ms

01.setting-up.jpg

01.setting-up.jpg

230 ms

04.anthony-me.jpg

04.anthony-me.jpg

211 ms

05.random-2.jpg

05.random-2.jpg

213 ms

07.sol-me-6.jpg

07.sol-me-6.jpg

211 ms

08.graham-soren-me.jpg

08.graham-soren-me.jpg

212 ms

03.anthony-andrew-mungo.jpg

03.anthony-andrew-mungo.jpg

285 ms

03.john-me-9.jpg

03.john-me-9.jpg

271 ms

09.end-2.jpg

09.end-2.jpg

294 ms

01.T-shirt-2.jpg

01.T-shirt-2.jpg

277 ms

09.end-speech.jpg

09.end-speech.jpg

299 ms

08.random-1.jpg

08.random-1.jpg

286 ms

09.corner.jpg

09.corner.jpg

329 ms

08.geoff-2.jpg

08.geoff-2.jpg

336 ms

06.kon-me-2.jpg

06.kon-me-2.jpg

342 ms

01.setup.jpg

01.setup.jpg

344 ms

01.Narelle-me.jpg

01.Narelle-me.jpg

384 ms

01.Nader-me-Jaime.jpg

01.Nader-me-Jaime.jpg

356 ms

01.Nader-John-me.jpg

01.Nader-John-me.jpg

415 ms

01.Nader-me.jpg

01.Nader-me.jpg

673 ms

SEO Factors

fighting-fathers.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fighting-fathers.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 Fighting-fathers.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

fighting-fathers.com

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