11.9 sec in total
927 ms
10.7 sec
313 ms
Visit xenex.co.za now to see the best up-to-date Xenex content and also check out these interesting facts you probably never knew about xenex.co.za
Unlock IT efficiency with our tailored MSP solutions. With Xenex Proactive support ensures uninterrupted operations, maximizing productivity for your business.
Visit xenex.co.zaWe analyzed Xenex.co.za page load time and found that the first response time was 927 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
xenex.co.za performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value7.3 s
5/100
25%
Value20.9 s
0/100
10%
Value1,080 ms
24/100
30%
Value0.047
99/100
15%
Value12.8 s
13/100
10%
927 ms
2173 ms
307 ms
619 ms
890 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 99% of them (72 requests) were addressed to the original Xenex.co.za, 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Xenex.co.za.
Page size can be reduced by 88.7 kB (18%)
491.6 kB
402.9 kB
In fact, the total size of Xenex.co.za main page is 491.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 206.3 kB which makes up the majority of the site volume.
Potential reduce by 70.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 70.5 kB or 80% of the original size.
Potential reduce by 17.2 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. Obviously, Xenex needs image optimization as it can save up to 17.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 384 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 623 B
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. Xenex.co.za has all CSS files already compressed.
Number of requests can be reduced by 62 (91%)
68
6
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xenex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
xenex.co.za
927 ms
www.xenex.co.za
2173 ms
74fb49425f13b20a62cc0b0282bc7210.css
307 ms
0897c1306ed651787caf5df18df28b4e.css
619 ms
7220b95453cb86886d1388f438a7408f.css
890 ms
596b9f95acb4fdd9f4505c63e0f11ffd.css
912 ms
3f966fd52f1fa3aec65d1ca9cb4fc90b.css
915 ms
e862ba94c63c38375bcad7ba5344b1cb.css
918 ms
c8870999f1bb830da04a35b4e3331280.css
921 ms
63057b61df2c0106b207bf51aa142e6d.css
918 ms
71cc23d809b214683ffb1c24ae21d4cc.css
1187 ms
6438001187e35fa57d47eda8b56df504.css
1213 ms
7d352c14d82f76bf86b7a3492b3f33d5.css
1224 ms
9dc4ce8410c1a600e66a1de7b9982871.css
1226 ms
ab47a6938ad5356cd79220c7cee971c0.css
1223 ms
c672727099851b02b42f89cbd7793383.css
1228 ms
203c24fb29bd668d3d61f91eb283d266.css
1490 ms
b890654ac485cdccb28679a9ca9a2174.css
1514 ms
b55b0b654ed033ac31f80ddaa5e768f0.css
1514 ms
375037052bca5b5079f7e37945b1b973.css
1523 ms
bcaa48cdefdc5af165bce60731ddab12.css
1535 ms
5732bfb0d43cb9f39bc5898bf0391383.css
1534 ms
5b087d6223e018bdb2855b74b16b95e9.css
1789 ms
167205dab5c6f2181d26dc9a349ef73b.css
1822 ms
35e8a2a6056e2e4618b15d16aa88ca60.css
1820 ms
2a927c316d7a1509e545773627063f4b.css
1824 ms
29058158a6f6399d9a85a0cc81ab22e8.css
1839 ms
0241344017a9bdf0577f11937a6ee423.css
1837 ms
c88a716198e1c6024f081e3feb75679a.css
2085 ms
3fe4f367cb42a09c227c7956eeda11bc.css
2120 ms
9a631b073d402896b53b8960a7b37a92.css
2121 ms
913f0daecd30472ec6e1ca28968a8bf5.css
2127 ms
dbdff1caa312cb8803c7868fdf760a14.css
2140 ms
7d32282d8adc3bccc4e62864e1d1aa1b.css
2142 ms
d5030d91ad74cae7eebe7086fb01afb9.css
2379 ms
cefb833a124c6e544cfe9e3a04ed9798.css
2419 ms
79d61a3b2ada699b6c8d97d9f2f808c3.css
2419 ms
js
44 ms
6da5528585b8eb440d5c7d1cad832a1c.css
2428 ms
a3566f51f469416d32b6f578e15e1c5a.css
2143 ms
jquery.min.js
2138 ms
7cedde5735b18503660d1b354fbb75e4.js
1801 ms
2bea5159ee39c810a1fbd5da70825af1.js
1812 ms
2fd03509cc636d113c88d03bc0220084.js
1815 ms
f04488c6d821c9d348c8f0549beb95d3.js
1826 ms
dd9567c3960d30ae62409641314c2f3d.js
1836 ms
c2b92e376347d62d4247203c538fc1c5.js
2668 ms
5c55e4e8ed986d7e74539f98895dd920.js
1839 ms
6bb0b23ff04e82164d9a4b6421609990.js
1820 ms
64dd32f3455a3b96e56987ba5890dad7.js
1823 ms
d026ca30fb2e3f2ec4ac06bae7d8ebfc.js
1839 ms
986ff4ae4ad9006d3d2acfeb5be89b41.js
1838 ms
1f724ed74d2bc1ec04dd29167a167fbf.js
2100 ms
9c89e6b23536ce0334283f745c31cffc.js
1854 ms
dfff9f906ffc88d1b033068adc0ff656.js
1836 ms
b5f10a2c0ae56eb1220ac4344ef52142.js
2157 ms
9776a34b54d5bb4fdc54fb1b0175cb76.js
1845 ms
1119a3fa47edb90d0511be1d4186788b.js
2092 ms
5018115ee0959f2f5f2a6382b8885a31.js
2112 ms
009133ebecb94ecb8f1e306c76978fcf.js
1862 ms
dc4cab0d840a893a916e4905496fce43.js
1853 ms
c0a442746ab17d534570ee8a845e5da6.js
2063 ms
46c8b81f043af356e8f886fe234c03fa.js
2107 ms
c0c8434da1a3dac773ea5eef5d916b9e.js
2118 ms
36bbcee04e4b0d53e04b6a659652c6fd.js
2119 ms
Xenex-computers-Logo-2022-1.png
1809 ms
placeholder-12.png
1212 ms
placeholder-13.png
1417 ms
placeholder-14.png
1474 ms
fa-solid-900.woff
2048 ms
fa-regular-400.woff
1457 ms
fa-brands-400.woff
1777 ms
196da1cadf8275603bf06c389f4a5e66.css
299 ms
xenex.co.za accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
xenex.co.za 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
Browser errors were logged to the console
Page has valid source maps
xenex.co.za SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Xenex.co.za 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 Xenex.co.za 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.
xenex.co.za
Open Graph data is detected on the main page of Xenex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: