2.6 sec in total
134 ms
2.1 sec
393 ms
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.comWe analyzed Fathersafter50.com page load time and found that the first response time was 134 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fathersafter50.com performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value11.3 s
0/100
25%
Value10.1 s
9/100
10%
Value800 ms
36/100
30%
Value0.26
47/100
15%
Value19.7 s
2/100
10%
134 ms
544 ms
36 ms
64 ms
41 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 (729 ms) belongs to the original domain Fathersafter50.com.
Page size can be reduced by 268.4 kB (6%)
4.6 MB
4.3 MB
In fact, the total size of Fathersafter50.com main page is 4.6 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. 70% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 64.1 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.1 kB or 79% of the original size.
Potential reduce by 11.2 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. Fathers After 50 images are well optimized though.
Potential reduce by 119.3 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 119.3 kB or 16% of the original size.
Potential reduce by 73.8 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 73.8 kB or 27% of the original size.
Number of requests can be reduced by 90 (93%)
97
7
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 73 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
fathersafter50.com
134 ms
fathersafter50.com
544 ms
css
36 ms
js
64 ms
validationEngine.jquery.css
41 ms
layerslider.css
134 ms
style.min.css
166 ms
styles.css
142 ms
rs6.css
182 ms
style.css
187 ms
font-awesome.min.css
191 ms
style.min.css
176 ms
style.css
188 ms
dripicons.css
204 ms
stylesheet.min.css
313 ms
print.css
230 ms
style_dynamic.css
231 ms
responsive.min.css
249 ms
style_dynamic_responsive.css
235 ms
js_composer.min.css
296 ms
custom_css.css
273 ms
ScrollToPlugin.min.js
273 ms
jquery.min.js
349 ms
jquery-migrate.min.js
292 ms
layerslider.utils.js
367 ms
layerslider.kreaturamedia.jquery.js
389 ms
layerslider.transitions.js
360 ms
frontend-gtag.min.js
361 ms
css
42 ms
index.js
361 ms
index.js
383 ms
revolution.tools.min.js
440 ms
rs6.min.js
439 ms
qode-like.min.js
384 ms
core.min.js
438 ms
accordion.min.js
437 ms
menu.min.js
438 ms
wp-polyfill-inert.min.js
439 ms
regenerator-runtime.min.js
475 ms
wp-polyfill.min.js
486 ms
dom-ready.min.js
474 ms
hooks.min.js
450 ms
i18n.min.js
355 ms
a11y.min.js
348 ms
autocomplete.min.js
371 ms
controlgroup.min.js
363 ms
checkboxradio.min.js
358 ms
button.min.js
356 ms
datepicker.min.js
353 ms
mouse.min.js
349 ms
resizable.min.js
375 ms
draggable.min.js
358 ms
dialog.min.js
356 ms
droppable.min.js
346 ms
progressbar.min.js
336 ms
selectable.min.js
305 ms
sortable.min.js
352 ms
slider.min.js
324 ms
spinner.min.js
316 ms
tooltip.min.js
272 ms
tabs.min.js
277 ms
effect.min.js
272 ms
effect-blind.min.js
296 ms
effect-bounce.min.js
299 ms
effect-clip.min.js
283 ms
effect-drop.min.js
283 ms
effect-explode.min.js
290 ms
effect-fade.min.js
250 ms
effect-fold.min.js
261 ms
effect-highlight.min.js
261 ms
effect-pulsate.min.js
269 ms
effect-size.min.js
270 ms
effect-scale.min.js
280 ms
pxiByp8kv8JHgFVrLDz8Z1JlEw.woff
41 ms
pxiByp8kv8JHgFVrLFj_Z1JlEw.woff
75 ms
pxiGyp8kv8JHgFVrLPTufntG.woff
85 ms
pxiEyp8kv8JHgFVrJJnedA.woff
104 ms
pxiByp8kv8JHgFVrLGT9Z1JlEw.woff
106 ms
pxiByp8kv8JHgFVrLEj6Z1JlEw.woff
105 ms
pxiByp8kv8JHgFVrLCz7Z1JlEw.woff
105 ms
pxiByp8kv8JHgFVrLDD4Z1JlEw.woff
106 ms
pxiByp8kv8JHgFVrLBT5Z1JlEw.woff
104 ms
effect-shake.min.js
278 ms
effect-slide.min.js
266 ms
effect-transfer.min.js
259 ms
plugins.js
342 ms
jquery.carouFredSel-6.2.1.min.js
274 ms
lemmon-slider.min.js
279 ms
jquery.fullPage.min.js
251 ms
jquery.mousewheel.min.js
251 ms
jquery.touchSwipe.min.js
246 ms
isotope.pkgd.min.js
271 ms
packery-mode.pkgd.min.js
278 ms
jquery.stretch.js
277 ms
imagesloaded.js
278 ms
rangeslider.min.js
344 ms
TweenLite.min.js
344 ms
smoothPageScroll.min.js
341 ms
default_dynamic.js
338 ms
default.min.js
338 ms
custom_js.js
335 ms
comment-reply.min.js
309 ms
js_composer_front.min.js
340 ms
fontawesome-webfont.woff
435 ms
Final-black.png
353 ms
8.jpeg
429 ms
what-is-a-father-s-role_59444ca115aef96a.jpg
304 ms
1.jpeg
491 ms
68LBZRAYIU.jpg
729 ms
loader.gif
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
8 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
7 ms
fathersafter50.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fathersafter50.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fathersafter50.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
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: