7.6 sec in total
375 ms
6.9 sec
291 ms
Visit pocoyize.com now to see the best up-to-date Pocoyize content and also check out these interesting facts you probably never knew about pocoyize.com
¡Diseña los personajes que quieras con Pocoyize y crea ahora divertidos avatares online! Y si lo deseas, compra tus figuras personalizadas.
Visit pocoyize.comWe analyzed Pocoyize.com page load time and found that the first response time was 375 ms and then it took 7.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.
pocoyize.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value10.6 s
0/100
25%
Value9.8 s
10/100
10%
Value5,310 ms
0/100
30%
Value0.46
19/100
15%
Value13.9 s
10/100
10%
375 ms
503 ms
340 ms
811 ms
36 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Pocoyize.com, 73% (80 requests) were made to Pocoyo.com and 7% (8 requests) were made to Sumome-140a.kxcdn.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Pocoyo.com.
Page size can be reduced by 1.6 MB (56%)
2.9 MB
1.3 MB
In fact, the total size of Pocoyize.com main page is 2.9 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 149.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 149.8 kB or 78% of the original size.
Potential reduce by 57.6 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. Pocoyize images are well optimized though.
Potential reduce by 721.9 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 721.9 kB or 68% of the original size.
Potential reduce by 672.5 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. Pocoyize.com needs all CSS files to be minified and compressed as it can save up to 672.5 kB or 91% of the original size.
Number of requests can be reduced by 46 (45%)
102
56
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pocoyize. 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 15 to 1 for CSS and as a result speed up the page load time.
pocoyize.com
375 ms
www.pocoyize.com
503 ms
340 ms
pocoyize
811 ms
font-awesome.min.css
36 ms
oocss.min.css
210 ms
style.css
308 ms
glyphicon.min.css
207 ms
cookies.min.css
210 ms
jquery-ui.min.css
211 ms
css
45 ms
css
57 ms
jquery-1.11.1.min.js
610 ms
jquery.ui.core.min.js
410 ms
jquery.ui.datepicker.min.js
512 ms
general.min.js
410 ms
angular.min.js
721 ms
ressController.angular.js
510 ms
adapt-config.min.js
634 ms
adapt.min.js
634 ms
jquery.lazyload.min.js
715 ms
nyroModal.min.css
714 ms
jquery.nyroModal.custom.min.js
918 ms
responsiveslides.min.css
816 ms
responsiveslides.min.js
820 ms
jwplayer.js
1126 ms
jquery.easing-1.3.min.js
924 ms
jquery.easing.compatibility.js
925 ms
jquery.mousewheel-3.1.12.min.js
1020 ms
jquery.jcarousellite.min.js
1026 ms
script.js
1122 ms
defaultTheme.css
1137 ms
load.sumome.com
309 ms
addthis_widget.js
24 ms
1200.min.css
399 ms
css
14 ms
analytics.js
132 ms
logo-pocoyo.jpg
216 ms
es.png
207 ms
pt.png
208 ms
it.png
206 ms
en.png
209 ms
ru.png
212 ms
tr.png
294 ms
pocoyizador-figuras-01.png
609 ms
pocoyizador-figuras-02.png
611 ms
pocoyizador-figuras-03.png
612 ms
pocoyizador-figuras-04.png
720 ms
pocoyizador-figuras-05.png
612 ms
pocoyizador-figuras-06.png
896 ms
comansi.png
814 ms
image.php
956 ms
image.php
964 ms
image.php
1058 ms
image.php
1159 ms
image.php
1258 ms
image.php
1341 ms
image.php
1395 ms
image.php
1401 ms
image.php
1493 ms
image.php
1596 ms
image.php
1695 ms
image.php
1777 ms
image.php
1736 ms
image.php
1835 ms
image.php
1928 ms
image.php
2033 ms
image.php
2130 ms
image.php
2169 ms
image.php
2215 ms
image.php
2274 ms
lazy-load-default.jpg
2434 ms
bt-app-store.png
2240 ms
299 ms
hr7Un5rTZbWMVxBLJvXJaaCWcynf_cDxXwCLxiixG1c.ttf
62 ms
fgA8TJeZk_EzRCmWevkeGXYhjbSpvc47ee6xR_80Hnw.ttf
63 ms
fontawesome-webfont.woff
62 ms
gs9rvuKkonuI8a0WE1GSuwLUuEpTyoUstqEm5AMlJo4.ttf
62 ms
collect
24 ms
glyphicons-halflings-regular.woff
2438 ms
bt-google-play.png
2178 ms
bt-windows-store.png
2223 ms
bt-windows-phone.png
2247 ms
logo-zinkia.png
2283 ms
logo_gob_espana.jpg
2474 ms
logo_gob_espana-2.jpg
2440 ms
service.js
18 ms
sumome-share-client.css
15 ms
css
30 ms
load
197 ms
sprite-social.png
2034 ms
nav-sep.png
2048 ms
title-pocoyize-mod.png
2180 ms
star-new.png
2129 ms
facebooklike-white-60.png
24 ms
facebook-white-60.png
7 ms
googleplus-white-60.png
10 ms
pinterest-white-60.png
7 ms
twitter-white-60.png
8 ms
sumome-white-60.png
8 ms
bg-pocoyizer.png
2439 ms
bg-to-top.png
2048 ms
home-apps.jpg
2190 ms
home-pocoyizate-avatar-online.jpg
2179 ms
home-concursos-pocoyo.png
2494 ms
boost
17 ms
300lo.json
46 ms
sh.07f0d9bf220d07a763adad1e.html
37 ms
custom-messages.13f2fa2c8d98ff03ac2a.js
35 ms
layers.173914a8ea2767730b7b.js
36 ms
pocoyize.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
pocoyize.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
pocoyize.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pocoyize.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Pocoyize.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.
pocoyize.com
Open Graph description is not detected on the main page of Pocoyize. 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: