5.9 sec in total
385 ms
5.2 sec
260 ms
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.clWe analyzed Inapi.cl page load time and found that the first response time was 385 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
inapi.cl performance score
name
value
score
weighting
Value7.6 s
1/100
10%
Value12.4 s
0/100
25%
Value14.4 s
1/100
10%
Value900 ms
31/100
30%
Value0.024
100/100
15%
Value12.0 s
16/100
10%
385 ms
632 ms
378 ms
251 ms
252 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 74% of them (65 requests) were addressed to the original Inapi.cl, 9% (8 requests) were made to Apis.modernizacion.cl and 3% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Inapi.cl.
Page size can be reduced by 708.7 kB (20%)
3.5 MB
2.8 MB
In fact, the total size of Inapi.cl main page is 3.5 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.8 MB which makes up the majority of the site volume.
Potential reduce by 45.5 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 9.2 kB, which is 16% 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 45.5 kB or 82% of the original size.
Potential reduce by 142.2 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. Inapi images are well optimized though.
Potential reduce by 165.4 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 165.4 kB or 61% of the original size.
Potential reduce by 355.6 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 355.6 kB or 83% of the original size.
Number of requests can be reduced by 44 (52%)
84
40
The browser has sent 84 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 15 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
inapi.cl
385 ms
w3-channel.html
632 ms
screen.css
378 ms
channels-500_js_main.html
251 ms
channels-500_js_cookies.js
252 ms
agenda.css
383 ms
jquery.min.js
74 ms
jquery-ui.min.js
92 ms
boxes-937_js_file.js
250 ms
marquesina.css
378 ms
ntg_marquesina.js
380 ms
boxes-1046_js_file.js
259 ms
ga.js
29 ms
tipografias.css
254 ms
layout.css
251 ms
header.css
256 ms
nav.css
253 ms
main.css
522 ms
footer.css
255 ms
main-bg.jpg
502 ms
body-bg.png
249 ms
logo-inapi.png
251 ms
bg_busqueda_global.png
253 ms
gobcl_regular-webfont.woff
497 ms
articles-6596_imagen.png
889 ms
btn_enviarmail.gif
256 ms
articles-5988_imagen.png
996 ms
articles-5990_imagen.png
627 ms
articles-1162_imagen.jpg
758 ms
articles-1189_imagen.jpg
636 ms
articles-2625_imagen.png
1023 ms
articles-4515_imagen.jpg
1131 ms
articles-5985_imagen.jpg
1267 ms
articles-6071_foto_portada.png
1009 ms
articles-1144_foto_portada.jpg
2662 ms
articles-1146_foto_portada.jpg
2890 ms
articles-1145_foto_portada.jpg
2771 ms
articles-4398_banner.jpg
1526 ms
articles-6487_foto_portada.jpg
1754 ms
articles-8182_foto_portada.jpg
2013 ms
articles-8151_foto_portada.jpg
2275 ms
articles-1708_banner.png
2137 ms
articles-3036_banner.jpg
2266 ms
articles-1174_banner.gif
2393 ms
articles-5293_banner.png
2520 ms
articles-6427_banner.png
2779 ms
articles-4671_banner.jpg
3147 ms
articles-1118_ddi.gif
2774 ms
articles-1118_empleos.gif
2908 ms
articles-1118_participacion.gif
3018 ms
articles-1118_transparencia.gif
3025 ms
articles-1118_solicitud.gif
3031 ms
articles-1118_licitaciones.gif
3140 ms
articles-1118_tdpi.png
3159 ms
articles-1118_trabaje_con_nosotros.jpg
3655 ms
btn_buscar_global.gif
488 ms
fondo_nav.gif
476 ms
bg_acceso_usuario.gif
474 ms
bg_titulocaja.png
496 ms
lightbox_overlay.png
714 ms
bullet_vermas_marq.gif
721 ms
bg_menuvalor.png
726 ms
sprite_accesos_destacados.png
728 ms
bullet_vermas.gif
731 ms
bullet.png
745 ms
bg_footer.jpg
1095 ms
ico_contacto_footer.png
967 ms
logo_rss.png
975 ms
__utm.gif
29 ms
barraEstado.js
362 ms
ypyJe4RG6Kg
102 ms
www-embed-player-vflZsBgOl.css
75 ms
www-embed-player.js
93 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
35 ms
ad_status.js
35 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
81 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
92 ms
iframe.php
178 ms
bootstrap.min.css
173 ms
bootstrap-theme.min.css
143 ms
style.css
182 ms
jquery.min.js
30 ms
bootstrap.min.js
199 ms
sprite.png
86 ms
topbar-search-submit-bg.png
71 ms
__utm.gif
11 ms
nr-852.min.js
16 ms
47c8f5244a
55 ms
inapi.cl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
inapi.cl 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
inapi.cl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
N/A
ISO-8859-1
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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Inapi.cl main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
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: