Your Website Score is

Similar Ranking

49
ONLINE APOTHEKE FÜR DEUTSCHLAND ▷ SHOP APOTHEKE
shop-apotheke.com
49
WEATHER - AUSTRALIA 7 DAY FORECASTS AND WEATHER RADAR - WEATHERZONE
weatherzone.com.au
49
LES VENTES PRIVÉES DE GRANDES MARQUES AVEC SHOWROOMPRIVE
showroomprive.com
49
UNIVERSITY OF JOHANNESBURG
uj.ac.za
49
SHOPGOODWILL.COM
shopgoodwill.com
49
ALLDATASHEET.COM - DATASHEET SEARCH SITE FOR ELECTRONIC COMPONENTS AND SEMICONDUCTORS AND OTHER SEMICONDUCTORS.
alldatasheet.com
49
ETEXTBOOKS | RENT OR BUY ONLINE TEXTBOOKS | VITALSOURCE
vitalsource.com

Latest Sites

14
PORTSTONE PARTNERS LIMITED
portstonepartnersltd.com
14
VENICTRADE.COM
venictrade.com
14
COINLUNO.COM
coinluno.com
14
SIGNCURRENCY.COM
signcurrency.com
14
ALLTRADESFX.COM
alltradesfx.com
19
MODERN KITCHENS | READIKIT | HOME PAGE
readikit.com
1

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

49 ufrgs.br Last Updated: 9 months

Success 47% of passed verification steps
Warning 23% of total warning
Errors 30% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 69%
Best Practices Desktop Score 62%
SEO Desktop Score 80%
Progressive Web App Desktop Score 8%
Performance Mobile Score 19%
Best Practices Mobile Score 62%
SEO Mobile Score 67%
Progressive Web App Mobile Score 7%
Page Authority Authority 54%
Domain Authority Domain Authority 84%
Moz Rank 5.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 59 Characters
INICIAL — UFRGS | UNIVERSIDADE FEDERAL DO RIO GRANDE DO SUL
Meta Description 303 Characters
A Universidade Federal do Rio Grande do Sul, com sede em Porto Alegre, capital do Estado do Rio Grande do Sul, é uma instituição centenária, reconhecida nacional e internacionalmente. Ministra cursos em todas as áreas do conhecimento e em todos os níveis, desde o Ensino Fundamental até a Pós-Graduação.
Effective URL 33 Characters
http://www.ufrgs.br/ufrgs/inicial
Excerpt Page content
Inicial — UFRGS | Universidade Federal do Rio Grande do SulInicial — UFRGS | Universidade Federal do Rio Grande do SulIr para o conteúdo Ir para a navegação Portal do Governo Brasileiro ...
Keywords Cloud Density
ufrgs30 notícias9 site9 mídia8 ingresso8 carregando7 vestibular5 reitoria4 sisu4 universidade4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
ufrgs 30
notícias 9
site 9
mídia 8
ingresso 8
carregando 7
vestibular 5
reitoria 4
sisu 4
universidade 4
Google Preview Your look like this in google search result
INICIAL — UFRGS | UNIVERSIDADE FEDERAL DO RIO GRANDE DO SUL
http://www.ufrgs.br/ufrgs/inicial
A Universidade Federal do Rio Grande do Sul, com sede em Porto Alegre, capital do Estado do Rio Grande do Sul, é uma instituição centenária, reconheci
Robots.txt File Detected
Sitemap.xml File No Found
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
Updated: 1970-01-01 / 51 years
Create on: 1970-01-01 / 51 years
Expires on: 1970-01-01 / 618 months 15 days

Universidade Federal do Rio Grande do Sul ,BR BR BR BR BR
Registrar Email: [email protected]

Nameservers
ns1.ufrgs.br
143.54.1.58
2804:1f20:0:1000::58
ns2.ufrgs.br
143.54.1.59
2804:1f20:0:1000::59
pampa.tche.br
Page Size Code & Text Ratio
Document Size: ~44.95 KB
Code Size: ~27.43 KB
Text Size: ~17.52 KB Ratio: 38.97%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Minify JavaScript Potential savings of 9 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 129 requests • 2,547 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 84 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 140 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 2.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 18.4 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 30 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 39 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 853 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Does not use HTTPS 97 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
User Timing marks and measures 6 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 560 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,260 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 21 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 417 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 350 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 230 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Defer offscreen images Potential savings of 387 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 7 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 2,547 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 21 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 823 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

Mobile

Mobile Screenshot
Does not use HTTPS 97 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
User Timing marks and measures 6 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 430 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 3,440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 21 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 417 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 4,890 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 4,290 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 7.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Defer offscreen images Potential savings of 540 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 10.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 12.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 2,607 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 9.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.8 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 21 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 823 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 9 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.8 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 130 requests • 2,607 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 84 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 1,310 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 19.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive at 19.4 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 7156 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 660 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 41 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 853 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 18 Jan 2020 15:15:08 GMT
Content-Type: text/html;charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
X-Frame-Options: SAMEORIGIN
Content-Language: pt-br
Cache-Control: max-age=60
Age: 0
proxyweb-backend: http_plone_ufrgs
proxyweb_site: ufrgs
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome