LNCC.BR LNCC - Laboratório Nacional de Computação Científica


lncc.br website information.

lncc.br domain name is registered by .BR top-level domain registry. See the other sites registred in .BR domain zone.

Following name servers are specified for lncc.br domain:

  • server1.pop-rj.rnp.br
  • view.lncc.br

and probably website lncc.br is hosted by AMAZON-02 - Amazon.com, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AMAZON-02 - Amazon.com, Inc., US hosting company.

According to Alexa traffic rank the highest website lncc.br position was 5092 (in the world). The lowest Alexa rank position was 998482. Now website lncc.br ranked in Alexa database as number 151739 (in the world).

Website lncc.br Desktop speed measurement score (40/100) is better than the results of 14.88% of other sites shows that the page desktop performance can be improved.

lncc.br Mobile usability score (94/100) is better than the results of 36.81% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of lncc.br (43/100) is better than the results of 22.8% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-20-2024 N/AN/A
Nov-19-2024 151,739-1,394
Nov-18-2024 150,345-3,364
Nov-17-2024 146,9811,669
Nov-16-2024 148,6502,711
Nov-15-2024 151,3613,799
Nov-14-2024 155,160-8,551

Advertisement

lncc.br Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



lncc.br whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


% Copyright (c) Nic.br
% The use of the data below is only permitted as described in
% full by the terms of use at https://registro.br/termo/en.html ,
% being prohibited its distribution, commercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2021-12-16T22:40:52-03:00 - IP: 167.99.102.248

% Permission denied. For more information, contact abuse@registro.br

% Security and mail abuse issues should also be addressed to
% cert.br, http://www.cert.br/ , respectivelly to cert@cert.br
% and mail-abuse@cert.br
%
% whois.registro.br accepts only direct match queries. Types
% of queries are: domain (.br), registrant (tax ID), ticket,
% provider, CIDR block, IP and ASN.

lncc.br server information

Servers Location

IP Address
146.134.9.171
Country
Brazil
Region
Rio de Janeiro
City
Petropolis

lncc.br desktop page speed rank

Last tested: 2019-07-02


Desktop Speed Bad
40/100

lncc.br Desktop Speed Test Quick Summary


priority - 155 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1.5MiB (59% reduction).

Compressing and resizing https://imagens.lncc.br/noticias/semin%C3%83%C2%A1…ulho%20para%20site.png could save 803.9KiB (87% reduction).
Compressing and resizing http://lncc.br/estrutura/images/banner-sdumont.png could save 235.4KiB (77% reduction).
Compressing and resizing http://lncc.br/estrutura/images/banner-grupos-pesquisa.png could save 118.4KiB (77% reduction).
Compressing https://imagens.lncc.br/noticias/petascale_computing_institute_logo.png could save 103.8KiB (20% reduction).
Compressing https://imagens.lncc.br/noticias/gadelha99.jpg could save 83.6KiB (54% reduction).
Compressing and resizing http://lncc.br/images/logo_lncc.png could save 50.3KiB (87% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/p240…ea7bc94786&oe=5DC552E3 could save 20.5KiB (27% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/s403…909b0eb173&oe=5DBD20D4 could save 13.6KiB (25% reduction).
Compressing http://lncc.br/images/sm_instagram.png could save 11.9KiB (98% reduction).
Compressing http://lncc.br/estrutura/images/pos_graduacao.png could save 11.7KiB (29% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/s320…d272d09f03&oe=5DAE484A could save 9.5KiB (25% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/yv/r/2jWGx3WzwbJ.png could save 9.4KiB (34% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/p296…1d7ab27bad&oe=5D7ADD5A could save 7.5KiB (23% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/p168…f51cbb3293&oe=5D7DBBD1 could save 6.5KiB (23% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/s235…3effd00743&oe=5DBA5367 could save 4.7KiB (21% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/p118…216a445813&oe=5DC69566 could save 3KiB (19% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/onuUJj0tCqE.png could save 2.8KiB (73% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y3/r/n-uOOobFC9i.png could save 2.7KiB (86% reduction).
Compressing https://yt3.ggpht.com/-LPVynuneAXA/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 2.1KiB (42% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/faq_tyJQplI.png could save 2.1KiB (31% reduction).
Compressing https://yt3.ggpht.com/-tJO3CDV2OeU/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 1.2KiB (40% reduction).
Compressing http://lncc.br/images/sm_linkedin.png could save 940B (79% reduction).
Compressing http://lncc.br/images/seta_azul.png could save 932B (74% reduction).
Compressing http://lncc.br/images/sm_youtube.png could save 923B (60% reduction).
Compressing http://lncc.br/images/sm_facebook.png could save 921B (75% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/s130…65829ed016&oe=5DB7C50B could save 867B (18% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t39.2147-6/…3c36875afc&oe=5D80F432 could save 860B (13% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/s130…3bc29e548b&oe=5DB563BD could save 856B (16% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/p118…84c2d5cc6a&oe=5DC0B33B could save 806B (14% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-0/p118…3cd8bc8198&oe=5DC4F58D could save 758B (12% reduction).
Compressing https://translate.googleapis.com/translate_static/img/te_bk.gif could save 683B (80% reduction).
Compressing https://translate.googleapis.com/translate_static/img/te_ctrl3.gif could save 591B (42% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/wrCiWd_JmQD.png could save 296B (30% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-1/p50x…50920929a8&oe=5D7E4CA6 could save 275B (11% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-1/p50x…72ad3e3348&oe=5D7E4CA6 could save 275B (11% reduction).
Compressing https://scontent-ort2-1.xx.fbcdn.net/v/t1.0-1/p50x…8f4aaef0bf&oe=5D7E4CA6 could save 275B (11% reduction).

priority - 4 Leverage 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://imagens.lncc.br/noticias/cartaz_interpore2019_baixa.jpg (expiration not specified)
https://imagens.lncc.br/noticias/gadelha99.jpg (expiration not specified)
https://imagens.lncc.br/noticias/petascale_computing_institute_logo.png (expiration not specified)
https://imagens.lncc.br/noticias/semin%C3%83%C2%A1…ulho%20para%20site.png (expiration not specified)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://connect.facebook.net/pt_BR/sdk.js (20 minutes)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:

http://lncc.br/css/bootstrap.css

priority - 0 Minify 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 2.5KiB (22% reduction).

Minifying http://lncc.br/estrutura/default.php could save 2.5KiB (22% reduction) after compression.

priority - 0 Minify 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 2.3KiB (20% reduction).

Minifying http://lncc.br/css/main.css could save 1.5KiB (20% reduction) after compression.
Minifying http://lncc.br/css/maincontraste.css could save 876B (19% reduction) after compression.

priority - 0 Minify 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 1.1KiB (31% reduction).

Minifying https://connect.facebook.net/pt_BR/sdk.js could save 674B (39% reduction) after compression.
Minifying http://lncc.br/js/styleswitcher.js could save 306B (29% reduction) after compression.
Minifying http://lncc.br/js/main.js could save 113B (15% reduction) after compression.

lncc.br Desktop Resources

Total Resources184
Number of Hosts21
Static Resources121
JavaScript Resources47
CSS Resources13

lncc.br Desktop Resource Breakdown

lncc.br mobile page speed rank

Last tested: 2017-05-15


Mobile Speed Bad
43/100

lncc.br Mobile Speed Test Quick Summary


priority - 116 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1.1MiB (98% reduction).

Compressing and resizing http://lncc.br/images/banner_facebook_para_o_site.png could save 435.6KiB (97% reduction).
Compressing and resizing http://lncc.br/images/panoramica_lncc.jpg could save 372.9KiB (99% reduction).
Compressing and resizing http://lncc.br/images/banner_abimael.png could save 319.2KiB (99% reduction).
Compressing http://lncc.br/images/logo.png could save 1.1KiB (18% reduction).
Compressing http://lncc.br/images/seta_azul.png could save 932B (74% reduction).

priority - 16 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:

http://lncc.br/css/bootstrap.css
http://lncc.br/css/font-awesome.min.css
http://lncc.br/css/main.css
http://fonts.googleapis.com/css?family=Open+Sans:3…ic,400,600,700,300,800

priority - 14 Leverage 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:

http://lncc.br/css/bootstrap.css (expiration not specified)
http://lncc.br/css/font-awesome.min.css (expiration not specified)
http://lncc.br/css/main.css (expiration not specified)
http://lncc.br/css/maincontraste.css (expiration not specified)
http://lncc.br/images/banner_abimael.png (expiration not specified)
http://lncc.br/images/banner_facebook_para_o_site.png (expiration not specified)
http://lncc.br/images/incub.png (expiration not specified)
http://lncc.br/images/logo.png (expiration not specified)
http://lncc.br/images/panoramica_lncc.jpg (expiration not specified)
http://lncc.br/images/pos.png (expiration not specified)
http://lncc.br/images/seta_azul.png (expiration not specified)
http://lncc.br/js/bootstrap.min.js (expiration not specified)
http://lncc.br/js/jquery.isotope.min.js (expiration not specified)
http://lncc.br/js/jquery.js (expiration not specified)
http://lncc.br/js/jquery.prettyPhoto.js (expiration not specified)
http://lncc.br/js/main.js (expiration not specified)
http://lncc.br/js/styleswitcher.js (expiration not specified)
http://lncc.br/js/wow.min.js (expiration not specified)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)

priority - 0 Minify 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 2.1KiB (31% reduction).

Minifying http://lncc.br/estrutura/default.php could save 2.1KiB (31% reduction) after compression.

priority - 0 Minify 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 1.8KiB (19% reduction).

Minifying http://lncc.br/css/main.css could save 981B (20% reduction) after compression.
Minifying http://lncc.br/css/maincontraste.css could save 874B (19% reduction) after compression.

lncc.br Mobile Resources

Total Resources39
Number of Hosts10
Static Resources27
JavaScript Resources13
CSS Resources6

lncc.br Mobile Resource Breakdown

lncc.br mobile page usability

Last tested: 2017-05-15


Mobile Usability Good
94/100

lncc.br Mobile Usability Test Quick Summary


priority - 5 Size 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.

The tap target <a id="menu-icon" href="#"> is close to 1 other tap targets.

The tap target <a href="/acessoainform…ar=off&amp;vMenu=0">Institucional</a> and 11 others are close to other tap targets.
The tap target <a href="/lncc/estrutur…ar=off&amp;vMenu=1">Estrutura Organizacional</a> and 21 others are close to other tap targets.

lncc.br similar domains

Similar domains:
www.lncc.com
www.lncc.net
www.lncc.org
www.lncc.info
www.lncc.biz
www.lncc.us
www.lncc.mobi
www.ncc.br
www.lncc.br
www.pncc.br
www.lpncc.br
www.plncc.br
www.oncc.br
www.loncc.br
www.olncc.br
www.kncc.br
www.lkncc.br
www.klncc.br
www.lcc.br
www.lbcc.br
www.lnbcc.br
www.lbncc.br
www.lhcc.br
www.lnhcc.br
www.lhncc.br
www.ljcc.br
www.lnjcc.br
www.ljncc.br
www.lmcc.br
www.lnmcc.br
www.lmncc.br
www.lnc.br
www.lnxc.br
www.lncxc.br
www.lnxcc.br
www.lndc.br
www.lncdc.br
www.lndcc.br
www.lnfc.br
www.lncfc.br
www.lnfcc.br
www.lnvc.br
www.lncvc.br
www.lnvcc.br
www.lncx.br
www.lnccx.br
www.lncd.br
www.lnccd.br
www.lncf.br
www.lnccf.br
www.lncv.br
www.lnccv.br

lncc.br Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


lncc.br TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.