pagalo.pe Website Information
Daily Unique Visits: 862
Daily Page Views: 1,724
Income Per Day: $5
Estimated Value: $1,200
pagalo.pe is registered under .PE top-level domain. Please check other sites in .PE zone.
No name server records were found.
and is probably hosted by Telefonica del Peru S.A.A., PE. See the full list of other websites hosted by Telefonica del Peru S.A.A., PE.
The highest website pagalo.pe position in Alexa rank database was 15002 and the lowest rank position was 996638. Current position of pagalo.pe in Alexa rank database is 832085.
Desktop speed score of pagalo.pe (61/100) is better than the results of 37.05% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of pagalo.pe (62/100) is better than the results of 7.29% of other sites and means that the page is not mobile-friendly.
Mobile speed score of pagalo.pe (53/100) is better than the results of 39.51% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
pagalo.pe Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
pagalo.pe whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
Sponsoring Registrar: NIC.PE
Domain Status: ok
Registrant Name: BANCO DE LA NACION
Admin Name: jesus chavarria
Admin Email: jchavarria@bn.com.pe
Name Server: dns1.unired.net.pe
Name Server: dns2.unired.net.pe
>>> Last update of WHOIS database: 2024-02-01T02:39:47.459Z
pagalo.pe server information
Servers Location
pagalo.pe desktop page speed rank
Last tested: 2018-06-19
pagalo.pe Desktop Speed Test Quick Summary
priority - 39Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 378.7KiB (73% reduction).
Compressing https://pagalo.pe/js/bn-jquery.js could save 59.8KiB (64% reduction).
Compressing https://pagalo.pe/js/bn-funciones.js could save 35.8KiB (88% reduction).
Compressing https://pagalo.pe/css/slider.css could save 17.7KiB (88% reduction).
Compressing https://pagalo.pe/css/dialogpack.css could save 15.1KiB (80% reduction).
Compressing https://pagalo.pe/css/estilos.css could save 14.1KiB (75% reduction).
Compressing https://pagalo.pe/css/home.css could save 14KiB (81% reduction).
Compressing https://pagalo.pe/recursos/js/util.js could save 13.7KiB (79% reduction).
Compressing https://pagalo.pe/js/select.js could save 12.2KiB (73% reduction).
Compressing https://pagalo.pe/js/modernizr.js could save 9KiB (59% reduction).
Compressing https://pagalo.pe/js/jquery.tools.min.js could save 8.5KiB (64% reduction).
Compressing https://pagalo.pe/js/jquery.loader.js could save 7.1KiB (70% reduction).
Compressing https://pagalo.pe/css/bn-principal.css could save 5.7KiB (73% reduction).
Compressing https://pagalo.pe/ could save 5KiB (63% reduction).
Compressing https://pagalo.pe/js/jquery.cslider.js could save 4.9KiB (72% reduction).
Compressing https://pagalo.pe/js/jquery.placeholder.js could save 3.5KiB (67% reduction).
Compressing https://pagalo.pe/css/select.css could save 2.3KiB (69% reduction).
Compressing https://pagalo.pe/js/jquery.jnotify.min.js could save 1.6KiB (53% reduction).
Compressing https://pagalo.pe/css/tipografias.css could save 1.3KiB (82% reduction).
Compressing https://pagalo.pe/css/jquery.jnotify.min.css could save 1.1KiB (72% reduction).
Compressing https://pagalo.pe/css/resetearcss.css could save 529B (45% reduction).
priority - 13Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://pagalo.pe/css/dialogpack.css (expiration not specified)
https://pagalo.pe/css/estilos.css (expiration not specified)
https://pagalo.pe/css/home.css (expiration not specified)
https://pagalo.pe/css/jquery.jnotify.min.css (expiration not specified)
https://pagalo.pe/css/resetearcss.css (expiration not specified)
https://pagalo.pe/css/select.css (expiration not specified)
https://pagalo.pe/css/slider.css (expiration not specified)
https://pagalo.pe/css/tipografias.css (expiration not specified)
https://pagalo.pe/imagenes/bg-body2.jpg (expiration not specified)
https://pagalo.pe/imagenes/home/bg-input.jpg (expiration not specified)
https://pagalo.pe/imagenes/home/reenvioemail.png (expiration not specified)
https://pagalo.pe/imagenes/logo-pagalo-bn-2.png (expiration not specified)
https://pagalo.pe/imagenes/play.png (expiration not specified)
https://pagalo.pe/imagenes/store.png (expiration not specified)
https://pagalo.pe/js/bn-funciones.js (expiration not specified)
https://pagalo.pe/js/bn-jquery.js (expiration not specified)
https://pagalo.pe/js/jquery-ui.min.js (expiration not specified)
https://pagalo.pe/js/jquery.cslider.js (expiration not specified)
https://pagalo.pe/js/jquery.jnotify.min.js (expiration not specified)
https://pagalo.pe/js/jquery.loader.js (expiration not specified)
https://pagalo.pe/js/jquery.placeholder.js (expiration not specified)
https://pagalo.pe/js/jquery.tools.min.js (expiration not specified)
https://pagalo.pe/js/modernizr.js (expiration not specified)
https://pagalo.pe/js/select.js (expiration not specified)
https://pagalo.pe/recursos/js/util.js (expiration not specified)
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://pagalo.pe/css/bn-principal.css
https://pagalo.pe/css/tipografias.css
https://pagalo.pe/css/home.css
https://pagalo.pe/css/select.css
https://pagalo.pe/css/jquery.jnotify.min.css
https://pagalo.pe/css/estilos.css
https://pagalo.pe/css/slider.css
https://pagalo.pe/css/dialogpack.css
priority - 4Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 41.3KiB (42% reduction).
Minifying https://pagalo.pe/recursos/js/util.js could save 8KiB (46% reduction).
Minifying https://pagalo.pe/js/select.js could save 4.6KiB (28% reduction).
Minifying https://pagalo.pe/js/jquery.loader.js could save 3.5KiB (35% reduction).
Minifying https://pagalo.pe/js/jquery.cslider.js could save 2.1KiB (32% reduction).
Minifying https://pagalo.pe/js/jquery.placeholder.js could save 1.7KiB (33% reduction).
Minifying https://pagalo.pe/js/jquery.jnotify.min.js could save 695B (23% reduction).
priority - 2Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 18.5KiB (68% reduction).
Compressing https://pagalo.pe/imagenes/bg-body2.jpg could save 6.9KiB (95% reduction).
Compressing https://pagalo.pe/imagenes/home/reenvioemail.png could save 2.8KiB (76% reduction).
Compressing https://pagalo.pe/imagenes/home/bg-input.jpg could save 1.2KiB (56% reduction).
Compressing and resizing https://pagalo.pe/imagenes/store.png could save 609B (17% reduction).
priority - 1Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 14.6KiB (21% reduction).
Minifying https://pagalo.pe/css/estilos.css could save 4.5KiB (25% reduction).
Minifying https://pagalo.pe/css/slider.css could save 2.3KiB (12% reduction).
Minifying https://pagalo.pe/css/bn-principal.css could save 1.6KiB (21% reduction).
Minifying https://pagalo.pe/css/select.css could save 645B (19% reduction).
Minifying https://pagalo.pe/css/resetearcss.css could save 283B (25% reduction).
Minifying https://pagalo.pe/css/tipografias.css could save 220B (14% reduction).
priority - 0Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.4KiB (18% reduction).
pagalo.pe Desktop Resource Breakdown
Total Resources | 29 |
Number of Hosts | 1 |
Static Resources | 26 |
JavaScript Resources | 11 |
CSS Resources | 9 |
pagalo.pe mobile page speed rank
Last tested: 2018-08-25
pagalo.pe Mobile Speed Test Quick Summary
priority - 38Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 369.7KiB (73% reduction).
Compressing https://pagalo.pe/js/bn-jquery.js could save 59.8KiB (64% reduction).
Compressing https://pagalo.pe/js/bn-funciones.js could save 26.6KiB (87% reduction).
Compressing https://pagalo.pe/css/slider.css could save 17.7KiB (88% reduction).
Compressing https://pagalo.pe/css/dialogpack.css could save 15.1KiB (80% reduction).
Compressing https://pagalo.pe/css/estilos.css could save 14.1KiB (75% reduction).
Compressing https://pagalo.pe/css/home.css could save 14KiB (81% reduction).
Compressing https://pagalo.pe/recursos/js/util.js could save 13.8KiB (79% reduction).
Compressing https://pagalo.pe/js/select.js could save 12.2KiB (73% reduction).
Compressing https://pagalo.pe/js/modernizr.js could save 9KiB (59% reduction).
Compressing https://pagalo.pe/js/jquery.tools.min.js could save 8.5KiB (64% reduction).
Compressing https://pagalo.pe/js/jquery.loader.js could save 7.1KiB (70% reduction).
Compressing https://pagalo.pe/css/bn-principal.css could save 5.7KiB (73% reduction).
Compressing https://pagalo.pe/ could save 5.1KiB (63% reduction).
Compressing https://pagalo.pe/js/jquery.cslider.js could save 4.9KiB (72% reduction).
Compressing https://pagalo.pe/js/jquery.placeholder.js could save 3.5KiB (67% reduction).
Compressing https://pagalo.pe/css/select.css could save 2.3KiB (69% reduction).
Compressing https://pagalo.pe/js/jquery.jnotify.min.js could save 1.6KiB (53% reduction).
Compressing https://pagalo.pe/css/tipografias.css could save 1.3KiB (82% reduction).
Compressing https://pagalo.pe/css/jquery.jnotify.min.css could save 1.1KiB (72% reduction).
Compressing https://pagalo.pe/css/resetearcss.css could save 529B (45% reduction).
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://pagalo.pe/css/bn-principal.css
https://pagalo.pe/css/tipografias.css
https://pagalo.pe/css/home.css
https://pagalo.pe/css/select.css
https://pagalo.pe/css/jquery.jnotify.min.css
https://pagalo.pe/css/estilos.css
https://pagalo.pe/css/slider.css
https://pagalo.pe/css/dialogpack.css
priority - 20Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://pagalo.pe/css/dialogpack.css (expiration not specified)
https://pagalo.pe/css/estilos.css (expiration not specified)
https://pagalo.pe/css/home.css (expiration not specified)
https://pagalo.pe/css/jquery.jnotify.min.css (expiration not specified)
https://pagalo.pe/css/resetearcss.css (expiration not specified)
https://pagalo.pe/css/select.css (expiration not specified)
https://pagalo.pe/css/slider.css (expiration not specified)
https://pagalo.pe/css/tipografias.css (expiration not specified)
https://pagalo.pe/imagenes/bg-body2.jpg (expiration not specified)
https://pagalo.pe/imagenes/home/bg-input.jpg (expiration not specified)
https://pagalo.pe/imagenes/home/reenvioemail.png (expiration not specified)
https://pagalo.pe/imagenes/logo-pagalo-bn-2.png (expiration not specified)
https://pagalo.pe/imagenes/play.png (expiration not specified)
https://pagalo.pe/imagenes/store.png (expiration not specified)
https://pagalo.pe/js/bn-funciones.js (expiration not specified)
https://pagalo.pe/js/bn-jquery.js (expiration not specified)
https://pagalo.pe/js/jquery-ui.min.js (expiration not specified)
https://pagalo.pe/js/jquery.cslider.js (expiration not specified)
https://pagalo.pe/js/jquery.jnotify.min.js (expiration not specified)
https://pagalo.pe/js/jquery.loader.js (expiration not specified)
https://pagalo.pe/js/jquery.placeholder.js (expiration not specified)
https://pagalo.pe/js/jquery.tools.min.js (expiration not specified)
https://pagalo.pe/js/modernizr.js (expiration not specified)
https://pagalo.pe/js/select.js (expiration not specified)
https://pagalo.pe/recursos/js/util.js (expiration not specified)
priority - 3Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 31.2KiB (35% reduction).
Minifying https://pagalo.pe/recursos/js/util.js could save 8KiB (46% reduction).
Minifying https://pagalo.pe/js/select.js could save 4.6KiB (28% reduction).
Minifying https://pagalo.pe/js/jquery.loader.js could save 3.5KiB (35% reduction).
Minifying https://pagalo.pe/js/jquery.cslider.js could save 2.1KiB (32% reduction).
Minifying https://pagalo.pe/js/jquery.placeholder.js could save 1.7KiB (33% reduction).
Minifying https://pagalo.pe/js/jquery.jnotify.min.js could save 695B (23% reduction).
priority - 1Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 14.6KiB (21% reduction).
Minifying https://pagalo.pe/css/estilos.css could save 4.5KiB (25% reduction).
Minifying https://pagalo.pe/css/slider.css could save 2.3KiB (12% reduction).
Minifying https://pagalo.pe/css/bn-principal.css could save 1.6KiB (21% reduction).
Minifying https://pagalo.pe/css/select.css could save 645B (19% reduction).
Minifying https://pagalo.pe/css/resetearcss.css could save 283B (25% reduction).
Minifying https://pagalo.pe/css/tipografias.css could save 220B (14% reduction).
priority - 1Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 10.9KiB (83% reduction).
Compressing https://pagalo.pe/imagenes/home/reenvioemail.png could save 2.8KiB (76% reduction).
Compressing https://pagalo.pe/imagenes/home/bg-input.jpg could save 1.2KiB (56% reduction).
priority - 0Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.4KiB (18% reduction).
pagalo.pe Mobile Resource Breakdown
Total Resources | 29 |
Number of Hosts | 1 |
Static Resources | 26 |
JavaScript Resources | 11 |
CSS Resources | 9 |
pagalo.pe mobile page usability
Last tested: 2018-08-25
pagalo.pe Mobile Usability Test Quick Summary
priority - 40Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
¿Qué pagos se pueden realizar?
and 2 others render only 6 pixels tall (16 CSS pixels).Una vez pagada…de imprimirla.
and 4 others render only 5 pixels tall (12 CSS pixels).ingresa aquí
renders only 5 pixels tall (12 CSS pixels).Acceso a la plataforma
renders only 8 pixels tall (20 CSS pixels).Correo electrónico
and 1 others render only 5 pixels tall (14 CSS pixels).Si no eres usuario,
renders only 5 pixels tall (12 CSS pixels).Regístrate ahora
renders only 5 pixels tall (12 CSS pixels).Recuperar contraseña
renders only 5 pixels tall (12 CSS pixels).Banco de la Na…mía y Finanzas
renders only 5 pixels tall (12 CSS pixels).Atención en of…13 a 14 horas
and 2 others render only 4 pixels tall (11 CSS pixels).priority - 12Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<input id="email" type="text" name="usuario.email" class="big">
and 1 others are close to other tap targets.<a id="nuevoUsuario" href="/usuarios/nuevoUsuario.action" class="hastool">Regístrate ahora</a>
is close to 2 other tap targets.<input id="login_" type="submit" name="" class="btn3">
is close to 2 other tap targets.<a id="login_" href="/usuarios/iniR…rasenia.action" class="hastool">Recuperar contraseña</a>
is close to 1 other tap targets.priority - 10Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
priority - 3Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 1,075 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<div id="logo-pagalo"></div>
falls outside the viewport.The element
<h1>Acceso a la plataforma</h1>
falls outside the viewport.The element
<li>Correo electrónico</li>
falls outside the viewport.The element
<li>Contraseña</li>
falls outside the viewport.The element
<li id="reg_ahora">Si no eres usu…gístrate ahora</li>
falls outside the viewport.The element
<li></li>
falls outside the viewport.The element
<div>Recuperar contraseña</div>
falls outside the viewport.The element
<div class="icomoviles"></div>
falls outside the viewport.pagalo.pe HTML validation
Errors
Malformed byte sequence: “e1”.
"......" Line: 121 Column: - 9
"......" Line: 134 Column: - 19
"......" Line: 136 Column: - 8
"......" Line: 139 Column: - 14
"......" Line: 141 Column: - 26
"......" Line: 142 Column: - 68
"......" Line: 142 Column: - 98
"......" Line: 143 Column: - 53
"......" Line: 160 Column: - 134
"......"
Malformed byte sequence: “f1”.
"......" Line: 99 Column: - 48
"......" Line: 100 Column: - 75
"......" Line: 136 Column: - 47
"......" Line: 167 Column: - 193
"......" Line: 167 Column: - 216
"......"
Malformed byte sequence: “fa”.
"......" Line: 11 Column: - 215
"......" Line: 11 Column: - 269
"......" Line: 136 Column: - 111
"......" Line: 139 Column: - 81
"......" Line: 143 Column: - 271
"......"
Malformed byte sequence: “f3”.
"......" Line: 14 Column: - 24
"......" Line: 136 Column: - 174
"......" Line: 141 Column: - 12
"......" Line: 142 Column: - 88
"......" Line: 143 Column: - 75
"......" Line: 144 Column: - 29
"......" Line: 167 Column: - 180
"......"
Almost standards mode doctype. Expected “<!DOCTYPE html>”.
"... <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <h..."
A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
"...t=UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" > <titl..."
Malformed byte sequence: “bf”.
"......" Line: 138 Column: - 10
"......" Line: 141 Column: - 10
"......"
Malformed byte sequence: “e9”.
"......" Line: 138 Column: - 13
"......" Line: 143 Column: - 136
"......" Line: 143 Column: - 146
"......"
Malformed byte sequence: “ed”.
"......" Line: 144 Column: - 137
"......" Line: 160 Column: - 167
"......"
Duplicate ID “login”.
"...ontainer'><form id="login" name="login" action="/seguridad/login.action" method="post" class="formDatos" autocomplete="off"> <ol..."
Bad value “” for attribute “name” on element “input”: Must not be empty.
"... center;"><input type="submit" id="login_" name="" value="Ingresar" style="margin: 0px;"/> <..."
Duplicate ID “login_”.
"...e-block;'><a id="login_" href="/usuarios/iniRecuperarContrasenia.action" class="hastool" title="Si olvid� su contrase�a.">Recupe..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...977?mt=8"><img class="icomovil" src="/imagenes/store.png"></a> ..." Line: 190 Column: 102 - 148
"...o&hl=es"><img class="icomovil" src="/imagenes/play.png"></a> <..."
Warnings
The first occurrence of ID “login” was here.
"...uerpo2"> <div id="login"> <div..."
The first occurrence of ID “login_” was here.
"... center;"><input type="submit" id="login_" name="" value="Ingresar" style="margin: 0px;"/> <..."
pagalo.pe similar domains
www.pagalo.net
www.pagalo.org
www.pagalo.info
www.pagalo.biz
www.pagalo.us
www.pagalo.mobi
www.agalo.pe
www.pagalo.pe
www.oagalo.pe
www.poagalo.pe
www.opagalo.pe
www.lagalo.pe
www.plagalo.pe
www.lpagalo.pe
www.pgalo.pe
www.pqgalo.pe
www.paqgalo.pe
www.pqagalo.pe
www.pwgalo.pe
www.pawgalo.pe
www.pwagalo.pe
www.psgalo.pe
www.pasgalo.pe
www.psagalo.pe
www.pzgalo.pe
www.pazgalo.pe
www.pzagalo.pe
www.paalo.pe
www.pafalo.pe
www.pagfalo.pe
www.pafgalo.pe
www.pavalo.pe
www.pagvalo.pe
www.pavgalo.pe
www.patalo.pe
www.pagtalo.pe
www.patgalo.pe
www.pabalo.pe
www.pagbalo.pe
www.pabgalo.pe
www.payalo.pe
www.pagyalo.pe
www.paygalo.pe
www.pahalo.pe
www.paghalo.pe
www.pahgalo.pe
www.paglo.pe
www.pagqlo.pe
www.pagaqlo.pe
www.pagqalo.pe
www.pagwlo.pe
www.pagawlo.pe
www.pagwalo.pe
www.pagslo.pe
www.pagaslo.pe
www.pagsalo.pe
www.pagzlo.pe
www.pagazlo.pe
www.pagzalo.pe
www.pagao.pe
www.pagapo.pe
www.pagalpo.pe
www.pagaplo.pe
www.pagaoo.pe
www.pagaloo.pe
www.pagaolo.pe
www.pagako.pe
www.pagalko.pe
www.pagaklo.pe
www.pagal.pe
www.pagali.pe
www.pagaloi.pe
www.pagalio.pe
www.pagalk.pe
www.pagalok.pe
www.pagall.pe
www.pagalol.pe
www.pagallo.pe
www.pagalp.pe
www.pagalop.pe
pagalo.pe Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
pagalo.pe TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.