Who.int - SEO Checker - Website Review

Your Website Score is

Similar Ranking

카카오

kakao.com

NEWS.COM.AU — AUSTRALIA’S #1 NEWS SITE

news.com.au

INÍCIO - INEP

inep.gov.br

CENTERS FOR DISEASE CONTROL AND PREVENTION

cdc.gov

LIVE, BREAKING NEWS TODAY: LATEST NATIONAL HEADLINES, WORLD NEWS AND MORE FROM CBSNEWS.COM AND WATCH THE CBSN LIVE NEWS STREAM 24X7

cbsnews.com

NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION | U.S. DEPARTMENT OF COMMERCE

noaa.gov

STOCK MARKETS, BUSINESS NEWS, FINANCIALS, EARNINGS - CNBC

cnbc.com

Latest Sites

WELCOME

rootpure.com

i72tq6h2fsoku1o5.onion

MONTHJOB - GET PAID FOR SUBSCRIPTIONS WITH FREE NEWSLETTERS

monthjob.com

eurobux.biz

OFFICIAL SITE - ZAAPTV - MAAXTV - ARAABTV - AUSTRALIA & N.Z

globetv.com.au

GIFTS AUSTRALIA WILL HELP TO FIND THE BEST GIFT QUICKLY FOR EVERY OCCASION!

giftsaustralia.com.au

FAN+ OFFERS FANS ACCESS TO EXTRAORDINARY EXPERIENCES

fanplus.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

91 who.int Last Updated: 2 years

Success 70% of passed verification steps

Warning 7% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 82%

Best Practices Desktop Score 69%

SEO Desktop Score 100%

Progressive Web App Desktop Score 27%

Performance Mobile Score 42%

Best Practices Mobile Score 62%

SEO Mobile Score 99%

Progressive Web App Mobile Score 30%

Page Authority Authority 68%

Domain Authority Domain Authority 93%

Moz Rank 6.8/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 36 Characters

WHO | WORLD HEALTH ORGANIZATION

Meta Description 143 Characters

WHO's primary role is to direct international health within the United Nations' system and to lead partners in global health responses.

Effective URL 19 Characters

https://www.who.int

Excerpt Page content

WHO | World Health Organization ...

Meta Keywords 15 Detected

World Health Organization health health for all #HealthForAll health organization universal health coverage disease UHC WHO health emergencies health data health policy advocacy health issues health news

Keywords Cloud Density

health13 news6 disease6 credits5 world5 global4 virus4 ebola4 emergencies4 general4

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
health	13
news	6
disease	6
credits	5
world	5
global	4
virus	4
ebola	4
emergencies	4
general	4

Google Preview Your look like this in google search result

WHO | WORLD HEALTH ORGANIZATION

https://www.who.int

WHO's primary role is to direct international health within the United Nations' system and to lead partners in global health responses.

Robots.txt File Detected

http://who.int/robots.txt

Sitemap.xml File No Found

http://who.int/sitemap.xml

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: 2017-06-14 / 4 years

Create on: 1998-06-05 / 23 years

Expires on: 1970-01-01 / 628 months 4 days

WHO-IMT-ESS WHO-IMT-ESS

Nameservers

EXT-DNS-2.CERN.CH

192.91.245.85

NS1.WPRO.WHO.INT

123.176.64.11

WHQDNS1.WHO.INT

158.232.12.5

WHQDNS2.WHO.INT

158.232.12.6

WHQDNS3.WHO.INT

1.9.217.220

Page Size Code & Text Ratio

Document Size: ~80.6 KB

Code Size: ~55.36 KB

Text Size: ~25.25 KB Ratio: 31.32%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Total Blocking Time 400 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 1.3 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 93 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

Speed Index 1.5 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 3.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).

Avoid enormous network payloads Total size was 3,440 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 2.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.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 2 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 24 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 2,087 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 21 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 1.5 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 121 requests • 3,440 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 70 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 230 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 3.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 on simulated mobile network at 14.7 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 60 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 114 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 323 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

User Timing marks and measures 5 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Server response times are low (TTFB) Root document took 170 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 70 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 12 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Minimize third-party usage Third-party code blocked the main thread for 190 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

Mobile

User Timing marks and measures 5 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Server response times are low (TTFB) Root document took 20 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,100 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 12 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Reduce the impact of third-party code Third-party code blocked the main thread for 1,790 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 2,650 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 5.5 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 152 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 5.7 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 14.4 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 3,317 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 8.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 2.1 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 2 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 24 chains found

Avoid an excessive DOM size 2,087 elements

Minify JavaScript Potential savings of 21 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 2.3 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 119 requests • 3,317 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 69 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 990 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 14.6 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 14.6 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 460 ms

First Contentful Paint (3G) 4290 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 97% 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 98.88% 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 119 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 299 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

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
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Date: Tue, 26 Nov 2019 12:54:16 GMT
Cache-Control: public, max-age=0, s-maxage=180
Expires: Tue, 26 Nov 2019 12:54:16 GMT
Last-Modified: Tue, 26 Nov 2019 12:54:13 GMT
Server: Microsoft-IIS/10.0
X-AspNet-Version: 4.0.30319
Access-Control-Allow-Origin: *
Content-Encoding: gzip
Vary: Accept-Encoding
X-Cache: Hit from cloudfront
Via: 1.1 e8541cab93cd37ee5ef379270867e664.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: ORD52-C2
X-Amz-Cf-Id: 9Z8s2giixHc7HEWk1upRcL5Fm1jdu_vN8yZ7N1mh72vKN1fC3sC80A==
Age: 497

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	who.int	158.232.12.119	IN	7143
NS	who.int	ext-dns-2.cern.ch	IN	21599
NS	who.int	whqdns3.who.int	IN	21599
NS	who.int	whqdns2.who.int	IN	21599
NS	who.int	ns1.wpro.who.int	IN	21599
NS	who.int	whqdns1.who.int	IN	21599
MX	who.int	mx5.who.int	IN	21599
MX	who.int	mx10.who.int	IN	21599
TXT	who.int	kfjFGux2GvIgH+XwWJgA8YLNiX6Jc9lZEtHz+2cfDoLo4cB03zeofnNz9eioELQriSHy0S6EuDQyrFY6DuoFqA==	IN	3599
TXT	who.int	MS=ms38766037	IN	3599
TXT	who.int	ciscocidomainverification=17f32bae2ea200dbca5879cd0dc89294b7e78220da17554d099fed05e3f7e8f4	IN	3599
TXT	who.int	v=spf1 ip4:158.232.12.0/24 ip4:37.98.232.0/24 ip4:199.91.137.0/24 ip4:149.96.66.25 ip4:149.96.50.25 mx:mx5.who.int mx:mx10.who.int include:spf.protection.outlook.com ~all	IN	3599

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

91 who.int Last Updated: 2 years

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Amazon Cloudfront

Google Tag Manager

IIS

Microsoft ASP NET

React

Sitefinity

Windows Server

YouTube

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments