Your Website Score is

Similar Ranking

44
ENPC.FR | ECOLE DES PONTS PARISTECH
enpc.fr
44
РОССИЙСКАЯ ТАМОЖЕННАЯ АКАДЕМИЯ
donrta.customs.ru
44
INICIO | UNIVERSIDADE DE VIGO
uvigo.gal
44
ERROR
glos.ac.uk
44
EMLYON BUSINESS SCHOOL : GRANDE ÉCOLE DE MANAGEMENT ET COMMERCE - ESC LYON, FRANCE - EMLYON BUSINESS SCHOOL
em-lyon.com
44
INTERNATIONAL BALKAN UNIVERSITY (IBU) - EXCELLENCE FOR THE FUTURE!
ibu.edu.mk
44
UNIVERSITY FOR TECHNOLOGY AND DESIGN | HARBOUR.SPACE BARCELONA
harbour.space

44 uvigo.gal Last Updated: 4 months

Success 70% of passed verification steps
Warning 15% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 95%
Best Practices Desktop Score 77%
SEO Desktop Score 91%
Progressive Web App Desktop Score 54%
Performance Mobile Score 80%
Best Practices Mobile Score 77%
SEO Mobile Score 90%
Progressive Web App Mobile Score 56%
Page Authority Authority 46%
Domain Authority Domain Authority 60%
Moz Rank 4.6/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 29 Characters
INICIO | UNIVERSIDADE DE VIGO
Meta Description 256 Characters
A Universidade de Vigo é unha institución pública, innovadora e con vocación internacional. Ten unha ampla oferta en títulos de grao, posgrao, mestrados e programas de doutoramento. Situada no sur de Galicia, conta con campus en Vigo, Ourense e Pontevedra.
Effective URL 21 Characters
https://www.uvigo.gal
Excerpt Page content
Inicio | Universidade de Vigo Ir o contido principal ...
Keywords Cloud Density
campus37 novas17 vigo16 uvigo15 investigación14 universidade13 para12 pontevedra11 bolsas10 centros10
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
campus 37
novas 17
vigo 16
uvigo 15
investigación 14
universidade 13
para 12
pontevedra 11
bolsas 10
centros 10
Google Preview Your look like this in google search result
INICIO | UNIVERSIDADE DE VIGO
https://www.uvigo.gal
A Universidade de Vigo é unha institución pública, innovadora e con vocación internacional. Ten unha ampla oferta en títulos de grao, posgrao, mestrad
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~205.53 KB
Code Size: ~131.76 KB
Text Size: ~73.77 KB Ratio: 35.89%

Estimation Traffic and Earnings

413
Unique Visits
Daily
764
Pages Views
Daily
$0
Income
Daily
11,564
Unique Visits
Monthly
21,774
Pages Views
Monthly
$0
Income
Monthly
133,812
Unique Visits
Yearly
256,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Use video formats for animated content Potential savings of 3,370 KB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Serve static assets with an efficient cache policy 56 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 120 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.3 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
Estimated Input Latency 10 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 74 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 260 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
Server response times are low (TTFB) Root document took 310 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 390 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 0 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 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.3 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 11 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 2,031 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.4 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.2 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).
Avoid enormous network payloads Total size was 5,271 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.7 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 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 15 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
Avoid an excessive DOM size 1,667 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 23 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 63 requests • 5,271 KB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
Minify JavaScript Potential savings of 23 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 4.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 62 requests • 5,245 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Use video formats for animated content Potential savings of 3,370 KB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Serve static assets with an efficient cache policy 55 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 420 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 5.0 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
Estimated Input Latency 60 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
First Contentful Paint (3G) 4428 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are not sized appropriately 78% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 98.2% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused CSS Potential savings of 76 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 260 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
Server response times are low (TTFB) Root document took 110 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 110 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 300 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 99 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 1,787 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.7 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).
Avoid enormous network payloads Total size was 5,245 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 2.3 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 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 14 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
Avoid an excessive DOM size 1,675 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)

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

0

Local Rank: / Users: / PageViews:

484,772

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
Date: Thu, 05 Mar 2020 19:11:07 GMT
Server: Apache
Cache-Control: must-revalidate, no-cache, private
X-Drupal-Dynamic-Cache: UNCACHEABLE
Link: ; rel="shortlink", ; rel="canonical"
Link: ; rel="alternate"; hreflang="es"
Link: ; rel="alternate"; hreflang="gl"
Link: ; rel="alternate"; hreflang="en"
Link: ; rel="revision"
X-UA-Compatible: IE=edge
Content-language: gl
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Vary:
X-Generator: Drupal 8 (https://www.drupal.org)
X-Drupal-Cache: HIT
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records