42 sec in total
876 ms
38.3 sec
2.8 sec
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
Computer support and IT solutions to businesses and home users. Service Level Agreements for any size business. +27 11 867 5888
Visit xenex.co.zaWe analyzed Xenex.co.za page load time and found that the first response time was 876 ms and then it took 41.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
xenex.co.za performance score
name
value
score
weighting
Value18.1 s
0/100
10%
Value25.6 s
0/100
25%
Value49.0 s
0/100
10%
Value1,540 ms
13/100
30%
Value0.008
100/100
15%
Value23.9 s
1/100
10%
876 ms
6707 ms
849 ms
871 ms
864 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 88% of them (64 requests) were addressed to the original Xenex.co.za, 5% (4 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Xenex.co.za.
Page size can be reduced by 287.6 kB (24%)
1.2 MB
922.8 kB
In fact, the total size of Xenex.co.za main page is 1.2 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. 55% of websites need less resources to load. Images take 812.3 kB which makes up the majority of the site volume.
Potential reduce by 120.9 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 120.9 kB or 84% of the original size.
Potential reduce by 155.4 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 155.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 6.7 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. Xenex.co.za has all CSS files already compressed.
Number of requests can be reduced by 58 (84%)
69
11
The browser has sent 69 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 32 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
xenex.co.za
876 ms
www.xenex.co.za
6707 ms
wp-emoji-release.min.js
849 ms
style.min.css
871 ms
animate.css
864 ms
frontend.css
844 ms
wprev-public_combine.css
853 ms
elementor-icons.min.css
882 ms
frontend-legacy.min.css
1623 ms
frontend.min.css
1929 ms
post-37.css
1659 ms
jquery.mmenu.all.css
1676 ms
slick.css
1683 ms
slick-theme.css
1726 ms
style.css
2456 ms
dashicons.min.css
2754 ms
frontend.css
2508 ms
global.css
2524 ms
post-2.css
2547 ms
css
129 ms
headers.css
2733 ms
footers.css
3280 ms
blog.css
3333 ms
main.css
3367 ms
style.css
3369 ms
responsive.css
3576 ms
css
118 ms
smartslider.min.css
3578 ms
css
118 ms
jquery.min.js
4379 ms
jquery-migrate.min.js
4158 ms
frontend.js
4176 ms
js
152 ms
n2.min.js
4210 ms
smartslider-frontend.min.js
4928 ms
ss-simple.min.js
4923 ms
w-arrow-image.min.js
5428 ms
w-bullet.min.js
6150 ms
animations.min.css
6108 ms
wprev-public-com-min.js
6148 ms
jquery.stellar.js
6146 ms
jquery.nav.js
6695 ms
css
16 ms
theia-sticky-sidebar.js
6051 ms
main.js
6278 ms
webpack.runtime.min.js
6283 ms
frontend-modules.min.js
6566 ms
waypoints.min.js
6259 ms
core.min.js
6798 ms
swiper.min.js
6344 ms
share-link.min.js
6293 ms
dialog.min.js
6265 ms
frontend.min.js
6561 ms
preloaded-modules.min.js
6786 ms
jquery.mmenu.all.min.js
6589 ms
jquery.sticky-sidebar.min.js
6321 ms
iframe-api.js
6269 ms
slick.min.js
6274 ms
frontend.js
6525 ms
facebook.png
4947 ms
linkedin.png
5231 ms
support.png
1336 ms
support-tools.png
1357 ms
Xenex-Logo.png
5791 ms
About-Us.jpg
6945 ms
f1.jpg
5232 ms
covid-250x.png
5506 ms
js
377 ms
analytics.js
58 ms
collect
469 ms
support.png
5016 ms
support-tools.png
4718 ms
www-widgetapi.js
42 ms
xenex.co.za accessibility score
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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
xenex.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
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: