10.5 sec in total
79 ms
9.8 sec
649 ms
Click here to check amazing Viadex content for South Africa. Otherwise, check out these important facts you probably never knew about viadex.com
Global IT Supply Chain. IT infrastructure deployment and managed services provider. Data Centre equipment supply and solutions. IOR
Visit viadex.comWe analyzed Viadex.com page load time and found that the first response time was 79 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
viadex.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value18.3 s
0/100
25%
Value37.7 s
0/100
10%
Value48,470 ms
0/100
30%
Value0.03
100/100
15%
Value60.8 s
0/100
10%
79 ms
438 ms
4717 ms
38 ms
226 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 22% of them (20 requests) were addressed to the original Viadex.com, 20% (18 requests) were made to Fonts.gstatic.com and 10% (9 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Viadex.com.
Page size can be reduced by 992.6 kB (21%)
4.8 MB
3.8 MB
In fact, the total size of Viadex.com main page is 4.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 693.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. 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 693.2 kB or 84% of the original size.
Potential reduce by 288.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. Viadex images are well optimized though.
Potential reduce by 4.7 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.3 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. Viadex.com needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 77% of the original size.
Number of requests can be reduced by 47 (72%)
65
18
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viadex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
viadex.com
79 ms
viadex.com
438 ms
www.viadex.com
4717 ms
jquery-1.12.4.min.js
38 ms
css
226 ms
css
305 ms
dashicons.min.css
122 ms
autoptimize_single_d626a72361d8e902966ee5aaaa50cfa5.css
123 ms
autoptimize_single_6c1f2b5c83fe719eb3c1ec245c13dbc1.css
409 ms
autoptimize_single_c3b0519e17c2b0ac1b017916a96f0ac8.css
123 ms
autoptimize_single_710fdceb582779d53f783de7e59bf2ae.css
85 ms
jquery.min.js
143 ms
6b2fe84a-5c51-46c6-bdd3-db0a2d952b74.js
866 ms
js
305 ms
conversion.js
299 ms
6a1dd6a9-d889-4d16-a398-ee04c1800d31.js
1459 ms
183700.js
290 ms
pa-612f55aa1733500011000074.js
992 ms
lazysizes.min.js
254 ms
js
315 ms
api.js
280 ms
autoptimize_ba23508d130f2dd6eb65da0d48886332.js
271 ms
wp-emoji-release.min.js
25 ms
gtm.js
493 ms
9ZV96Cqb026KZO5yCJa3
764 ms
sl.js
1099 ms
webfont.js
1158 ms
js
530 ms
js
949 ms
js
745 ms
analytics.js
1091 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jvvKsOdC6jJ7bpDhI.ttf
1250 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jjPKsOdC6jJ7bpDhI.ttf
1450 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8j4PKsOdC6jJ7bpDhI.ttf
1538 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jPvKsOdC6jJ7bpDhI.ttf
1562 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jvvOsOdC6jJ7bpDhI.ttf
1518 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jYPWsOdC6jJ7bpDhI.ttf
1518 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jWfWsOdC6jJ7bpDhI.ttf
1537 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jPvWsOdC6jJ7bpDhI.ttf
1762 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jF_WsOdC6jJ7bpDhI.ttf
1780 ms
fa-solid-900.woff
1281 ms
fa-regular-400.woff
678 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drF0feC9hpr5oBBKdrg.ttf
1778 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drFGfeC9hpr5oBBKdrg.ttf
1779 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drEqfeC9hpr5oBBKdrg.ttf
1777 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drH0feC9hpr5oBBKdrg.ttf
1777 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drF0fOC9hpr5oBBKdrg.ttf
1865 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drGqeuC9hpr5oBBKdrg.ttf
1883 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drGTeuC9hpr5oBBKdrg.ttf
1999 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drH0euC9hpr5oBBKdrg.ttf
1882 ms
7cH3v4okm5zmbtYtMeA0FKq0Jjg2drHdeuC9hpr5oBBKdrg.ttf
2097 ms
hotjar-2067953.js
1092 ms
insight.min.js
1088 ms
fa-brands-400.woff
1076 ms
1030 ms
1es37nrju
1283 ms
1lCCWTDocEWYtF-zaOvFww2
1523 ms
gen_204
417 ms
recaptcha__en_gb.js
1072 ms
r
793 ms
568 ms
viadex-selig-bkg.png
1319 ms
css
516 ms
web-banner.png
1387 ms
3510-vdx-covid-19-trade-routes-graphic-01-01.png
1369 ms
3220-vdx_micrograming-web-banner.jpg
1220 ms
hme-covid-19-icon.png
632 ms
collect
230 ms
203 ms
modules.cbd9768ba80ba0be5b17.js
550 ms
i
114 ms
collect
677 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
449 ms
version.js
471 ms
ga-audiences
149 ms
fonts.styles.css
323 ms
globalize.js
325 ms
globalize.culture.en-GB.js
328 ms
booking.selfservice.js
448 ms
visit-data
762 ms
25 ms
6a1dd6a9-d889-4d16-a398-ee04c1800d31.js
246 ms
twk-event-polyfill.js
62 ms
twk-entries-polyfill.js
65 ms
twk-main.js
50 ms
twk-vendor.js
118 ms
twk-chunk-vendors.js
50 ms
twk-chunk-common.js
32 ms
twk-runtime.js
42 ms
twk-app.js
98 ms
viadex.com 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
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
viadex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
viadex.com 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
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 Viadex.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 Viadex.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.
viadex.com
Open Graph data is detected on the main page of Viadex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: