Urb.ae Site Title
Home - URB
Urb.ae Test Results
Urb.ae Mobile Performance: 63/100
Quick overview:
First Meaningful Paint
3.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
5.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Properly size images
Potential savings of 73 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve images in next-gen formats
Potential savings of 58 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Reduce unused JavaScript
Potential savings of 66 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Reduce unused CSS
Potential savings of 40 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Eliminate render-blocking resources
Potential savings of 1,750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Largest Contentful Paint element
7,060 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
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. Learn how to use modern JavaScript
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Urb.ae Mobile SEO: 100/100
Quick overview:
Urb.ae Mobile Best Practices: 79/100
Quick overview:
User Experience
Document doesn't use legible font sizes
47.61% 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. Learn more about legible font sizes.
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over 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. Learn more about HTTPS.
Urb.ae Mobile Accessibility: 94/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Skip links are not focusable.
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
Similar sites
Similar tests
www.urb.com
www.urb.net
www.urb.org
www.urb.info
www.urb.biz
www.urb.us
www.urb.mobi
www.rb.ae
www.urb.ae
www.yrb.ae
www.uyrb.ae
www.yurb.ae
www.hrb.ae
www.uhrb.ae
www.hurb.ae
www.jrb.ae
www.ujrb.ae
www.jurb.ae
www.irb.ae
www.uirb.ae
www.iurb.ae
www.ub.ae
www.ueb.ae
www.ureb.ae
www.uerb.ae
www.udb.ae
www.urdb.ae
www.udrb.ae
www.ufb.ae
www.urfb.ae
www.ufrb.ae
www.utb.ae
www.urtb.ae
www.utrb.ae
www.ur.ae
www.urv.ae
www.urbv.ae
www.urvb.ae
www.urg.ae
www.urbg.ae
www.urgb.ae
www.urh.ae
www.urbh.ae
www.urhb.ae
www.urn.ae
www.urbn.ae
www.urnb.ae
www.urb.net
www.urb.org
www.urb.info
www.urb.biz
www.urb.us
www.urb.mobi
www.rb.ae
www.urb.ae
www.yrb.ae
www.uyrb.ae
www.yurb.ae
www.hrb.ae
www.uhrb.ae
www.hurb.ae
www.jrb.ae
www.ujrb.ae
www.jurb.ae
www.irb.ae
www.uirb.ae
www.iurb.ae
www.ub.ae
www.ueb.ae
www.ureb.ae
www.uerb.ae
www.udb.ae
www.urdb.ae
www.udrb.ae
www.ufb.ae
www.urfb.ae
www.ufrb.ae
www.utb.ae
www.urtb.ae
www.utrb.ae
www.ur.ae
www.urv.ae
www.urbv.ae
www.urvb.ae
www.urg.ae
www.urbg.ae
www.urgb.ae
www.urh.ae
www.urbh.ae
www.urhb.ae
www.urn.ae
www.urbn.ae
www.urnb.ae