Tools & Wizards About Us
inapi.cl screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

inapi.cl

Inapi - Instituto Nacional de Propiedad Industrial

Page Load Speed

5.4 sec in total

First Response

654 ms

Resources Loaded

4.2 sec

Page Rendered

506 ms

inapi.cl screenshot

About Website

Click here to check amazing Inapi content for Chile. Otherwise, check out these important facts you probably never knew about inapi.cl

Organismo encargado de la administración y atención de los servicios de la propiedad industrial en Chile.

Visit inapi.cl

Key Findings

We analyzed Inapi.cl page load time and found that the first response time was 654 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

inapi.cl performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

inapi.cl

654 ms

ScriptResource.axd

397 ms

ScriptResource.axd

262 ms

ScriptResource.axd

529 ms

fonts.css

267 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 95% of them (79 requests) were addressed to the original Inapi.cl, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to F1-na.readspeaker.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Inapi.cl.

Page Optimization Overview & Recommendations

Page size can be reduced by 466.9 kB (18%)

Content Size

2.6 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inapi.cl main page is 2.6 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. 40% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 45.6 kB

  • Original 56.5 kB
  • After minification 53.8 kB
  • After compression 10.9 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 45.6 kB or 81% of the original size.

Image Optimization

-15%

Potential reduce by 359.8 kB

  • Original 2.4 MB
  • After minification 2.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. Obviously, Inapi needs image optimization as it can save up to 359.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-33%

Potential reduce by 44.4 kB

  • Original 134.6 kB
  • After minification 134.3 kB
  • After compression 90.2 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 44.4 kB or 33% of the original size.

CSS Optimization

-22%

Potential reduce by 17.1 kB

  • Original 76.2 kB
  • After minification 76.2 kB
  • After compression 59.1 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. Inapi.cl needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (69%)

Requests Now

75

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inapi.cl

inapi.cl

654 ms

ScriptResource.axd

ScriptResource.axd

397 ms

ScriptResource.axd

ScriptResource.axd

262 ms

ScriptResource.axd

ScriptResource.axd

529 ms

fonts.css

fonts.css

267 ms

bootstrap.min.css

bootstrap.min.css

469 ms

font-awesome.min.css

font-awesome.min.css

314 ms

owl.carousel.css

owl.carousel.css

407 ms

owl.theme.css

owl.theme.css

408 ms

jquery-ui.css

jquery-ui.css

474 ms

animate.css

animate.css

552 ms

push.css

push.css

554 ms

flexslider.css

flexslider.css

555 ms

normalize.css

normalize.css

626 ms

estilos.css

estilos.css

630 ms

estilos-home.css

estilos-home.css

657 ms

webReader.js

webReader.js

148 ms

ga.js

ga.js

18 ms

bootstrap.min.js

bootstrap.min.js

681 ms

jquery-migrate.min.js

jquery-migrate.min.js

693 ms

bootstrap.min.js

bootstrap.min.js

692 ms

jquery.flexslider.js

jquery.flexslider.js

785 ms

owl.carousel.js

owl.carousel.js

789 ms

jquery.countimator.js

jquery.countimator.js

788 ms

push.js

push.js

791 ms

shortcut.js

shortcut.js

807 ms

viewportchecker.js

viewportchecker.js

812 ms

funciones.js

funciones.js

820 ms

funciones_widget.js

funciones_widget.js

797 ms

wow.js

wow.js

824 ms

funciones-home.js

funciones-home.js

796 ms

language-selector.js

language-selector.js

817 ms

__utm.gif

__utm.gif

76 ms

descargar_guia.png

descargar_guia.png

2197 ms

cerrar.png

cerrar.png

275 ms

en.png

en.png

379 ms

es.png

es.png

379 ms

fr.png

fr.png

407 ms

zh.png

zh.png

427 ms

logo-interior.png

logo-interior.png

428 ms

ic-login1.png

ic-login1.png

406 ms

ic-login2.png

ic-login2.png

507 ms

slide_principal_inapi.jpg

slide_principal_inapi.jpg

685 ms

bg-nubes.png

bg-nubes.png

558 ms

fig-rec1.svg

fig-rec1.svg

574 ms

fig-rec2.svg

fig-rec2.svg

848 ms

fig-rec3.svg

fig-rec3.svg

856 ms

banner-home_plataforma-sin-texto.png

banner-home_plataforma-sin-texto.png

2683 ms

banner-cuenta-publica-2024-pc.jpg

banner-cuenta-publica-2024-pc.jpg

753 ms

inventores-pai.jpg

inventores-pai.jpg

1667 ms

noticia_martes_de_pi.jpg

noticia_martes_de_pi.jpg

1542 ms

noticia-cuenta-publica-portada.jpg

noticia-cuenta-publica-portada.jpg

1439 ms

bg-cooperacion.png

bg-cooperacion.png

2348 ms

logo-prosur.png

logo-prosur.png

1125 ms

logo-ompi.png

logo-ompi.png

1399 ms

2024-plan.png

2024-plan.png

1640 ms

teletrabajo.png

teletrabajo.png

1633 ms

lobby.png

lobby.png

1704 ms

collect

collect

23 ms

codigo-etica.png

codigo-etica.png

1777 ms

Montserrat-Light.woff

Montserrat-Light.woff

1723 ms

Montserrat-Hairline.woff

Montserrat-Hairline.woff

1747 ms

Montserrat-Regular.woff

Montserrat-Regular.woff

1787 ms

Montserrat-SemiBold.woff

Montserrat-SemiBold.woff

1937 ms

Montserrat-Bold.woff

Montserrat-Bold.woff

1958 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2854 ms

propiedad-industrial.png

propiedad-industrial.png

1924 ms

trafb6f93033a4548dcb97d9ff3716da78a.jpg

trafb6f93033a4548dcb97d9ff3716da78a.jpg

2035 ms

banner-recursos.jpg

banner-recursos.jpg

2049 ms

d-d-home.png

d-d-home.png

2034 ms

gestion-institucional.png

gestion-institucional.png

2147 ms

empleos-publicos.png

empleos-publicos.png

2138 ms

licitaciones.png

licitaciones.png

2097 ms

ley-transparencia.png

ley-transparencia.png

2133 ms

ley-transparencia71c9a78d48c24735acf16af7b4690be4e02a66ec4d364e3d8006006b5a4dba21.jpg

ley-transparencia71c9a78d48c24735acf16af7b4690be4e02a66ec4d364e3d8006006b5a4dba21.jpg

2162 ms

gob-2.jpg

gob-2.jpg

2162 ms

logo-footer.png

logo-footer.png

2211 ms

img-footer.png

img-footer.png

2243 ms

bg-menu-sec.png

bg-menu-sec.png

2197 ms

aa.png

aa.png

2146 ms

bg-propiedad.png

bg-propiedad.png

2217 ms

l-left.png

l-left.png

2141 ms

l-right.png

l-right.png

2062 ms

Accessibility Review

inapi.cl accessibility score

74

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

inapi.cl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

inapi.cl SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

inapi.cl

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