7.4 sec in total
1.1 sec
5.2 sec
1 sec
Visit encounter.co.za now to see the best up-to-date Encounter content for South Africa and also check out these interesting facts you probably never knew about encounter.co.za
Encounter South Africa is your online guide to What to Do and Where to Go in the country. Experience the cultural and natural diversity through our articles About South Africa.
Visit encounter.co.zaWe analyzed Encounter.co.za page load time and found that the first response time was 1.1 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
encounter.co.za performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value2.9 s
80/100
25%
Value4.0 s
80/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.9 s
96/100
10%
1136 ms
1131 ms
270 ms
536 ms
559 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 41% of them (19 requests) were addressed to the original Encounter.co.za, 17% (8 requests) were made to Googleads.g.doubleclick.net and 17% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Encounter.co.za.
Page size can be reduced by 88.6 kB (36%)
246.5 kB
157.8 kB
In fact, the total size of Encounter.co.za main page is 246.5 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. 45% of websites need less resources to load. Javascripts take 109.4 kB which makes up the majority of the site volume.
Potential reduce by 26.0 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. This page needs HTML code to be minified as it can gain 3.9 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 26.0 kB or 83% of the original size.
Potential reduce by 11.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. Obviously, Encounter needs image optimization as it can save up to 11.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 29.3 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 29.3 kB or 27% of the original size.
Potential reduce by 22.1 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. Encounter.co.za needs all CSS files to be minified and compressed as it can save up to 22.1 kB or 93% of the original size.
Number of requests can be reduced by 26 (60%)
43
17
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Encounter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
encounter.co.za
1136 ms
www.encounter.co.za
1131 ms
ajxmenu.css
270 ms
ajxmenu.js
536 ms
style.css
559 ms
adsbygoogle.js
9 ms
brand
19 ms
brand
97 ms
encounter-logo.png
630 ms
ca-pub-5941707402936268.js
89 ms
zrt_lookup.html
150 ms
show_ads_impl.js
150 ms
bg-content.png
506 ms
cr_final2.png
506 ms
bu-bg.gif
609 ms
bu-top.gif
610 ms
bu-top-sub.gif
610 ms
search_button.gif
609 ms
arrow.gif
610 ms
Where%20to%20go.jpg
889 ms
arrow.gif
890 ms
What%20to%20do.jpg
1121 ms
Info%20hub.jpg
1219 ms
What's%20on.jpg
1121 ms
ga.js
415 ms
ads
449 ms
__utm.gif
57 ms
google_custom_search_watermark.gif
50 ms
osd.js
223 ms
ads
332 ms
cr_btm_30.png
351 ms
scream_V3_display_url_single_css.css
344 ms
scream_V3_display_url_single_css.js
332 ms
layout_engine.js
342 ms
abg.js
330 ms
css
232 ms
m_js_controller.js
230 ms
favicon
470 ms
nessie_icon_tiamat_white.png
448 ms
11389056339426638867
78 ms
x_button_blue2.png
70 ms
back_blue.png
50 ms
s
25 ms
ad_choices_blue.png
9 ms
x_blue.png
63 ms
s
22 ms
encounter.co.za accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
encounter.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
encounter.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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Encounter.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Encounter.co.za main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
encounter.co.za
Open Graph description is not detected on the main page of Encounter. 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: