Your Website Score is

Similar Ranking

69
UNIVERSITÉ DE LA RÉUNION - UNIVERSITÉ DE LA RÉUNION
univ-reunion.fr
68
STRONA GŁÓWNA UMCS
umcs.pl
63
UNIWERSYTET ŁÓDZKI
uni.lodz.pl
62
CANTERBURY CHRIST CHURCH UNIVERSITY
canterbury.ac.uk
62
SCHOOL OF ADVANCED STUDY
sas.ac.uk
61
ROSKILDE UNIVERSITET
ruc.dk
61
UNIVERSITÉ DU LITTORAL CÔTE D'OPALE – ULCO
univ-littoral.fr

69 univ-reunion.fr Last Updated: 4 weeks

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

Desktop

Mobile

Performance Desktop Score 82%
Best Practices Desktop Score 85%
SEO Desktop Score 100%
Progressive Web App Desktop Score 69%
Performance Mobile Score 79%
Best Practices Mobile Score 77%
SEO Mobile Score 98%
Progressive Web App Mobile Score 70%
Page Authority Authority 45%
Domain Authority Domain Authority 55%
Moz Rank 4.5/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 61 Characters
UNIVERSITÉ DE LA RÉUNION - UNIVERSITÉ DE LA RÉUNION
Meta Description 24 Characters
Université de La Réunion
Effective URL 27 Characters
https://www.univ-reunion.fr
Excerpt Page content
Université de La Réunion - Université de La Réunion ...
Keywords Cloud Density
mars10 site9 moufia8 université7 recherche7 événement6 santé5 sciences4 formation4 services3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
mars 10
site 9
moufia 8
université 7
recherche 7
événement 6
santé 5
sciences 4
formation 4
services 3
Google Preview Your look like this in google search result
UNIVERSITÉ DE LA RÉUNION - UNIVERSITÉ DE LA RÉUNIO
https://www.univ-reunion.fr
Université de La Réunion
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~42.25 KB
Code Size: ~31.51 KB
Text Size: ~10.74 KB Ratio: 25.42%

Estimation Traffic and Earnings

840
Unique Visits
Daily
1,554
Pages Views
Daily
$4
Income
Daily
23,520
Unique Visits
Monthly
44,289
Pages Views
Monthly
$100
Income
Monthly
272,160
Unique Visits
Yearly
522,144
Pages Views
Yearly
$1,056
Income
Yearly

Desktop

Desktop Screenshot
Reduce server response times (TTFB) Root document took 1,310 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 180 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 45 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.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
Properly size images Potential savings of 526 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 0.9 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 1,315 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.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 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 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 8 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 484 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 43 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 42 requests • 1,315 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 40 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 0.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
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 59 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 451 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

Mobile

Mobile Screenshot
Total Blocking Time 80 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.4 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
Properly size images Potential savings of 423 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 5.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.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).
Avoids enormous network payloads Total size was 1,313 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.4 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.4 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 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 8 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 484 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 43 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 4.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 41 requests • 1,313 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 39 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 4.2 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
First Contentful Paint (3G) 2790 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 77% 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 95.1% 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 59 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 451 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
Reduce server response times (TTFB) Root document took 1,290 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 550 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 45 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

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
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not 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

Local Rank: O / Users: 81.1% / PageViews: 75.6%

183,986

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:23:03 GMT
Server: Apache/2.4.25 (Debian)
Content-Language: fr
Cache-Control: private, no-store
Content-Length: 43146
Content-Type: text/html; charset=utf-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records