1.6 sec in total
636 ms
818 ms
97 ms
Visit fathercare.org now to see the best up-to-date Father Care content and also check out these interesting facts you probably never knew about fathercare.org
Visit fathercare.orgWe analyzed Fathercare.org page load time and found that the first response time was 636 ms and then it took 915 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
fathercare.org performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value7.9 s
3/100
25%
Value7.9 s
23/100
10%
Value700 ms
42/100
30%
Value0.247
50/100
15%
Value5.9 s
66/100
10%
636 ms
12 ms
87 ms
60 ms
11 ms
Our browser made a total of 22 requests to load all elements on the main page. We found that 9% of them (2 requests) were addressed to the original Fathercare.org, 82% (18 requests) were made to Ak2.imgaft.com and 9% (2 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (636 ms) belongs to the original domain Fathercare.org.
Page size can be reduced by 119.2 kB (64%)
185.8 kB
66.7 kB
In fact, the total size of Fathercare.org main page is 185.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 152.4 kB which makes up the majority of the site volume.
Potential reduce by 19.7 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 19.7 kB or 80% of the original size.
Potential reduce by 43 B
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. Father Care images are well optimized though.
Potential reduce by 99.4 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 99.4 kB or 65% of the original size.
We found no issues to fix!
21
21
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Father Care. According to our analytics all requests are already optimized.
fathercare.org
636 ms
txt_comingsoon_plparked.gif
12 ms
jquery-1.5.1.min.js
87 ms
pl-20150601.min.js
60 ms
jquery-1.3.1.min.js
11 ms
PL_btn_go2.png
9 ms
PL_bluebanner.gif
9 ms
cnr_tl_grey_plparked.gif
9 ms
cnr_tr_grey_plparked.gif
10 ms
txt_start_plparked.gif
12 ms
but_search_plparked.gif
11 ms
but_domaintranschkout.gif
10 ms
img_dbp86.gif
11 ms
txt_dbp86.gif
11 ms
img_wst86.jpg
12 ms
txt_eem86_hdr.gif
13 ms
txt_eem86_bullets.gif
14 ms
txt_eem86.gif
13 ms
txt_ssl86_hdr.gif
14 ms
txt_ssl86_bullets.gif
15 ms
img_wedge_plparked_grey.gif
27 ms
img.aspx
58 ms
fathercare.org 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.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
fathercare.org 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
fathercare.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fathercare.org 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 Fathercare.org 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.
fathercare.org
Open Graph description is not detected on the main page of Father Care. 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: