6.3 sec in total
283 ms
5.6 sec
392 ms
Welcome to trafalgar.co.za homepage info - get ready to check Trafalgar best content for South Africa right away, or after learning these important things about trafalgar.co.za
Property management services with our core business being property management services of sectional title schemes & home owners associations across South Africa
Visit trafalgar.co.zaWe analyzed Trafalgar.co.za page load time and found that the first response time was 283 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
trafalgar.co.za performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value11.8 s
0/100
25%
Value11.6 s
4/100
10%
Value2,920 ms
3/100
30%
Value0.086
93/100
15%
Value25.8 s
0/100
10%
283 ms
1389 ms
40 ms
55 ms
94 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 48% of them (50 requests) were addressed to the original Trafalgar.co.za, 11% (11 requests) were made to Fonts.gstatic.com and 8% (8 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source News.trafalgar.co.za.
Page size can be reduced by 370.7 kB (17%)
2.2 MB
1.8 MB
In fact, the total size of Trafalgar.co.za main page is 2.2 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 124.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. This page needs HTML code to be minified as it can gain 43.5 kB, which is 31% 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 124.8 kB or 89% of the original size.
Potential reduce by 128.2 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. Trafalgar images are well optimized though.
Potential reduce by 87.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 87.0 kB or 16% of the original size.
Potential reduce by 30.7 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. Trafalgar.co.za needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 21% of the original size.
Number of requests can be reduced by 48 (55%)
88
40
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trafalgar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
trafalgar.co.za
283 ms
www.trafalgar.co.za
1389 ms
style.css
40 ms
owl.carousel.min.css
55 ms
bootstrap.min.css
94 ms
style.css
77 ms
forms.css
63 ms
responsive.css
73 ms
owl.carousel.min.css
37 ms
jquery.fancybox.min.css
44 ms
select2.min.css
64 ms
toastr.css
42 ms
bootstrap-multiselect.css
43 ms
jquery-3.3.1.min.js
116 ms
popper.min.js
86 ms
bootstrap.min.js
137 ms
jquery.sticky.js
127 ms
main.js
136 ms
toastr.min.js
44 ms
select2.full.min.js
195 ms
bootstrap-multiselect.min.js
195 ms
api.js
33 ms
css2
39 ms
gtm.js
178 ms
7sNnYFXViME
275 ms
Blog-Images-800-X-600.jpg
3583 ms
Blog-Images-800-X-600.jpg
3546 ms
April.webp
2425 ms
header-logo.webp
109 ms
property_bg.webp
120 ms
section_footer.png
110 ms
zyKGuJVbeqGt5rvhZ3DoUaKlPUYnG7eVF812eTf5.png
263 ms
Wu7wuEhR7ZT8znVoDlwUsOoWqAQkd54hF2PpLRYe.webp
109 ms
1z2bQA4xzWJMA8HqVTC15susQMCKC9qPMYqjGVKs.webp
108 ms
cRv4tRaSr8QJyLpxz9rytv1Tq08qt3tEcmgeEycN.webp
143 ms
yQXQZaaFm342xH4Wu5vfLAVlJNNBUtd61ak96iTi.webp
144 ms
RaXiTtyGN0wLXr7i1BJbf6lrCehhul1MZl6hW3ej.webp
143 ms
MF5TZa1Jd1kAXRAqfx0md9STssRbZmHwhCd3F3Oc.png
143 ms
right-arrow.png
143 ms
magazine-image.webp
211 ms
icon-property-alerts.webp
210 ms
icon-sell-your-property.webp
210 ms
icon-free-evaluation.webp
211 ms
icon-e_learning.webp
210 ms
icon-health.webp
212 ms
icon-webinar.webp
212 ms
branches-cape_town.webp
212 ms
branches-durban.webp
212 ms
branches-east_london.webp
213 ms
branches-birdhaven_jhb.webp
214 ms
branches-knysna.webp
215 ms
branches-port_eliza.webp
214 ms
branches-pretoria.webp
214 ms
section_footer_1.png
260 ms
section_footer_2.png
260 ms
footer-logo.webp
261 ms
facebook.webp
261 ms
insta.webp
264 ms
twitter.webp
253 ms
pxiEyp8kv8JHgFVrFJM.woff
86 ms
pxiByp8kv8JHgFVrLGT9V1g.woff
96 ms
pxiByp8kv8JHgFVrLDz8V1g.woff
122 ms
pxiByp8kv8JHgFVrLFj_V1g.woff
122 ms
pxiGyp8kv8JHgFVrLPTedA.woff
133 ms
pxiByp8kv8JHgFVrLEj6V1g.woff
133 ms
pxiByp8kv8JHgFVrLCz7V1g.woff
134 ms
pxiByp8kv8JHgFVrLDD4V1g.woff
133 ms
pxiByp8kv8JHgFVrLBT5V1g.woff
133 ms
linked.webp
244 ms
youtube.webp
186 ms
icomoon.ttf
512 ms
1g54c425r
417 ms
js
79 ms
analytics.js
61 ms
destination
264 ms
insight.min.js
298 ms
loader.js
250 ms
fbevents.js
291 ms
fbt.js
347 ms
www-player.css
15 ms
www-embed-player.js
208 ms
base.js
338 ms
collect
226 ms
call-tracking_9.js
38 ms
collect
349 ms
insight_tag_errors.gif
469 ms
ad_status.js
198 ms
4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js
95 ms
embed.js
50 ms
ga-audiences
165 ms
KFOmCnqEu92Fr1Mu4mxM.woff
43 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
42 ms
id
111 ms
wcm
113 ms
Create
26 ms
GenerateIT
16 ms
log_event
17 ms
twk-event-polyfill.js
249 ms
twk-main.js
89 ms
twk-vendor.js
166 ms
twk-chunk-vendors.js
180 ms
twk-chunk-common.js
46 ms
twk-runtime.js
87 ms
twk-app.js
65 ms
trafalgar.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
trafalgar.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
Page has valid source maps
trafalgar.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 Trafalgar.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 Trafalgar.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.
trafalgar.co.za
Open Graph description is not detected on the main page of Trafalgar. 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: