12.2 sec in total
1.1 sec
10.1 sec
1 sec
Welcome to oonkloof.co.za homepage info - get ready to check O Onkloof best content right away, or after learning these important things about oonkloof.co.za
Visit oonkloof.co.zaWe analyzed Oonkloof.co.za page load time and found that the first response time was 1.1 sec and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
oonkloof.co.za performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value10.9 s
0/100
25%
Value29.8 s
0/100
10%
Value24,280 ms
0/100
30%
Value0.034
100/100
15%
Value42.9 s
0/100
10%
1054 ms
621 ms
538 ms
596 ms
2509 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 57% of them (75 requests) were addressed to the original Oonkloof.co.za, 18% (24 requests) were made to Google.com and 12% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Oonkloof.co.za.
Page size can be reduced by 116.4 kB (9%)
1.4 MB
1.2 MB
In fact, the total size of Oonkloof.co.za main page is 1.4 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 84.1 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 84.1 kB or 82% of the original size.
Potential reduce by 12.3 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. O Onkloof images are well optimized though.
Potential reduce by 20.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 20.0 kB or 12% of the original size.
Number of requests can be reduced by 73 (69%)
106
33
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O Onkloof. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
www.oonkloof.co.za
1054 ms
main.css
621 ms
style.min.css
538 ms
rs6.css
596 ms
style.min.css
2509 ms
theme.min.css
2375 ms
frontend-lite.min.css
574 ms
post-8.css
816 ms
elementor-icons.min.css
878 ms
frontend-lite.min.css
900 ms
post-166.css
857 ms
all.min.css
1082 ms
v4-shims.min.css
1141 ms
post-125.css
1165 ms
post-119.css
1175 ms
ekiticons.css
1383 ms
css
102 ms
elegant.css
1416 ms
linearicons.css
1441 ms
themify.css
1426 ms
widget-styles.css
1990 ms
responsive.css
1700 ms
fontawesome.min.css
1689 ms
solid.min.css
1724 ms
jkiticon.css
1965 ms
regular.min.css
1954 ms
brands.min.css
2055 ms
jquery.min.js
2270 ms
jquery-migrate.min.js
2233 ms
rbtools.min.js
2256 ms
rs6.min.js
2800 ms
v4-shims.min.js
2472 ms
widget-icon-list.min.css
2477 ms
widget-nav-menu.min.css
2502 ms
widget-call-to-action.min.css
2609 ms
tiny-slider.css
2416 ms
hello-frontend.min.js
3510 ms
frontend-script.js
2550 ms
widget-scripts.js
2509 ms
webpack.runtime.min.js
2470 ms
frontend-modules.min.js
2431 ms
waypoints.min.js
2543 ms
core.min.js
2359 ms
frontend.min.js
2315 ms
sticky-element.js
2416 ms
jquery.smartmenus.min.js
2396 ms
testimonials.js
2331 ms
tiny-slider.js
2276 ms
webpack-pro.runtime.min.js
2327 ms
regenerator-runtime.min.js
2392 ms
wp-polyfill.min.js
2165 ms
hooks.min.js
2320 ms
i18n.min.js
2234 ms
frontend.min.js
2298 ms
elements-handlers.min.js
2105 ms
animate-circle.js
2067 ms
elementor.js
2194 ms
swiper.min.js
2315 ms
logo-oonkloof-trans-psa1i1rs6elut3xoj38zrvr15ypvsuqpr3yh1foe0w.png
1041 ms
dummy.png
1097 ms
O-onkloof-new-logo.jpg
1672 ms
Tripadvisor-2019_2.jpeg
1159 ms
Tripadvisor-2018.jpeg
1327 ms
Tripadvisor-2017.jpeg
1338 ms
Tripadvisor-2016.jpeg
1386 ms
Tripadvisor-2015.jpeg
1442 ms
Tripadvisor-2014.jpeg
1560 ms
maps
102 ms
bg-tvlounge.jpeg
1755 ms
O-onkloof-The-Perfect-Welcome.jpeg
1482 ms
O-onkloof-hotel.jpeg
1396 ms
OonKloof_sunset_full.jpeg
2497 ms
o-on-kloof-3810.jpeg
2498 ms
ieVi2ZhZI2eCN5jzbjEETS9weq8-33mZGCQYatlecyU.ttf
88 ms
ieVl2ZhZI2eCN5jzbjEETS9weq8-19K7CAk6YvM.ttf
88 ms
ieVi2ZhZI2eCN5jzbjEETS9weq8-32meGCQYatlecyU.ttf
88 ms
fa-solid-900.woff
2448 ms
fa-regular-400.woff
1692 ms
fa-brands-400.woff
2447 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMBbKsUPpjl.ttf
136 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMBbKsUPpjl.ttf
412 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMBbKsUPpjl.ttf
412 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMBbKsUPpjl.ttf
281 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMBbKsUPpjl.ttf
149 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl2xMBbKsUPpjl.ttf
148 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql2xMBbKsUPpjl.ttf
146 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
220 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
219 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
219 ms
KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf
223 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
221 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
223 ms
jkiticon.ttf
3178 ms
embed
712 ms
js
22 ms
gen_204
28 ms
init_embed.js
33 ms
common.js
83 ms
util.js
132 ms
map.js
118 ms
overlay.js
79 ms
onion.js
71 ms
search_impl.js
70 ms
openhand_8_8.cur
101 ms
ViewportInfoService.GetViewportInfo
57 ms
kh
76 ms
AuthenticationService.Authenticate
77 ms
vt
124 ms
vt
95 ms
vt
93 ms
vt
94 ms
vt
98 ms
vt
125 ms
vt
133 ms
vt
130 ms
vt
124 ms
vt
126 ms
vt
128 ms
vt
134 ms
vt
155 ms
vt
161 ms
vt
154 ms
vt
147 ms
vt
149 ms
vt
153 ms
vt
200 ms
vt
186 ms
vt
193 ms
vt
144 ms
vt
147 ms
QuotaService.RecordEvent
18 ms
oonkloof.co.za accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
oonkloof.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
Browser errors were logged to the console
oonkloof.co.za SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Oonkloof.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 Oonkloof.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.
oonkloof.co.za
Open Graph description is not detected on the main page of O Onkloof. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: