Your Website Score is

Similar Ranking

9
YOUTUBE
youtube.com
9
COVID-19 TESTING, COVID-19 SCREENING, THIRD PARTY ADMINISTRATOR (TPA), MANAGED CARE ORGANIZ
aspmedic.com

Latest Sites

31
JUMIA KENYA | ONLINE SHOPPING FOR GROCERIES, CLEANING SUPPLIES, HOME ESSENTIALS & MORE
jumia.co.ke
11
RÉPONSES ICI
askfrance.me
19
LIBRI UNITO · VENDI E COMPRA LIBRI USATI PER L'UNIVERSITÀ DI TORINO
libriunito.it
2
TRADUTOR DE DOCUMENTOS BRASILEIROS NOS ESTADOS UNIDOS
tradutorbrasileironosestadosunidos.com
29
TRADUTOR BRASILEIRO 877 297 4998
tradutorbrasileiro.com
14
TRADITIONALRIGHT – TRADITIONALISM IN A CHANGING WORLD.
traditionalright.com

Top Technologies

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

9 unodc.org Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 56%
Best Practices Desktop Score 79%
SEO Desktop Score 91%
Progressive Web App Desktop Score 30%
Performance Mobile Score 21%
Best Practices Mobile Score 79%
SEO Mobile Score 91%
Progressive Web App Mobile Score 32%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 16 Characters
http://unodc.org
Google Preview Your look like this in google search result
unodc.org
http://unodc.org
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~1 B
Code Size: ~NAN B
Text Size: ~1 B Ratio: 100.00%

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

Desktop

Desktop Screenshot
Avoid an excessive DOM size 1,383 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)
Does not use HTTPS 32 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Enable text compression Potential savings of 459 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Serve static assets with an efficient cache policy 35 resources found
A long cache lifetime can speed up repeat visits to your page
Keep request counts low and transfer sizes small 153 requests • 12,418 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint 1.7 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 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid enormous network payloads Total size was 12,418 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify JavaScript Potential savings of 41 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 21.2 s
A fast page load over a cellular network ensures a good mobile user experience
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 1,634 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.015
Cumulative Layout Shift measures the movement of visible elements within the viewport
Initial server response time was short Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources Potential savings of 1,870 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Minimize third-party usage Third-party code blocked the main thread for 140 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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.8 s
First Meaningful Paint measures when the primary content of a page is visible
User Timing marks and measures 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Serve images in next-gen formats Potential savings of 8,042 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
Largest Contentful Paint 5.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused CSS Potential savings of 86 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
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
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
Remove unused JavaScript Potential savings of 617 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.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/).
Replace unnecessarily large JavaScript libraries 1 large library found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Time to Interactive 4.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Efficiently encode images Potential savings of 376 KiB
Optimized images load faster and consume less cellular data
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
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

Mobile

Mobile Screenshot
First CPU Idle 16.9 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/).
Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize main-thread work 4.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks 12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Largest Contentful Paint 25.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Defer offscreen images Potential savings of 167 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid an excessive DOM size 1,383 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)
Eliminate render-blocking resources Potential savings of 6,750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve images in next-gen formats Potential savings of 8,150 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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 Contentful Paint 7.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid multiple page redirects Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded
Avoid enormous network payloads Total size was 12,964 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint (3G) 15212 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Replace unnecessarily large JavaScript libraries 1 large library found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Initial server response time was short Root document took 220 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce the impact of third-party code Third-party code blocked the main thread for 960 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
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
Minify JavaScript Potential savings of 41 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Efficiently encode images Potential savings of 376 KiB
Optimized images load faster and consume less cellular data
Keep request counts low and transfer sizes small 153 requests • 12,964 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Does not use HTTPS 33 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Serve static assets with an efficient cache policy 35 resources found
A long cache lifetime can speed up repeat visits to your page
User Timing marks and measures 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Tap targets are not sized appropriately 96% 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
Max Potential First Input Delay 270 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Time to Interactive 23.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Properly size images Potential savings of 711 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Remove unused CSS Potential savings of 86 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 626 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce JavaScript execution time 2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.021
Cumulative Layout Shift measures the movement of visible elements within the viewport
Total Blocking Time 590 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First Meaningful Paint 7.6 s
First Meaningful Paint measures when the primary content of a page is visible
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
Page load is not fast enough on mobile networks Interactive at 23.4 s
A fast page load over a cellular network ensures a good mobile user experience
Speed Index 9.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Estimated Input Latency 120 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
Enable text compression Potential savings of 459 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

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


						
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments