Tools & Wizards About Us
myplaytales.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

myplaytales.com

PlayTales Kids apps | iPhone, iPad, Android Interactive books for kids | Apps for children.

Page Load Speed

2.2 sec in total

First Response

170 ms

Resources Loaded

1.7 sec

Page Rendered

302 ms

myplaytales.com screenshot

About Website

Visit myplaytales.com now to see the best up-to-date My Play Tales content and also check out these interesting facts you probably never knew about myplaytales.com

Great digital books for kids for smartphones and tablets that make the learning process more perceptive and intuitive

Visit myplaytales.com

Key Findings

We analyzed Myplaytales.com page load time and found that the first response time was 170 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

myplaytales.com performance score

0

Network Requests Diagram

myplaytales.com

170 ms

13 ms

base_v2.css

260 ms

index.css

39 ms

shadowbox.css

64 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Myplaytales.com, 81% (50 requests) were made to Static.touchybooks.s3.amazonaws.com and 5% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.touchybooks.s3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.9 kB (13%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Myplaytales.com main page is 2.1 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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 12.4 kB

  • Original 16.7 kB
  • After minification 15.7 kB
  • After compression 4.3 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 12.4 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 84.1 kB

  • Original 1.8 MB
  • After minification 1.8 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. My Play Tales images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 155.6 kB

  • Original 236.7 kB
  • After minification 217.3 kB
  • After compression 81.1 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 155.6 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 23.8 kB

  • Original 29.6 kB
  • After minification 26.3 kB
  • After compression 5.9 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. Myplaytales.com needs all CSS files to be minified and compressed as it can save up to 23.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (20%)

Requests Now

59

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

myplaytales.com

myplaytales.com

170 ms

13 ms

base_v2.css

base_v2.css

260 ms

index.css

index.css

39 ms

shadowbox.css

shadowbox.css

64 ms

jquery-1.8.0.min.js

jquery-1.8.0.min.js

60 ms

jcarousellite.js

jcarousellite.js

43 ms

jquery.cycle.all.js

jquery.cycle.all.js

40 ms

shadowbox.js

shadowbox.js

63 ms

simplecarousel.js

simplecarousel.js

78 ms

home_v2.js

home_v2.js

63 ms

all.js

all.js

59 ms

background_body.gif

background_body.gif

62 ms

bg03.jpg

bg03.jpg

452 ms

bg01.jpg

bg01.jpg

169 ms

bg02.jpg

bg02.jpg

295 ms

03_en.png

03_en.png

720 ms

02_en.png

02_en.png

974 ms

01_en.png

01_en.png

1108 ms

playtales_logo.png

playtales_logo.png

179 ms

arrow_left.png

arrow_left.png

211 ms

arrow_right.png

arrow_right.png

242 ms

newsletter.png

newsletter.png

270 ms

movie_playtales.png

movie_playtales.png

306 ms

playtales_basic.png

playtales_basic.png

327 ms

or.png

or.png

394 ms

playtales_gold.png

playtales_gold.png

350 ms

playtales_grey.png

playtales_grey.png

378 ms

generainteractive.png

generainteractive.png

409 ms

mytalkingtoys.png

mytalkingtoys.png

421 ms

taptapkids.png

taptapkids.png

464 ms

bravo.png

bravo.png

448 ms

flag_spain.png

flag_spain.png

494 ms

flag_gb.png

flag_gb.png

471 ms

ga.js

ga.js

40 ms

menu_base.png

menu_base.png

424 ms

menu_left.png

menu_left.png

449 ms

menu_center.png

menu_center.png

452 ms

menu_right.png

menu_right.png

469 ms

more_books.png

more_books.png

483 ms

caracol-gif.gif

caracol-gif.gif

471 ms

line_.png

line_.png

493 ms

btn_iphone_appstore.png

btn_iphone_appstore.png

490 ms

btn_ipad_appstore.png

btn_ipad_appstore.png

511 ms

btn_googleplay.png

btn_googleplay.png

528 ms

btn_bbavaiable.png

btn_bbavaiable.png

532 ms

background_footer.gif

background_footer.gif

554 ms

background_footer_kids.jpg

background_footer_kids.jpg

550 ms

playtales_background.png

playtales_background.png

566 ms

btn_pint.png

btn_pint.png

585 ms

__utm.gif

__utm.gif

26 ms

ZagBold.otf

ZagBold.otf

24 ms

88 ms

xd_arbiter.php

xd_arbiter.php

42 ms

xd_arbiter.php

xd_arbiter.php

52 ms

btn_twitter.png

btn_twitter.png

557 ms

btn_facebook.png

btn_facebook.png

461 ms

playtales_background2.png

playtales_background2.png

454 ms

pages_ipad.png

pages_ipad.png

432 ms

ping

ping

43 ms

like.php

like.php

68 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

25 ms

SEO Factors

myplaytales.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myplaytales.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 Myplaytales.com main page’s claimed encoding is . 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

myplaytales.com

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