Your Website Score is

Similar Ranking

54
LOWE'S HOME IMPROVEMENT
lowes.com
54
RADIO--- ASIA
rfa.org
54
NAIRALAND FORUM
nairaland.com
54
RENT THE RUNWAY | RENT UNLIMITED DESIGNER CLOTHING, DRESSES, ACCESSORIES
renttherunway.com
54
BACKSTAGE | AUDITIONS, CASTING CALLS, JOBS, TALENT SEEKING, ADVICE
backstage.com
54
BROWSE SAFELY AND STEER CLEAR OF ONLINE DANGERS | MCAFEE WEBADVISOR
siteadvisor.com
54
NICHE: EXPLORE SCHOOLS, COMPANIES, AND NEIGHBORHOODS
niche.com

Latest Sites

40
İSTANBUL SPOR ENVANTERI | İBB DIRECTORATE OF YOUTH AND SPORTS
sporenvanteri.ibb.istanbul
19
FREEMINING - START--- BITCOIN CLOUD MINING & EARN--- BTC EVERY HOUR
freemining.club
19
MININGCOMPANY.LTD - CLOUD MINING FARMA
miningcompany.ltd
26
NACIONAL MONTE DE PIEDAD
montepiedad.com.mx
19
PINOY MOVIES - WATCH PINOY MOVIES ONLINE---
cineko.to
14
FINYA LIMITED
finyalimited.com
14
CADOCINVESTMENT.COM | AUSTRALIAN INVESTMENT COMPANY
cadocinvestment.com

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

54 umontreal.ca Last Updated: 7 months

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

Desktop

Mobile

Performance Mobile Score 22%
Best Practices Mobile Score 77%
SEO Mobile Score 80%
Progressive Web App Mobile Score 30%
Page Authority Authority 56%
Domain Authority Domain Authority 79%
Moz Rank 5.6/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 22 Characters
UNIVERSITÉ DE MONTRÉAL
Meta Description 0 Characters
NO DATA
Effective URL 24 Characters
https://www.umontreal.ca
Excerpt Page content
Université de Montréal Passer au contenuUniversité de Montréal Menu Rechercher Fermer la recherche Liens rapides ...
Google Preview Your look like this in google search result
UNIVERSITÉ DE MONTRÉAL
https://www.umontreal.ca
Université de Montréal Passer au contenuUniversité de Montréal Menu Rechercher Fermer la recherche Liens rapides ...
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: 2016-12-09 / 4 years
Create on: 2000-10-30 / 20 years
Expires on: 2022-03-21 / 15 months 24 days

Réseau Internet Québec Inc. ,CA
Registrar Name: Université de Montréal
Registrar Whois Server: whois.ca.fury.ca
Registrar URL: https://portail.riq.qc.ca/
Registrar Phone: +1.5143436111
Registrar Email: [email protected]
Registrar Address: 2900, boul Édouard-Montpetit , Montréal

Jude Baril
Admin Organization: Université de Montréal
Admin Email: [email protected]
Admin Phone: +1.5143436111
Admin Address: 2900 blv Edouard Montpetit, Montreal

Nameservers
dnsp1.dit.umontreal.ca
dnsp2.dit.umontreal.ca
ns1.risq.qc.ca
ns2.risq.qc.ca
Page Size Code & Text Ratio
Document Size: ~31.75 KB
Code Size: ~27 KB
Text Size: ~4.76 KB Ratio: 14.98%

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

Mobile

Mobile Screenshot
Server response times are low (TTFB) Root document took 40 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 3,300 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 2,493 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 596 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 30 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 920 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 3.8 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 4,327 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,038 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 10.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.0 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 8,406 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 6.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.6 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 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 27 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,023 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 4.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 106 requests • 8,406 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 74 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 970 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 38.1 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 38.1 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 390 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) 9615 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minify CSS Potential savings of 23 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 65% 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 92.98% 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 407 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 1,393 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
Date: Wed, 22 Apr 2020 07:26:50 GMT
Expires: Wed, 22 Apr 2020 08:26:50 GMT
Cache-Control: max-age=3600
Pragma: public
Vary: Host,Accept-Encoding
ETag: "c41b5395073731686650455cc2f6f213-gzip"
Content-Encoding: gzip
Content-Length: 12371
Content-Type: text/html; charset=utf-8
X-Server-By: web4
Age: 194
grace: none
X-Cache: HIT
Accept-Ranges: bytes
Connection: keep-alive
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome