1.3 sec in total
135 ms
1.1 sec
120 ms
Click here to check amazing My XM content for South Africa. Otherwise, check out these important facts you probably never knew about my.xm.com
Visit my.xm.comWe analyzed My.xm.com page load time and found that the first response time was 135 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
my.xm.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value7.8 s
3/100
25%
Value3.3 s
90/100
10%
Value140 ms
95/100
30%
Value0.057
98/100
15%
Value5.4 s
71/100
10%
135 ms
90 ms
97 ms
126 ms
144 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original My.xm.com, 56% (22 requests) were made to Static.xm-cdn.com and 15% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (291 ms) relates to the external source Connect.facebook.net.
Page size can be reduced by 692.2 kB (69%)
1.0 MB
317.1 kB
In fact, the total size of My.xm.com main page is 1.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. CSS take 782.6 kB which makes up the majority of the site volume.
Potential reduce by 18.2 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 6.4 kB, which is 28% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 18.2 kB or 79% of the original size.
Potential reduce by 1.6 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. My XM images are well optimized though.
Potential reduce by 110.2 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 110.2 kB or 59% of the original size.
Potential reduce by 562.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. My.xm.com needs all CSS files to be minified and compressed as it can save up to 562.1 kB or 72% of the original size.
Number of requests can be reduced by 4 (21%)
19
15
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My XM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
login
135 ms
css
90 ms
main.css
97 ms
en.css
126 ms
jquery-1.11.1.min.js
144 ms
main.js
154 ms
gtm.js
85 ms
gb.svg
113 ms
xm.png
54 ms
meta-quotes.png
54 ms
verisign.png
54 ms
investors.png
69 ms
unicef.png
70 ms
trading-point.png
55 ms
Roboto-Bold-webfont.woff
55 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
66 ms
Roboto-Black-webfont.woff
243 ms
H1vB34nOKWXqzKotq25pcg.ttf
82 ms
Roboto-Medium-webfont.woff
243 ms
Uxzkqj-MIMWle-XP2pDNAA.ttf
122 ms
Roboto-Regular-webfont.woff
226 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
136 ms
Roboto-Light-webfont.woff
242 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
136 ms
Roboto-Thin-webfont.woff
65 ms
7MygqTe2zs9YkP0adA9QQQ.ttf
137 ms
fontawesome-webfont.woff
134 ms
bebasneue_bold-webfont.ttf
79 ms
bebasneue_bold-webfont.ttf
134 ms
bebasneue_regular-webfont.ttf
135 ms
bebasneue_regular-webfont.ttf
151 ms
analytics.js
45 ms
fbds.js
291 ms
collect
34 ms
collect
74 ms
collect
32 ms
collect
89 ms
ga-audiences
40 ms
ga-audiences
24 ms
my.xm.com accessibility score
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.
Impact
Issue
[role]s are not contained by their required parent element
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.
Impact
Issue
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
my.xm.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
my.xm.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My.xm.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that My.xm.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
my.xm.com
Open Graph description is not detected on the main page of My XM. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: