26 sec in total
957 ms
24.8 sec
237 ms
Visit omniland.co.za now to see the best up-to-date Omniland content for South Africa and also check out these interesting facts you probably never knew about omniland.co.za
At Omniland we strive to do better for our clients whether it is property auctioneers, property on auction or property for sale we do it all.
Visit omniland.co.zaWe analyzed Omniland.co.za page load time and found that the first response time was 957 ms and then it took 25 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
omniland.co.za performance score
name
value
score
weighting
Value14.0 s
0/100
10%
Value18.5 s
0/100
25%
Value43.7 s
0/100
10%
Value390 ms
69/100
30%
Value0.185
66/100
15%
Value20.2 s
2/100
10%
957 ms
7501 ms
961 ms
963 ms
962 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 85% of them (88 requests) were addressed to the original Omniland.co.za, 13% (13 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7.5 sec) belongs to the original domain Omniland.co.za.
Page size can be reduced by 306.6 kB (35%)
875.8 kB
569.3 kB
In fact, the total size of Omniland.co.za main page is 875.8 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. 55% of websites need less resources to load. HTML takes 363.2 kB which makes up the majority of the site volume.
Potential reduce by 298.3 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 298.3 kB or 82% of the original size.
Potential reduce by 2.8 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. Omniland images are well optimized though.
Potential reduce by 1.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 3.8 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. Omniland.co.za has all CSS files already compressed.
Number of requests can be reduced by 78 (90%)
87
9
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omniland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
omniland.co.za
957 ms
www.omniland.co.za
7501 ms
font-awesome.min.css
961 ms
fullcalendar.min.css
963 ms
jquery.qtip.min.css
962 ms
owl.carousel.css
965 ms
woocommerce-layout.css
966 ms
woocommerce.css
969 ms
css
27 ms
css
13 ms
photoswipe.min.css
961 ms
default-skin.min.css
961 ms
select2.css
958 ms
meta-style.css
963 ms
general.css
966 ms
style.css
973 ms
jquery.min.js
1612 ms
jquery-migrate.min.js
1285 ms
jquery.blockUI.min.js
1285 ms
add-to-cart.min.js
1290 ms
js.cookie.min.js
1293 ms
woocommerce.min.js
1298 ms
jquery.zoom.min.js
1610 ms
jquery.flexslider.min.js
1610 ms
photoswipe.min.js
1682 ms
photoswipe-ui-default.min.js
1681 ms
single-product.min.js
1682 ms
cart-fragments.min.js
1944 ms
country-select.min.js
1641 ms
address-i18n.min.js
1629 ms
checkout.min.js
1641 ms
select2.full.min.js
1644 ms
selectWoo.full.min.js
1966 ms
wc-blocks.css
1951 ms
core.min.js
1959 ms
menu.min.js
1961 ms
wp-polyfill-inert.min.js
1962 ms
regenerator-runtime.min.js
1968 ms
wp-polyfill.min.js
2284 ms
dom-ready.min.js
2296 ms
hooks.min.js
1952 ms
i18n.min.js
1967 ms
a11y.min.js
1964 ms
autocomplete.min.js
1966 ms
owl.carousel.min.js
2278 ms
plugin-script.js
2267 ms
sourcebuster.min.js
1958 ms
order-attribution.min.js
1965 ms
react.min.js
1972 ms
deprecated.min.js
1961 ms
dom.min.js
2271 ms
react-dom.min.js
2593 ms
escape-html.min.js
1964 ms
element.min.js
1961 ms
is-shallow-equal.min.js
1960 ms
keycodes.min.js
1965 ms
priority-queue.min.js
2260 ms
compose.min.js
1967 ms
private-apis.min.js
1965 ms
redux-routine.min.js
1896 ms
data.min.js
1903 ms
lodash.min.js
2198 ms
wc-blocks-registry.js
2226 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
18 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
27 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
33 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
36 ms
u-4m0qyriQwlOrhSvowK_l5-eRZAf-c.ttf
120 ms
u-4l0qyriQwlOrhSvowK_l5-eR7lXff2jvk.ttf
108 ms
u-4l0qyriQwlOrhSvowK_l5-eR71Wvf2jvk.ttf
85 ms
u-4l0qyriQwlOrhSvowK_l5-eR7NWPf2jvk.ttf
209 ms
u-440qyriQwlOrhSvowK_l5-ciZJ.ttf
41 ms
u-4n0qyriQwlOrhSvowK_l521wRZVsf_.ttf
41 ms
u-4n0qyriQwlOrhSvowK_l52xwNZVsf_.ttf
44 ms
u-4n0qyriQwlOrhSvowK_l52_wFZVsf_.ttf
45 ms
url.min.js
1963 ms
api-fetch.min.js
1956 ms
wc-settings.js
1964 ms
data-controls.min.js
1966 ms
html-entities.min.js
2257 ms
notices.min.js
1960 ms
wc-blocks-middleware.js
1964 ms
wc-blocks-data.js
1976 ms
primitives.min.js
1968 ms
warning.min.js
1970 ms
blocks-components.js
2266 ms
blocks-checkout.js
1965 ms
order-attribution-blocks.min.js
1952 ms
scripts.min.js
2322 ms
jquery.fitvids.js
1973 ms
common.js
1964 ms
smush-lazy-load.min.js
2257 ms
modules.woff
1988 ms
3D_illustration_image_of_a_gavel_-_auction_hammer_-_free_to_use_in_your_projects_02-small-scaled.jpg
2285 ms
OMNILAND-BANNER.jpg
968 ms
www.omniland.co.za
3249 ms
IMG-20220102-WA0019-300x300.jpg
336 ms
LOTTER-ML-resize-300x300.jpg
331 ms
thumb__600_450_0_0_crop-300x300.jpeg
332 ms
ROBBERTZE-resize-300x300.jpg
645 ms
woocommerce-smallscreen.css
327 ms
style.min.css
645 ms
omniland.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.
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
<frame> or <iframe> elements do not have a title
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.
omniland.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
omniland.co.za SEO score
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 Omniland.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 Omniland.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.
omniland.co.za
Open Graph data is detected on the main page of Omniland. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: