Tools & Wizards About Us
pucho.ai screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pucho.ai

Pucho AI

Page Load Speed

1.2 sec in total

First Response

146 ms

Resources Loaded

1 sec

Page Rendered

77 ms

pucho.ai screenshot

About Website

Visit pucho.ai now to see the best up-to-date Pucho content and also check out these interesting facts you probably never knew about pucho.ai

Comming soon

Visit pucho.ai

Key Findings

We analyzed Pucho.ai page load time and found that the first response time was 146 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

pucho.ai performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

pucho.ai

146 ms

pucho.ai

295 ms

css

40 ms

css

57 ms

style.css

71 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 72% of them (28 requests) were addressed to the original Pucho.ai, 21% (8 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (398 ms) belongs to the original domain Pucho.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.5 kB (15%)

Content Size

298.0 kB

After Optimization

253.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pucho.ai main page is 298.0 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. 35% of websites need less resources to load. Javascripts take 228.9 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 7.2 kB

  • Original 9.9 kB
  • After minification 7.9 kB
  • After compression 2.6 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 1.9 kB, which is 20% 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 7.2 kB or 73% of the original size.

Image Optimization

-7%

Potential reduce by 327 B

  • Original 4.7 kB
  • After minification 4.4 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. Pucho images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 22.4 kB

  • Original 228.9 kB
  • After minification 228.9 kB
  • After compression 206.5 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

-27%

Potential reduce by 14.5 kB

  • Original 54.5 kB
  • After minification 54.4 kB
  • After compression 40.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. Pucho.ai needs all CSS files to be minified and compressed as it can save up to 14.5 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (90%)

Requests Now

29

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pucho.ai

pucho.ai

146 ms

pucho.ai

pucho.ai

295 ms

css

css

40 ms

css

css

57 ms

style.css

style.css

71 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

207 ms

angular.min.js

angular.min.js

307 ms

modernizr.custom.js

modernizr.custom.js

188 ms

app.js

app.js

199 ms

controllers.js

controllers.js

205 ms

notifyMe.js

notifyMe.js

251 ms

jquery.countdown.js

jquery.countdown.js

250 ms

jquery.placeholder.js

jquery.placeholder.js

265 ms

photoswipe.min.js

photoswipe.min.js

274 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

275 ms

jquery.lettering.js

jquery.lettering.js

312 ms

jquery.textillate.js

jquery.textillate.js

312 ms

dotty.js

dotty.js

333 ms

jquery.nicescroll.js

jquery.nicescroll.js

343 ms

js

js

79 ms

init.js

init.js

344 ms

white_Pucho.png

white_Pucho.png

368 ms

jquery.countdown.css

jquery.countdown.css

313 ms

animate.css

animate.css

309 ms

component2.css

component2.css

332 ms

font-awesome.min.css

font-awesome.min.css

346 ms

et-line-font.css

et-line-font.css

346 ms

bootstrap.min.css

bootstrap.min.css

363 ms

inputtext.css

inputtext.css

370 ms

photoswipe.css

photoswipe.css

370 ms

default-skin.css

default-skin.css

398 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

44 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

47 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

51 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

54 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

57 ms

5aU69_a8oxmIdGl4AQ.ttf

5aU69_a8oxmIdGl4AQ.ttf

60 ms

5aU19_a8oxmIfJpbERySiA.ttf

5aU19_a8oxmIfJpbERySiA.ttf

56 ms

5aU19_a8oxmIfMJaERySiA.ttf

5aU19_a8oxmIfMJaERySiA.ttf

60 ms

Accessibility Review

pucho.ai accessibility score

81

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pucho.ai best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pucho.ai SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pucho.ai can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Pucho.ai 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

pucho.ai

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