Your Website Score is

Similar Ranking

93
GOOGLE
google.com
93
OUTLOOK – FREE PERSONAL EMAIL AND CALENDAR FROM MICROSOFT
live.com
93
SEND MONEY, PAY ONLINE OR SET UP A MERCHANT ACCOUNT - PAYPAL CA
paypal.com
93
WHO | WORLD HEALTH ORGANIZATION
who.int
93
GOOGLE DEVELOPERS
developers.google.com
93
BBC - HOMEPAGE
bbc.com
93
NEWS, SPORT AND OPINION FROM THE GUARDIAN'S GLOBAL EDITION | THE GUARDIAN
theguardian.com

Latest Sites

3
-
musicbigpedia.com
3
MUSIC-PEDIA - LISTEN WORLDWIDE MUSIC ONLINE FREE STREAMING
music-pedia.com
22
TERBITFILM - FREE WATCH FULL MOVIES HD ONLINE
terbitfilm.com
19
XXIKU - WATCH FULL MOVIES HD ONLINE FREE
xxiku.com
4
-
liveamor.com
19
ASEP MEDIA BLOGGER
aseprohimatea.online
19
TECHSUKHEN - FOR YOUR SOLUTION
techsukhen.com

Top Technologies

PHP
Programming Languages
Google Font API
Font Scripts
WordPress
CMS
CloudFlare
CDN
jQuery
JavaScript Frameworks
Nginx
Web Servers
Font Awesome
Font Scripts
Google Tag Manager
Tag Managers
Apache
Web Servers
LiteSpeed
Web Servers

93 who.int Last Updated: 1 year

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

Desktop

Mobile

Performance Desktop Score 62%
Best Practices Desktop Score 71%
SEO Desktop Score 92%
Progressive Web App Desktop Score 26%
Performance Mobile Score 35%
Best Practices Mobile Score 71%
SEO Mobile Score 93%
Progressive Web App Mobile Score 29%
Page Authority Authority 75%
Domain Authority Domain Authority 95%
Moz Rank 7.5/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
covid15 health14 disease11 news8 september8 world7 coronavirus7 data7 credits6 dashboard6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
covid 15
health 14
disease 11
news 8
september 8
world 7
coronavirus 7
data 7
credits 6
dashboard 6
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 / 5 years
Create on: 1998-06-05 / 24 years
Expires on: 1970-01-01 / 633 months 28 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: ~109.84 KB
Code Size: ~68.62 KB
Text Size: ~41.22 KB Ratio: 37.53%

Social Data

Delicious Total: 0
Facebook Total: 575,486
Google Total: 0
Linkedin Total: 0
Pinterest Total: 2,198
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Estimation Traffic and Earnings

63,929
Unique Visits
Daily
118,268
Pages Views
Daily
$114
Income
Daily
1,790,012
Unique Visits
Monthly
3,370,638
Pages Views
Monthly
$2,850
Income
Monthly
20,712,996
Unique Visits
Yearly
39,738,048
Pages Views
Yearly
$30,096
Income
Yearly

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 66 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Total Blocking Time 470 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
User Timing marks and measures 6 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
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 CPU Idle 3.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/).
Max Potential First Input Delay 400 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Properly size images Potential savings of 99 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
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
Cumulative Layout Shift 0.031
Cumulative Layout Shift measures the movement of visible elements within the viewport
Estimated Input Latency 40 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
Minimize third-party usage Third-party code blocked the main thread for 160 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
Time to Interactive 3.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid enormous network payloads Total size was 3,881 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Links do not have descriptive text 3 links found
Descriptive link text helps search engines understand your content
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.8 s
A fast page load over a cellular network ensures a good mobile user experience
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 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
First Meaningful Paint 1.6 s
First Meaningful Paint measures when the primary content of a page is visible
Initial server response time was short Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid chaining critical requests 23 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
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint 2.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Serve images in next-gen formats Potential savings of 1,099 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
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Keep request counts low and transfer sizes small 111 requests • 3,881 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Remove unused CSS Potential savings of 128 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
Remove unused JavaScript Potential savings of 719 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
Avoid an excessive DOM size 2,300 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
Time to Interactive 14.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Minimize main-thread work 7.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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 4.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint (3G) 5444.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Total Blocking Time 2,130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused CSS Potential savings of 131 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
Eliminate render-blocking resources Potential savings of 1,320 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Links do not have descriptive text 3 links found
Descriptive link text helps search engines understand your content
Page load is not fast enough on mobile networks Interactive at 14.5 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid long main-thread tasks 15 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve images in next-gen formats Potential savings of 1,073 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
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
Remove unused JavaScript Potential savings of 736 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid an excessive DOM size 2,300 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)
User Timing marks and measures 6 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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
First Meaningful Paint 2.8 s
First Meaningful Paint measures when the primary content of a page is visible
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
Reduce JavaScript execution time 4.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Estimated Input Latency 760 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 23 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
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
Cumulative Layout Shift 0.119
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid enormous network payloads Total size was 3,763 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy 63 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 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
Speed Index 5.7 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Max Potential First Input Delay 1,430 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Reduce the impact of third-party code Third-party code blocked the main thread for 1,100 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
Keep request counts low and transfer sizes small 108 requests • 3,763 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
First CPU Idle 14.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/).

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
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not 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
First 20 Links Relationship HTTP Status
https://www.who.int/ Internal Link 200
Africa Internal Link 200
South-East Asia Internal Link 302
Europe Internal Link 301
Eastern Mediterranean Internal Link 200
Western Pacific Internal Link 200
Home Internal Link 302
Health Topics Internal Link 302
All topics » Internal Link 302
Resources » Internal Link 302
Fact sheets Internal Link 302
Facts in pictures Internal Link 302
Publications Internal Link 302
Questions & answers Internal Link 302
Popular » Internal Link 302
Coronavirus disease (COVID-19) Internal Link 302
Ebola virus disease Internal Link 302
Nutrition Internal Link 302
Hepatitis Internal Link 302
Top 10 causes of death Internal Link 302

Alexa Rank

587

Global Rank

495

India
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
who.co Available Buy Now!
who.us Available Buy Now!
who.com Available Buy Now!
who.org Available Buy Now!
who.net Available Buy Now!
wo.int Available Buy Now!
zho.int Available Buy Now!
sho.int Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/2 200 
content-type: text/html; charset=utf-8
last-modified: Tue, 15 Sep 2020 16:16:53 GMT
server: Microsoft-IIS/10.0
x-aspnet-version: 4.0.30319
x-powered-by: ASP.NET
access-control-allow-origin: *
content-encoding: gzip
date: Tue, 15 Sep 2020 19:37:20 GMT
cache-control: public, max-age=0, s-maxage=180
expires: Tue, 15 Sep 2020 19:37:11 GMT
etag: "1fa5fc69-d6ff-46a9-a080-2f5fa1b82371"
x-cache: Hit from cloudfront
via: 1.1 a06e85a5c7853d2f85565a048a9d2609.cloudfront.net (CloudFront)
x-amz-cf-pop: YTO50-C3
x-amz-cf-id: dFlC_LE8zVGGicKeIow_P_humO5MJNiXMHp-hahZajM3ZGQ2LdOVEQ==
age: 952
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 72201
NS who.int ns1.wpro.who.int IN 86400
NS who.int ext-dns-2.cern.ch IN 86400
NS who.int whqdns3.who.int IN 86400
NS who.int whqdns1.who.int IN 86400
NS who.int whqdns2.who.int IN 86400
MX who.int mx10.who.int IN 86400
MX who.int mx5.who.int IN 86400
TXT who.int ciscocidomainverification=17f32bae2ea200dbca5879cd0dc89294b7e78220da17554d099fed05e3f7e8f4 IN 3600
TXT who.int MS=ms38766037 IN 3600
TXT who.int ca3-5fc9c6c655cf481e9d53b30866a6e690 IN 3600
TXT who.int kfjFGux2GvIgH+XwWJgA8YLNiX6Jc9lZEtHz+2cfDoLo4cB03zeofnNz9eioELQriSHy0S6EuDQyrFY6DuoFqA== IN 3600
TXT who.int ZOOM_verify_bTI318yfSumXtVIVnfEdzQ IN 3600
TXT who.int docusign=c346709c-41f2-43fd-8a5a-cf7992d6e560 IN 3600
TXT who.int v=spf1 ip4:158.232.12.0/24 include:spf.protection.outlook.com include:_spfincludes.who.int -all IN 3600
TXT who.int apple-domain-verification=cYOp0B6FuXeoDFAX IN 3600
TXT who.int docusign=9f72d1bd-efd7-4a97-b385-83d687978e8d IN 3600

Comments

About Us

AllSEOPart is a Website Review, SEO, Estimation Traffic and Earnings And Speed And Optimization Tips. Best choice web service free for Website Owners, Webmasters and General Internet Users to retrieve information regarding Domain Names, Google PageSpeed, Page Authority, Moz Rank, Keyword & Meta Info, Alexa Info, Response Header, Technologiess analyze, Google Preview, Whois, Domain Create Date, Domain Age, Domain Expiry Date, Domain Authority, Keywords Cloud, Keyword Consistency, Real URL, Broken Link Checker, Accelerated Mobile Pages (AMP) Checker, DNS Record, Name Server, IP Server, Bounce Rate, Estimation Traffic with Earnings, Traffic Statistics, Alexa Rank Map, Website score and Search Engine Optimization (SEO). Just type your Domain Name at the top to get amazing reports.

Contact Info

ALLSEOPART Group
Tusam Hill District
Kutacane, Southeast Aceh
+6282273598787
cs{@}allseopart.com

Follow Us

Twitter
Facebook
Google Plus
Linkedin
Instagram
Copyright © 2020 - 2022 ALLSEOPART.COM - All Rights Reserved.
Languages | English