Xr.global Site Title

XR: Revolutionizing Advertising with Unified Data at Scale

Xr.global Meta Description

Elevate your advertising strategy with XR's global technology platform. Simplifying the advertising ecosystem, we seamlessly deliver unified data at scale.

Xr.global Test Results

Xr.global Mobile Performance: 29/100
Quick overview:
Max Potential First Input Delay
2,120 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.
Time to Interactive
19.0 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 91 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 CSS
Potential savings of 36 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.
Minimize main-thread work
10.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Reduce the impact of third-party code
Third-party code blocked the main thread for 4,480 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. Learn how to minimize third-party impact.
Eliminate render-blocking resources
Potential savings of 2,940 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.
Reduce JavaScript execution time
7.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 567 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.
Properly size images
Potential savings of 42 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
7,720 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
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`.
Serve static assets with an efficient cache policy
10 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 7,129 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 13 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

Xr.global Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
2 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Xr.global Mobile Best Practices: 76/100
Quick overview:
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
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.
Xr.global Mobile Accessibility: 92/100
Quick overview:
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.
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.xr.com
www.xr.net
www.xr.org
www.xr.info
www.xr.biz
www.xr.us
www.xr.mobi
www.r.global
www.xr.global
www.zr.global
www.xzr.global
www.zxr.global
www.sr.global
www.xsr.global
www.sxr.global
www.dr.global
www.xdr.global
www.dxr.global
www.cr.global
www.xcr.global
www.cxr.global
www.x.global
www.xe.global
www.xre.global
www.xer.global
www.xd.global
www.xrd.global
www.xf.global
www.xrf.global
www.xfr.global
www.xt.global
www.xrt.global
www.xtr.global
Last Tested: