Your Website Score is

Similar Ranking

60
DISCONTINUE GPO
gpo.iitb.ac.in
60
PAGE NOT FOUND
prompts.neocities.org
60
LIFESTYLE NEWS TELUGU | FASHION & BEAUTY TIPS TELUGU | HEALTH NEWS TELUGU | జీవనశైలి వార్తలు | ఫ్యాషన్ మరియు మెడిసిన్ చిట్కాలు | ఆరోగ్యం వార్తలు తెలుగు - BOLDSKY TELUGU
telugu.boldsky.com
60
ZIMBRA WEB CLIENT SIGN IN
webmail.tradeindia.com
60
SEHAT NEGERIKU - PORTAL BERITA RESMI KEMENTERIAN KESEHATAN RI
sehatnegeriku.kemkes.go.id
60
LOGIN - CAS – CENTRAL AUTHENTICATION SERVICE
mail.univ-lorraine.fr
60
PLATE-FORME PÉDAGOGIQUE MOODLE ENGEES
engees-moodle.unistra.fr

Latest Sites

26
VIEW PRIVATE INSTAGRAM ACCOUNTS FOR FREE - UNPRIVATE INSTAGRAM
viewpriv.com
91
INSTAGRAM
instagram.com
26
DOWNLOAD VIDEO FROM INSTAGRAM ONLINE – INSTA VIDEO DOWNLOAD
instafinsta.com
12
trakop.com Website SEO Rank Analysis by SEOWebsiteRank.com
trakop.com
21
NUDISM AND NATURISM. FAMILY PHOTOS AND VIDEOS
ournakedbodies.net
28
SATTA MATKA | KALYAN MATKA RESULT | MATKA CHARTS | SATTA MATKA TIPS
sattamatkai.net

Top Technologies

Nginx.png
Nginx
Web Servers
Apache.png
Apache
Web Servers
CloudFlare.png
CloudFlare
CDN
Google%20Font%20API.png
Google Font API
Font Scripts
Font%20Awesome.png
Font Awesome
Font Scripts
WordPress.png
WordPress
CMS
Twitter%20Bootstrap.png
Twitter Bootstrap
Web Frameworks
Microsoft.png
Windows Server
Operating Systems

SEO Rank : 60 Website URL: mail.univ-lorraine.fr Last Updated: 1 month

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

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Desktop

Mobile

Performance Desktop Score 78%
Best Practices Desktop Score 86%
SEO Desktop Score 90%
Progressive Web App Desktop Score 26%
Performance Mobile Score 76%
Best Practices Mobile Score 86%
SEO Mobile Score 92%
Progressive Web App Mobile Score 29%

Moz Authority Rank

Page Authority Authority 44%
Domain Authority Domain Authority 68%
Moz Rank 4.4/10
Bounce Rate Rate 0%

Meta Data

Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 44 Characters
LOGIN - CAS – CENTRAL AUTHENTICATION SERVICE
Meta Description 0 Characters
NO DATA
Effective URL 119 Characters
https://auth.univ-lorraine.fr/login?service=https%3A%2F%2Fmail.univ-lorraine.fr%2Fzimbra%2Fpreauth%2FpreauthUL_PERS.jsp
Excerpt Page content
Login - CAS – Central Authentication Service Service d'authentification L'usage des ressources et services numériques de l'Université de Lorraine se fait dans le strict respect de la Cha...
Keywords Cloud Density
browser3 université2 services2 lorraine2 cookies2 service1 capslock1 enseigner1 travailler1 distance1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
browser 3
université 2
services 2
lorraine 2
cookies 2
service 1
capslock 1
enseigner 1
travailler 1
distance 1
Google Preview Your look like this in google search result
LOGIN - CAS – CENTRAL AUTHENTICATION SERVICE
https://auth.univ-lorraine.fr/login?service=https%3A%2F%2Fmail.univ-lorraine.fr%2Fzimbra%2Fpreauth%2FpreauthUL_PERS.jsp
Login - CAS – Central Authentication Service Service d'authentification L'usage des ressources et services numériques de l'Université de Lorraine se fait dans le strict respect de la Cha...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~11.72 KB
Code Size: ~8.89 KB
Text Size: ~2.83 KB Ratio: 24.16%

Social Data

Desktop

Desktop Screenshot
Avoids enormous network payloads Total size was 1,493 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
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
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
Properly size images Potential savings of 7 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Eliminate render-blocking resources Potential savings of 360 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Largest Contentful Paint 2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused JavaScript Potential savings of 324 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Preload key requests Potential savings of 110 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Total Blocking Time 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 18 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Enable text compression Potential savings of 766 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minimizes main-thread work 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small 19 requests • 1,493 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 10.4 s
A fast page load over a cellular network ensures a good mobile user experience
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce initial server response time Root document took 730 ms
Keep the server response time for the main document short because all other requests depend on it
First CPU Idle 1.8 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/).
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
Time to Interactive 2.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Serve images in next-gen formats Potential savings of 48 KiB
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
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Remove unused CSS Potential savings of 50 KiB
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
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids an excessive DOM size 60 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
First Meaningful Paint 2.0 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Speed Index 3.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
First Contentful Paint (3G) 4448 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Remove unused JavaScript Potential savings of 324 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Enable text compression Potential savings of 766 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted
Preload key requests Potential savings of 750 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Remove unused CSS Potential savings of 40 KiB
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
Time to Interactive 10.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Tap targets are sized appropriately 100% 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
Keep request counts low and transfer sizes small 19 requests • 1,493 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Cumulative Layout Shift 0.034
Cumulative Layout Shift measures the movement of visible elements within the viewport
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 large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
JavaScript execution time 0.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Total Blocking Time 410 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Estimated Input Latency 260 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 CPU Idle 4.1 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/).
Largest Contentful Paint 2.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids enormous network payloads Total size was 1,493 KiB
Large network payloads cost users real money and are highly correlated with long load times
Page load is not fast enough on mobile networks Interactive at 10.4 s
A fast page load over a cellular network ensures a good mobile user experience
Document uses legible font sizes 100% 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
Serve static assets with an efficient cache policy 18 resources found
A long cache lifetime can speed up repeat visits to your page
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
Initial server response time was short Root document took 590 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources Potential savings of 1,050 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids an excessive DOM size 60 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)
Max Potential First Input Delay 810 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve images in next-gen formats Potential savings of 48 KiB
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

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:

Global Rank

Domain Available

Domain (TDL) and Typo Status
mail.univ-lorraine.co Already Registered
mail.univ-lorraine.us Already Registered
mail.univ-lorraine.com Already Registered
mail.univ-lorraine.org Already Registered
mail.univ-lorraine.net Already Registered
mil.univ-lorraine.fr Already Registered
jail.univ-lorraine.fr Already Registered
iail.univ-lorraine.fr Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 
Strict-Transport-Security: max-age=15768000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
Pragma: no-cache
Content-Type: text/html;charset=UTF-8
Content-Language: fr-FR
Transfer-Encoding: chunked
Date: Wed, 20 Jan 2021 00:05:04 GMT
Connection: close
Set-Cookie: UL_CAS=leia; path=/

View DNS Records

DNS Records DNS Resource Records associated with a hostname
Type Name Value Class TTL

Comments

mail.univ-lorraine.fr Stats By Traffic Tips Alexa Server Meta Authority Technologies Pagespeed Pagespeed Stats Social Domain Available
Add extension to Chrome