Your Website Score is

Similar Ranking

33
ПОИСК ОБРАЗОВАТЕЛЬНЫХ ОРГАНИЗАЦИЙ
mskobr.ru
33
INDIARESULTS.COM
indiaresults.com
33
NOT FOUND
omnivox.ca
33
株式会社コムニコ | SNSマーケティングのエージェンシー
comnico.jp
33
CTWANT
ctwant.com
33
MP3TECA
mp3teca.com
33
ERROR: THE REQUESTED URL COULD NOT BE RETRIEVED
synchronycredit.com

Latest Sites

24
THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ
noithatmanhhe.vn
19
SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP
nhacanhothongminh.com
16
CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM
crypto-mining.biz
57
99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING
999dice.com
19
RELANDICE BOT FOR 999DICE
relandice.com
23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn
51
ONE MORE STEP
seeking.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

33 whu.edu.cn Last Updated: 9 months

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

Desktop

Mobile

Performance Desktop Score 74%
Best Practices Desktop Score 85%
SEO Desktop Score 78%
Progressive Web App Desktop Score 46%
Performance Mobile Score 100%
Best Practices Mobile Score 100%
SEO Mobile Score 91%
Progressive Web App Mobile Score 52%
Page Authority Authority 56%
Domain Authority Domain Authority 54%
Moz Rank 5.6/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 8 Characters
武汉大学邮件系统
Meta Description 0 Characters
NO DATA
Effective URL 37 Characters
https://whu.edu.cn/coremail/index.jsp
Excerpt Page content
武汉大学邮件系统 邮件系统 邮件服务器 企业邮箱 企业邮箱
Keywords Cloud Density
企业邮箱2 邮件系统1 邮件服务器1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
企业邮箱 2
邮件系统 1
邮件服务器 1
Google Preview Your look like this in google search result
武汉大学邮件系统
https://whu.edu.cn/coremail/index.jsp
武汉大学邮件系统 邮件系统 邮件服务器 企业邮箱 企业邮箱
Robots.txt File No Found
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~24.01 KB
Code Size: ~9.32 KB
Text Size: ~14.69 KB Ratio: 61.19%

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
Serve static assets with an efficient cache policy 12 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 530 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 50 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
Serve images in next-gen formats Potential savings of 1,415 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,270 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 240 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 1,166 KB
Optimized images load faster and consume less cellular data
Total Blocking Time 440 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.7 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
Speed Index 4.5 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).
Avoids enormous network payloads Total size was 2,016 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.0 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
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 146 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)
Preload key requests Potential savings of 230 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 17 requests • 2,016 KB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
Avoid chaining critical requests 1 chain 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 33 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)
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 7 requests • 15 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets 2 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 20 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
First Contentful Paint (3G) 2520 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
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
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
Avoid multiple page redirects Potential savings of 960 ms
Redirects introduce additional delays before the page can be loaded
Server response times are low (TTFB) Root document took 260 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
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.0 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
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.3 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 15 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.1 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.3 s
First Contentful Paint marks the time at which the first text or image is painted

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
Server: nginx
Date: Thu, 02 Jan 2020 00:01:08 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Protected-By: OpenRASP
X-Request-ID: c340f39a60764f1d972b3277f248c7c8
Pragma: No-cache
Cache-Control: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Language: zh-CN
x-frame-options:: SAMEORIGIN
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome