18 sec in total
737 ms
17 sec
322 ms
Click here to check amazing Visitzululand content. Otherwise, check out these important facts you probably never knew about visitzululand.co.za
Umlalazi Paradise - Choose your favorite route to explore. We aim to be your go-to guide for when you visit our piece of paradise.
Visit visitzululand.co.zaWe analyzed Visitzululand.co.za page load time and found that the first response time was 737 ms and then it took 17.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
visitzululand.co.za performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value19.8 s
0/100
25%
Value28.8 s
0/100
10%
Value1,720 ms
10/100
30%
Value0
100/100
15%
Value28.7 s
0/100
10%
737 ms
2710 ms
65 ms
39 ms
740 ms
Our browser made a total of 190 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Visitzululand.co.za, 89% (169 requests) were made to Visitumlalazi.com and 7% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Visitumlalazi.com.
Page size can be reduced by 187.5 kB (63%)
298.2 kB
110.8 kB
In fact, the total size of Visitzululand.co.za main page is 298.2 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. 70% of websites need less resources to load. HTML takes 220.2 kB which makes up the majority of the site volume.
Potential reduce by 179.8 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 179.8 kB or 82% of the original size.
Potential reduce by 7.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. Visitzululand images are well optimized though.
Potential reduce by 225 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 225 B or 35% of the original size.
Number of requests can be reduced by 158 (92%)
172
14
The browser has sent 172 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Visitzululand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 125 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
visitzululand.co.za
737 ms
visitumlalazi.com
2710 ms
js
65 ms
css
39 ms
select2.min.css
740 ms
iconfonts.css
1077 ms
frontend.min.css
2202 ms
tooltip.css
1087 ms
tooltipster-sideTip-shadow.min.css
1089 ms
featherlight.css
1102 ms
lity.min.css
1107 ms
mec-general-calendar.css
1441 ms
style.min.css
1813 ms
cookie-law-info-public.css
1458 ms
cookie-law-info-gdpr.css
1477 ms
ivory-search.min.css
1474 ms
mediaelementplayer-legacy.min.css
1801 ms
wp-mediaelement.min.css
1822 ms
style.css
1839 ms
font-awesome.min.css
1844 ms
style.min.css
2162 ms
style.css
2177 ms
dripicons.css
2189 ms
kiko-all.css
2216 ms
font-awesome-5.min.css
2217 ms
stylesheet.min.css
3987 ms
print.css
2541 ms
style_dynamic.css
2554 ms
responsive.min.css
2563 ms
style_dynamic_responsive.css
2655 ms
js_composer.min.css
3412 ms
core-dashboard.min.css
2904 ms
joinchat.min.css
2917 ms
jquery.min.js
3303 ms
jquery-migrate.min.js
3019 ms
mec-general-calendar.js
4383 ms
frontend.js
3657 ms
events.js
3386 ms
timeme.min.js
3668 ms
api.js
33 ms
ivory-ajax-search.min.css
3408 ms
cookie-law-info-table.css
3047 ms
rs6.css
2967 ms
intl-tel-input.min.css
2958 ms
wpforms-full.css
3040 ms
burst.min.js
3056 ms
cookie-law-info-public.js
3246 ms
cookie-law-info-ccpa.js
2966 ms
rbtools.min.js
3340 ms
rs6.min.js
4200 ms
core.min.js
3164 ms
mediaelement-and-player.min.js
3285 ms
mediaelement-migrate.min.js
2941 ms
datepicker.min.js
2960 ms
jquery.typewatch.js
3166 ms
featherlight.js
3291 ms
select2.full.min.js
3342 ms
tooltip.js
2981 ms
lity.min.js
3184 ms
colorbrightness.min.js
3231 ms
owl.carousel.min.js
3283 ms
accordion.min.js
3298 ms
menu.min.js
3200 ms
wp-polyfill-inert.min.js
3252 ms
regenerator-runtime.min.js
3298 ms
wp-polyfill.min.js
3218 ms
dom-ready.min.js
2979 ms
hooks.min.js
3126 ms
i18n.min.js
3088 ms
a11y.min.js
2864 ms
autocomplete.min.js
2843 ms
controlgroup.min.js
2812 ms
checkboxradio.min.js
2588 ms
button.min.js
2745 ms
mouse.min.js
2722 ms
resizable.min.js
2748 ms
draggable.min.js
2555 ms
dialog.min.js
2562 ms
droppable.min.js
2568 ms
progressbar.min.js
2659 ms
selectable.min.js
2700 ms
sortable.min.js
2547 ms
slider.min.js
2560 ms
jdi0wx151h
149 ms
spinner.min.js
2531 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml1RMC.woff
112 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl1RMC.woff
196 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl1RMC.woff
196 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml1RMC.woff
198 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl1RMC.woff
199 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl1RMC.woff
199 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql1RMC.woff
198 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
144 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff
144 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
146 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
146 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
147 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
147 ms
clarity.js
82 ms
tooltip.min.js
2337 ms
tabs.min.js
2402 ms
effect.min.js
2446 ms
effect-blind.min.js
2443 ms
effect-bounce.min.js
2328 ms
effect-clip.min.js
2228 ms
effect-drop.min.js
2200 ms
effect-explode.min.js
2356 ms
effect-fade.min.js
2222 ms
effect-fold.min.js
2174 ms
effect-highlight.min.js
2195 ms
effect-pulsate.min.js
2186 ms
effect-size.min.js
2190 ms
effect-scale.min.js
2209 ms
effect-shake.min.js
2227 ms
effect-slide.min.js
2176 ms
effect-transfer.min.js
2196 ms
doubletaptogo.js
2194 ms
modernizr.min.js
2190 ms
jquery.appear.js
2213 ms
hoverIntent.min.js
2230 ms
counter.js
2182 ms
easypiechart.js
2208 ms
mixitup.js
2575 ms
jquery.prettyPhoto.js
2209 ms
jquery.fitvids.js
2213 ms
jquery.flexslider-min.js
2231 ms
wp-mediaelement.min.js
2187 ms
infinitescroll.min.js
2210 ms
jquery.waitforimages.js
2223 ms
jquery.form.min.js
2386 ms
waypoints.min.js
2295 ms
jplayer.min.js
2226 ms
bootstrap.carousel.js
2272 ms
skrollr.js
2214 ms
Chart.min.js
2617 ms
jquery.easing.1.3.js
2388 ms
abstractBaseClass.js
2285 ms
jquery.countdown.js
2226 ms
jquery.multiscroll.min.js
2276 ms
jquery.justifiedGallery.min.js
2214 ms
bigtext.js
2399 ms
jquery.sticky-kit.min.js
2458 ms
owl.carousel.min.js
2316 ms
typed.js
2305 ms
jquery.carouFredSel-6.2.1.min.js
2303 ms
lemmon-slider.min.js
2257 ms
jquery.fullPage.min.js
2416 ms
jquery.mousewheel.min.js
2460 ms
jquery.touchSwipe.min.js
2319 ms
jquery.isotope.min.js
2301 ms
packery-mode.pkgd.min.js
2306 ms
jquery.stretch.js
2260 ms
imagesloaded.js
2422 ms
rangeslider.min.js
2453 ms
jquery.event.move.js
2325 ms
jquery.twentytwenty.js
2305 ms
swiper.min.js
2678 ms
TweenLite.min.js
2249 ms
ScrollToPlugin.min.js
2408 ms
smoothPageScroll.min.js
2271 ms
default_dynamic.js
2243 ms
default.min.js
2692 ms
comment-reply.min.js
2249 ms
js_composer_front.min.js
2414 ms
qode-like.min.js
2439 ms
qr-creator.min.js
2332 ms
joinchat.min.js
2320 ms
ivory-search.min.js
2352 ms
ivory-ajax-search.min.js
2440 ms
jquery.intl-tel-input.min.js
2454 ms
jquery.validate.min.js
2337 ms
jquery.inputmask.bundle.min.js
2346 ms
mailcheck.min.js
2324 ms
wpforms.js
2250 ms
fontawesome-webfont.woff
3164 ms
fontawesome-webfont.woff
2784 ms
ElegantIcons.woff
3063 ms
Logo-resized.png
2363 ms
MASTER-visit-Umlalazi-logo-WHITE-02.png
2332 ms
spinner.gif
2612 ms
Accommodation-Guide-120x120.png
2618 ms
Travellers-Tips-1-120x120.png
2590 ms
KZN-Travel-Guide-120x120.png
2618 ms
KZN-Tourism-Map-120x120.png
2714 ms
Wedding-Planner-120x120.png
2711 ms
delete-sign.png
2647 ms
dummy.png
1240 ms
47 ms
jquery.intl-tel-input-utils.js
755 ms
c.gif
9 ms
visitzululand.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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
visitzululand.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
Page has valid source maps
visitzululand.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 Visitzululand.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 Visitzululand.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.
visitzululand.co.za
Open Graph data is detected on the main page of Visitzululand. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: