Your Website Score is

Similar Ranking

14
ЯНДЕКС
yandex.ru
14
MAIL.RU: ПОЧТА, ПОИСК В ИНТЕРНЕТЕ, НОВОСТИ, ИГРЫ
mail.ru
14
MEDIUM – A PLACE TO READ AND WRITE BIG IDEAS AND IMPORTANT STORIES
medium.com
14
您查看的页面找不到了!-理想生活上天猫
detail.tmall.com
14
VIDEO CONFERENCING, WEB CONFERENCING, WEBINARS, SCREEN SHARING - ZOOM
zoom.us
14
INSTRUCTURE | LMS & EMPLOYEE DEVELOPMENT SOLUTION
instructure.com
14
凤凰网
ifeng.com

Latest Sites

19
SIEMENS | MINDSPHERE
mindsphere.io
2
官網
hocom.tw
2
APACHE2 UBUNTU DEFAULT PAGE: IT WORKS
yildiz.tv
31
HOME | RAINFOREST ALLIANCE
rainforest-alliance.org
19
AKBANK
akbank.com.tr
39
UNI KIEL: CHRISTIAN-ALBRECHTS-UNIVERSITÄT ZU KIEL
uni-kiel.de
31
SHIVARWEB: DIYER'S GUIDE TO BETTER WEBSITES & MARKETING
shivarweb.com

Top Technologies

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

14 uwo.ca Last Updated: 3 months

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

Desktop

Mobile

Performance Desktop Score 93%
Best Practices Desktop Score 69%
SEO Desktop Score 100%
Progressive Web App Desktop Score 58%
Performance Mobile Score 58%
Best Practices Mobile Score 69%
SEO Mobile Score 98%
Progressive Web App Mobile Score 59%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 25 Characters
WESTERN UNIVERSITY
Meta Description 272 Characters
Western University delivers an academic experience second to none. Western challenges the best and brightest faculty, staff and students to commit to the highest global standards. Our research excellence expands knowledge and drives discovery with real-world application.
Effective URL 18 Characters
Excerpt Page content
Western University Skip to Content Future Students | Current Students | Faculty / Staff | International | Community | Alumni | Media | Give F...
Keywords Cloud Density
western15 faculty13 campus12 studies9 students9 programs9 academics7 life7 graduate7 student6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
western 15
faculty 13
campus 12
studies 9
students 9
programs 9
academics 7
life 7
graduate 7
student 6
Google Preview Your look like this in google search result
WESTERN UNIVERSITY
https://www.uwo.ca
Western University delivers an academic experience second to none. Western challenges the best and brightest faculty, staff and students to commit to
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: 2019-01-24 / 1 year
Create on: 2000-10-13 / 19 years
Expires on: 2020-01-12 / 0 months 13 days

Webnames.ca Inc. ,CA
Registrar Name: The University of Western Ontario
Registrar Whois Server: whois.ca.fury.ca
Registrar URL: www.webnames.ca
Registrar Phone: +1.5196612151
Registrar Email: dghantou@uwo.ca
Registrar Address: Support Services Building Rm 3312 , London

Dave Ghantous
Admin Organization: The University of Western Ontario
Admin Email: dghantou@uwo.ca
Admin Phone: +1.5196612151
Admin Address: Support Services Building Rm 3312, London

Nameservers
ns1.uwo.ca
ns2.uwo.ca
ns3.uwo.ca
Page Size Code & Text Ratio
Document Size: ~46.72 KB
Code Size: ~40.93 KB
Text Size: ~5.8 KB Ratio: 12.41%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

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
Remove unused CSS Potential savings of 80 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,209 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 590 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 200 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 379 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 561 KB
Optimized images load faster and consume less cellular data
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 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 1,578 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.6 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
Avoid enormous network payloads Total size was 4,186 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.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 0.9 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
Minimize Critical Requests Depth 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
Avoids an excessive DOM size 804 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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)
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 87 requests • 4,186 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 65 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
Minify CSS Potential savings of 15 KB
Minifying CSS files can reduce network payload sizes

Mobile

Mobile Screenshot
Total Blocking Time 250 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 72 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 1,092 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 4.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 6.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input
Avoid enormous network payloads Total size was 4,155 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.6 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.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 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize Critical Requests Depth 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
Avoids an excessive DOM size 805 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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)
First Meaningful Paint 3.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 82 requests • 4,155 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 60 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 7.8 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 20 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) 6435 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 15 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 89% 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 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
Remove unused CSS Potential savings of 82 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,219 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 580 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 870 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 561 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 379 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Third-Party Usage Third-party code blocked the main thread for 170 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Sat, 19 Oct 2019 04:46:24 GMT
Server: Apache/1.3.41 (Unix)
Last-Modified: Fri, 18 Oct 2019 07:00:08 GMT
ETag: "dc56ae0e-bad4-5da962f8"
Accept-Ranges: bytes
Content-Length: 47828
Content-Type: text/html
Set-Cookie: NSC_JQw6--xxx.vxp.db--443=ffffffffaf11921f45525d5f4f58455e445a4a42378b;path=/;secure
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments