Tools & Wizards About Us

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

yapo.cl

Marketplace en Chile - miles de anuncios clasificados en Yapo

Page Load Speed

988 ms in total

First Response

142 ms

Resources Loaded

496 ms

Page Rendered

350 ms

About Website

Visit yapo.cl now to see the best up-to-date Yapo content for Chile and also check out these interesting facts you probably never knew about yapo.cl

Herramienta de confianza #1 en compra y venta. Categorías: Vehículos, Bienes Raíces, Empleos, Electrónica, y más. Su plataforma confiable y segura, con nuevas opciones TODOS los días.

Visit yapo.cl

Key Findings

We analyzed Yapo.cl page load time and found that the first response time was 142 ms and then it took 846 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

yapo.cl performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

yapo.cl

142 ms

www.yapo.cl

75 ms

styles.ad100276e5bcaf19.css

45 ms

storefront.svg

70 ms

email-decode.min.js

20 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Yapo.cl, 84% (37 requests) were made to Storage.googleapis.com and 9% (4 requests) were made to Static.yapo.cl. The less responsive or slowest element that took the longest time to load (272 ms) relates to the external source Storage.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.6 kB (44%)

Content Size

355.2 kB

After Optimization

197.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yapo.cl main page is 355.2 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. Only 5% of websites need less resources to load. HTML takes 178.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 153.2 kB

  • Original 178.5 kB
  • After minification 175.4 kB
  • After compression 25.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 153.2 kB or 86% of the original size.

Image Optimization

-8%

Potential reduce by 897 B

  • Original 11.5 kB
  • After minification 10.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. Yapo images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 3.3 kB

  • Original 158.1 kB
  • After minification 158.1 kB
  • After compression 154.8 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

-2%

Potential reduce by 147 B

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

Requests Breakdown

Number of requests can be reduced by 32 (76%)

Requests Now

42

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

yapo.cl accessibility score

76

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-*] attributes are not valid or misspelled

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

yapo.cl best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

yapo.cl SEO score

97

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

High

Tap targets are not sized appropriately

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 Yapo.cl 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 Yapo.cl 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

Open Graph data is detected on the main page of Yapo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: