Tools & Wizards About Us
fathersafter50.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fathersafter50.com

Fathers After 50 | Happy, Healthy, Wealthy and Great Relationships

Page Load Speed

2.9 sec in total

First Response

108 ms

Resources Loaded

2.4 sec

Page Rendered

412 ms

fathersafter50.com screenshot

About Website

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

Fathers After 50 is meant to encourage individuals with stories of men and women who have had children after age 50.

Visit fathersafter50.com

Key Findings

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

Performance Metrics

fathersafter50.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.26

47/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

fathersafter50.com

108 ms

fathersafter50.com

873 ms

css

44 ms

js

81 ms

validationEngine.jquery.css

57 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 88% of them (98 requests) were addressed to the original Fathersafter50.com, 10% (11 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (873 ms) belongs to the original domain Fathersafter50.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 263.2 kB (6%)

Content Size

4.5 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fathersafter50.com main page is 4.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. Only a small number of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 64.5 kB

  • Original 81.3 kB
  • After minification 79.2 kB
  • After compression 16.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 64.5 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 11.2 kB

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

JavaScript Optimization

-16%

Potential reduce by 112.1 kB

  • Original 712.3 kB
  • After minification 711.9 kB
  • After compression 600.2 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 112.1 kB or 16% of the original size.

CSS Optimization

-26%

Potential reduce by 75.4 kB

  • Original 286.8 kB
  • After minification 286.4 kB
  • After compression 211.4 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. Fathersafter50.com needs all CSS files to be minified and compressed as it can save up to 75.4 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 90 (93%)

Requests Now

97

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fathersafter50.com

fathersafter50.com

108 ms

fathersafter50.com

fathersafter50.com

873 ms

css

css

44 ms

js

js

81 ms

validationEngine.jquery.css

validationEngine.jquery.css

57 ms

layerslider.css

layerslider.css

109 ms

style.min.css

style.min.css

129 ms

styles.css

styles.css

135 ms

rs6.css

rs6.css

157 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

155 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

165 ms

widget-base.min.css

widget-base.min.css

176 ms

style.css

style.css

196 ms

font-awesome.min.css

font-awesome.min.css

198 ms

style.min.css

style.min.css

202 ms

style.css

style.css

224 ms

dripicons.css

dripicons.css

231 ms

stylesheet.min.css

stylesheet.min.css

316 ms

print.css

print.css

242 ms

style_dynamic.css

style_dynamic.css

243 ms

responsive.min.css

responsive.min.css

253 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

261 ms

js_composer.min.css

js_composer.min.css

342 ms

custom_css.css

custom_css.css

283 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

281 ms

jquery.min.js

jquery.min.js

341 ms

jquery-migrate.min.js

jquery-migrate.min.js

298 ms

layerslider.utils.js

layerslider.utils.js

379 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

406 ms

layerslider.transitions.js

layerslider.transitions.js

375 ms

frontend-gtag.min.js

frontend-gtag.min.js

376 ms

css

css

38 ms

hooks.min.js

hooks.min.js

376 ms

i18n.min.js

i18n.min.js

375 ms

index.js

index.js

403 ms

index.js

index.js

463 ms

revolution.tools.min.js

revolution.tools.min.js

465 ms

rs6.min.js

rs6.min.js

467 ms

qode-like.min.js

qode-like.min.js

464 ms

core.min.js

core.min.js

463 ms

accordion.min.js

accordion.min.js

464 ms

menu.min.js

menu.min.js

419 ms

dom-ready.min.js

dom-ready.min.js

367 ms

a11y.min.js

a11y.min.js

343 ms

autocomplete.min.js

autocomplete.min.js

384 ms

controlgroup.min.js

controlgroup.min.js

364 ms

checkboxradio.min.js

checkboxradio.min.js

361 ms

button.min.js

button.min.js

355 ms

datepicker.min.js

datepicker.min.js

355 ms

mouse.min.js

mouse.min.js

325 ms

resizable.min.js

resizable.min.js

331 ms

draggable.min.js

draggable.min.js

328 ms

dialog.min.js

dialog.min.js

351 ms

droppable.min.js

droppable.min.js

345 ms

progressbar.min.js

progressbar.min.js

334 ms

selectable.min.js

selectable.min.js

344 ms

sortable.min.js

sortable.min.js

332 ms

slider.min.js

slider.min.js

328 ms

spinner.min.js

spinner.min.js

340 ms

tooltip.min.js

tooltip.min.js

342 ms

tabs.min.js

tabs.min.js

321 ms

effect.min.js

effect.min.js

283 ms

effect-blind.min.js

effect-blind.min.js

248 ms

effect-bounce.min.js

effect-bounce.min.js

258 ms

effect-clip.min.js

effect-clip.min.js

271 ms

effect-drop.min.js

effect-drop.min.js

271 ms

effect-explode.min.js

effect-explode.min.js

279 ms

effect-fade.min.js

effect-fade.min.js

258 ms

effect-fold.min.js

effect-fold.min.js

252 ms

effect-highlight.min.js

effect-highlight.min.js

233 ms

effect-pulsate.min.js

effect-pulsate.min.js

220 ms

effect-size.min.js

effect-size.min.js

220 ms

effect-scale.min.js

effect-scale.min.js

232 ms

effect-shake.min.js

effect-shake.min.js

224 ms

effect-slide.min.js

effect-slide.min.js

233 ms

effect-transfer.min.js

effect-transfer.min.js

229 ms

plugins.js

plugins.js

297 ms

jquery.carouFredSel-6.2.1.min.js

jquery.carouFredSel-6.2.1.min.js

264 ms

lemmon-slider.min.js

lemmon-slider.min.js

260 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

49 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

78 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

92 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

109 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

112 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

110 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

111 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

110 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

108 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

260 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

228 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

230 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

386 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

392 ms

jquery.stretch.js

jquery.stretch.js

383 ms

imagesloaded.js

imagesloaded.js

383 ms

rangeslider.min.js

rangeslider.min.js

382 ms

TweenLite.min.js

TweenLite.min.js

382 ms

smoothPageScroll.min.js

smoothPageScroll.min.js

338 ms

default_dynamic.js

default_dynamic.js

336 ms

default.min.js

default.min.js

329 ms

custom_js.js

custom_js.js

325 ms

comment-reply.min.js

comment-reply.min.js

325 ms

js_composer_front.min.js

js_composer_front.min.js

324 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

293 ms

Final-black.png

Final-black.png

292 ms

8.jpeg

8.jpeg

332 ms

what-is-a-father-s-role_59444ca115aef96a.jpg

what-is-a-father-s-role_59444ca115aef96a.jpg

331 ms

1.jpeg

1.jpeg

433 ms

68LBZRAYIU.jpg

68LBZRAYIU.jpg

653 ms

loader.gif

loader.gif

44 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

10 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

10 ms

Accessibility Review

fathersafter50.com accessibility score

66

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fathersafter50.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fathersafter50.com SEO score

93

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

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

fathersafter50.com

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