6.4 sec in total
167 ms
6 sec
200 ms
Visit familyfables.org now to see the best up-to-date Family Fables content and also check out these interesting facts you probably never knew about familyfables.org
Family Fables publishes joyful, whimsical children’s books that bring families together — funny read-aloud stories, bedtime books, and interactive adventures for kids ages 2–10.
Visit familyfables.orgWe analyzed Familyfables.org page load time and found that the first response time was 167 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
familyfables.org performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value15.0 s
0/100
25%
Value14.3 s
1/100
10%
Value340 ms
74/100
30%
Value0.116
85/100
15%
Value12.9 s
13/100
10%
167 ms
1505 ms
120 ms
189 ms
185 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 74% of them (59 requests) were addressed to the original Familyfables.org, 20% (16 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Familyfables.org.
Page size can be reduced by 450.6 kB (6%)
7.0 MB
6.5 MB
In fact, the total size of Familyfables.org main page is 7.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. 70% of websites need less resources to load. Images take 6.4 MB which makes up the majority of the site volume.
Potential reduce by 107.2 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 107.2 kB or 84% of the original size.
Potential reduce by 217.0 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. Family Fables images are well optimized though.
Potential reduce by 53.0 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 53.0 kB or 22% of the original size.
Potential reduce by 73.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. Familyfables.org needs all CSS files to be minified and compressed as it can save up to 73.4 kB or 35% of the original size.
Number of requests can be reduced by 41 (67%)
61
20
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Family Fables. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
familyfables.org
167 ms
www.familyfables.org
1505 ms
prettyPhoto.css
120 ms
wp-video-lightbox.css
189 ms
Rich-Web-Slider-Widget.css
185 ms
richwebicons.css
193 ms
woocommerce-layout.css
178 ms
woocommerce.css
186 ms
front.min.css
180 ms
css
35 ms
css
56 ms
style.css
254 ms
font-awesome.min.css
38 ms
style-static.min.css
432 ms
jquery.min.js
309 ms
jquery-migrate.min.js
250 ms
jquery.prettyPhoto.min.js
252 ms
video-lightbox.js
255 ms
core.min.js
315 ms
jquery.easing.1.2.js
317 ms
jquery.anythingslider.min.js
316 ms
jquery.colorbox-min.js
388 ms
jquery.blockUI.min.js
390 ms
add-to-cart.min.js
384 ms
js.cookie.min.js
381 ms
woocommerce.min.js
390 ms
ie-compat.min.js
484 ms
jquery.mobile.custom.min.js
486 ms
slider.js
485 ms
js
60 ms
css
68 ms
wc-blocks.css
435 ms
style.css
466 ms
front.min.js
530 ms
scripts.min.js
587 ms
smoothscroll.js
530 ms
sourcebuster.min.js
531 ms
order-attribution.min.js
530 ms
common.js
531 ms
jquery.uniform.min.js
532 ms
custom.js
530 ms
idle-timer.min.js
536 ms
Final-Teal-Logo.png
187 ms
deep-purple-poo-poo-face-title.png
188 ms
Dream-Ideas-Paperback-Cover-400.png
336 ms
amber-the-dragon-keeper.jpg
298 ms
gilroys-gobble-400.png
366 ms
Front-Cover-scaled.jpg
356 ms
Lumpiest-Pumpkin-Front-Cover-400.png
367 ms
Final-One-Tom-Turkey-Square-Cover.png
544 ms
subscribe-loader.gif
359 ms
Ollie-Come-Home-400.png
452 ms
WhataDoodleDo-400.jpg
424 ms
ShutInButton-cover-400.png
422 ms
frog-a-dog-400.png
431 ms
whats-your-poopoo-face-400.png
488 ms
finding-hampton-400-height-1-e1684862019508.png
485 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4nY1M2xYkS.ttf
28 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4nY1M2xYkS.ttf
44 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4nY1M2xYkS.ttf
39 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4nY1M2xYkS.ttf
44 ms
modules.woff
422 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd1anXulujFy8.ttf
119 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd1anXulujFy8.ttf
122 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd1anXulujFy8.ttf
119 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd1anXulujFy8.ttf
120 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc1anXulujFy8.ttf
120 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPKba1anXulujFy8.ttf
161 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a1anXulujFy8.ttf
120 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPja1anXulujFy8.ttf
136 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa1anXulujFy8.ttf
157 ms
Final-Teal-Logo.png
335 ms
Final-Teal-Logo.png
71 ms
woocommerce-smallscreen.css
70 ms
style.min.css
76 ms
style.min.css
88 ms
Final-Teal-Logo.png
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
5 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf
5 ms
familyfables.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
familyfables.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
familyfables.org SEO score
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 Familyfables.org 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 Familyfables.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.
familyfables.org
Open Graph description is not detected on the main page of Family Fables. 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: