Un.org Welcome to the United Nations
un.org Mobile Performance
54/100
These metrics represent real-world Chrome users experience viewing un.org on mobile devices. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
First Contentful Paint
First Input Delay
Cumulative Layout Shift
Largest Contentful Paint
Metrics
Largest Contentful Paint0/100 10.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Speed Index25/100 7.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First Contentful Paint50/100 4.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive85/100 4.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time100/100 60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift100/100 0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (13)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 845 KiB
4,200 ms
Efficiently encode images
Potential savings of 518 KiB
2,550 ms
Avoid multiple page redirects
Potential savings of 1,740 ms
1,740 ms
Eliminate render-blocking resources
Potential savings of 870 ms
870 ms
Remove unused JavaScript
Potential savings of 21 KiB
290 ms
Remove unused CSS
Potential savings of 22 KiB
150 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
8 resources found
Minimize main-thread work
2.3 s
Keep request counts low and transfer sizes small
26 requests • 6,625 KiB
Largest Contentful Paint element
1 element found
Avoid chaining critical requests
12 chains found
Avoid long main-thread tasks
5 long tasks found
Passed Audits (15)
JavaScript execution time
0.3 s
Avoids an excessive DOM size
107 elements
Use video formats for animated content
Avoids `document.write()`
Preconnect to required origins
Uses passive listeners to improve scrolling performance
Properly size images
Initial server response time was short
Root document took 370 ms
Avoids enormous network payloads
Total size was 1,248 KiB
Defer offscreen images
Preload key requests
Minify JavaScript
Minimize third-party usage
Third-party code blocked the main thread for 110 ms
Enable text compression
Potential savings of 4 KiB
Minify CSS
un.org Mobile SEO
92/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (1)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Passed Audits (12)
Page has successful HTTP status code
Document uses legible font sizes
100% legible text
Tap targets are sized appropriately
100% appropriately sized tap targets
robots.txt is valid
Links are crawlable
Document has a `<title>` element
Page isn’t blocked from indexing
Document avoids plugins
Document has a valid `hreflang`
Image elements have `[alt]` attributes
Links have descriptive text
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
un.org Mobile Best Practices
69/100
These checks highlight opportunities to improve the overall code health of un.org mobile page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
User Experience
Serves images with low resolution
Trust and Safety
Does not use HTTPS
2 insecure requests found
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Passed Audits (10)
Allows users to paste into password fields
Avoids requesting the notification permission on page load
Avoids requesting the geolocation permission on page load
Displays images with correct aspect ratio
Links to cross-origin destinations are safe
Avoids deprecated APIs
Avoids Application Cache
Detected JavaScript libraries
Properly defines charset
No browser errors logged to the console
un.org Mobile Progressive Web App
46/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (9)
Fast and reliable
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
PWA Optimized
Is not configured for a custom splash screen
Does not provide a valid `apple-touch-icon`
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Installable
Web app manifest does not meet the installability requirements
Does not use HTTPS
2 insecure requests found
Does not register a service worker that controls page and `start_url`
Passed Audits (5)
Page load is fast enough on mobile networks
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
Content is sized correctly for the viewport
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
un.org Mobile Accessibility
90/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (3)
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Navigation
These are opportunities to improve keyboard navigation in your application.
The page does not contain a heading, skip link, or landmark region
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
Passed Audits (12)
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-hidden="true"]` elements do not contain focusable descendents
Background and foreground colors have a sufficient contrast ratio
`<video>` elements contain a `<track>` element with `[kind="description"]`
`[lang]` attributes have a valid value
Buttons have an accessible name
Document has a `<title>` element
`<video>` elements contain a `<track>` element with `[kind="captions"]`
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[aria-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
Links have a discernible name
Mobile Usability
100/100
These checks validate how easily a visitor can use un.org on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Passed Audits (5)
Avoid plugins
Configure the viewport
Size content to viewport
Size tap targets appropriately
Use legible font sizes
Mobile Speed
64/100
These checks analyze the performance of un.org on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (6)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Optimize images
Leverage browser caching
Enable compression
Minify JavaScript
Minify CSS
Passed Audits (4)
Avoid landing page redirects
Reduce server response time
Minify HTML
Prioritize visible content
www.un.com
www.un.net
www.un.org
www.un.info
www.un.biz
www.un.us
www.un.mobi
www.n.org
www.un.org
www.yn.org
www.uyn.org
www.yun.org
www.hn.org
www.uhn.org
www.hun.org
www.jn.org
www.ujn.org
www.jun.org
www.in.org
www.uin.org
www.iun.org
www.u.org
www.ub.org
www.unb.org
www.ubn.org
www.uh.org
www.unh.org
www.uj.org
www.unj.org
www.um.org
www.unm.org
www.umn.org
www.un.net
www.un.org
www.un.info
www.un.biz
www.un.us
www.un.mobi
www.n.org
www.un.org
www.yn.org
www.uyn.org
www.yun.org
www.hn.org
www.uhn.org
www.hun.org
www.jn.org
www.ujn.org
www.jun.org
www.in.org
www.uin.org
www.iun.org
www.u.org
www.ub.org
www.unb.org
www.ubn.org
www.uh.org
www.unh.org
www.uj.org
www.unj.org
www.um.org
www.unm.org
www.umn.org