Tools & Wizards About Us
pocoyize.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

pocoyize.com

Pocoyize: crea avatares y personajes online de Pocoyo

Page Load Speed

2.8 sec in total

First Response

322 ms

Resources Loaded

2.2 sec

Page Rendered

332 ms

pocoyize.com screenshot

About Website

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.com

Key Findings

We analyzed Pocoyize.com page load time and found that the first response time was 322 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.

Performance Metrics

pocoyize.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value1.44

0/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

pocoyize.com

322 ms

es

153 ms

min-css

111 ms

min-css

183 ms

min-css

193 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 83% of them (66 requests) were addressed to the original Pocoyize.com, 6% (5 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (757 ms) belongs to the original domain Pocoyize.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.4 kB (4%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pocoyize.com main page is 1.4 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 47.7 kB

  • Original 55.0 kB
  • After minification 46.9 kB
  • After compression 7.4 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. This page needs HTML code to be minified as it can gain 8.2 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 47.7 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 6.9 kB

  • Original 1.0 MB
  • After minification 1.0 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. Pocoyize images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 438 B

  • Original 266.4 kB
  • After minification 266.4 kB
  • After compression 266.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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 425 B

  • Original 4.4 kB
  • After minification 4.4 kB
  • After compression 4.0 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (62%)

Requests Now

74

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 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 26 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pocoyize.com

pocoyize.com

322 ms

es

es

153 ms

min-css

min-css

111 ms

min-css

min-css

183 ms

min-css

min-css

193 ms

min-css

min-css

205 ms

min-css

min-css

196 ms

min-css

min-css

208 ms

min-css

min-css

216 ms

min-css

min-css

282 ms

min-css

min-css

287 ms

min-css

min-css

293 ms

min-css

min-css

298 ms

min-css

min-css

392 ms

min-css

min-css

319 ms

min-css

min-css

379 ms

min-css

min-css

384 ms

min-css

min-css

399 ms

jwplayer.js

jwplayer.js

562 ms

css

css

38 ms

css

css

55 ms

css

css

56 ms

css

css

59 ms

css

css

60 ms

jquery.min.js

jquery.min.js

411 ms

min-js

min-js

471 ms

min-js

min-js

475 ms

min-js

min-js

490 ms

min-js

min-js

492 ms

min-js

min-js

515 ms

min-js

min-js

566 ms

min-js

min-js

570 ms

min-js

min-js

581 ms

min-js

min-js

591 ms

js

js

85 ms

min-js

min-js

609 ms

min-js

min-js

654 ms

min-js

min-js

662 ms

min-js

min-js

667 ms

min-js

min-js

675 ms

min-js

min-js

680 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

708 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

750 ms

min-js

min-js

757 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

659 ms

min-js

min-js

610 ms

min-js

min-js

594 ms

animate.css

animate.css

532 ms

analytics.js

analytics.js

248 ms

logo_zinkia.png

logo_zinkia.png

196 ms

slider-fullscreen-slide-home-4.jpg

slider-fullscreen-slide-home-4.jpg

498 ms

product-pocoyo-shape.png

product-pocoyo-shape.png

268 ms

product-shuriken-shape.png

product-shuriken-shape.png

195 ms

product-mola-shape.png

product-mola-shape.png

271 ms

background-img-7.jpg

background-img-7.jpg

499 ms

muchoy%C3%B3-blog-zinkia.jpg

muchoy%C3%B3-blog-zinkia.jpg

277 ms

youtube-blog-zinkia.jpg

youtube-blog-zinkia.jpg

364 ms

licencing-blog-zinkia.jpg

licencing-blog-zinkia.jpg

441 ms

ghost-bros-blog-zinkia.jpg

ghost-bros-blog-zinkia.jpg

450 ms

newsletter-mayo-2023luppa.jpg

newsletter-mayo-2023luppa.jpg

371 ms

newsletter-mayo-2023-Pocoy%C3%B3-20-a%C3%B1os.jpg

newsletter-mayo-2023-Pocoy%C3%B3-20-a%C3%B1os.jpg

462 ms

background-img-10.jpg

background-img-10.jpg

542 ms

proyecto-moving-pocoyo.png

proyecto-moving-pocoyo.png

533 ms

nuevo-proyecto-avanza2.png

nuevo-proyecto-avanza2.png

547 ms

banner-zinkia-croupier.png

banner-zinkia-croupier.png

551 ms

logo_principal.png

logo_principal.png

588 ms

mecd.png

mecd.png

587 ms

mec.png

mec.png

626 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

468 ms

font

font

20 ms

font

font

28 ms

fontello.woff

fontello.woff

530 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

504 ms

collect

collect

14 ms

collect

collect

44 ms

js

js

63 ms

ga-audiences

ga-audiences

80 ms

loader.gif

loader.gif

97 ms

font

font

34 ms

revicons.woff

revicons.woff

92 ms

Accessibility Review

pocoyize.com accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

pocoyize.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pocoyize.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    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.

Social Sharing Optimization

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: