8.4 sec in total
769 ms
7.4 sec
284 ms
Click here to check amazing Vrm content. Otherwise, check out these important facts you probably never knew about vrm.co.za
G.P. Van Rhyn Minnaar attorneys, notaries and conveyancers Port Elizabeth and Uitenhage.
Visit vrm.co.zaWe analyzed Vrm.co.za page load time and found that the first response time was 769 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
vrm.co.za performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value10.4 s
0/100
25%
Value10.2 s
9/100
10%
Value880 ms
32/100
30%
Value0.095
91/100
15%
Value16.6 s
5/100
10%
769 ms
2719 ms
263 ms
500 ms
533 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 37% of them (32 requests) were addressed to the original Vrm.co.za, 16% (14 requests) were made to Maps.google.com and 11% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Vrm.co.za.
Page size can be reduced by 988.9 kB (22%)
4.5 MB
3.5 MB
In fact, the total size of Vrm.co.za main page is 4.5 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 137.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 137.3 kB or 77% of the original size.
Potential reduce by 5.1 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. Vrm images are well optimized though.
Potential reduce by 830.5 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 830.5 kB or 66% of the original size.
Potential reduce by 16.0 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. Vrm.co.za needs all CSS files to be minified and compressed as it can save up to 16.0 kB or 77% of the original size.
Number of requests can be reduced by 39 (53%)
73
34
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vrm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
vrm.co.za
769 ms
www.vrm.co.za
2719 ms
stylesheet.css
263 ms
fe_menu.css
500 ms
royalslider.css
533 ms
jquery.fancybox.min.css
11 ms
jquery.min.js
34 ms
rcn7evr.js
164 ms
in.js
8 ms
js
23 ms
jquery.tools.scroller.min.js
552 ms
jquery.royalslider.min.js
768 ms
jquery.easing-1.3.js
505 ms
addthis_widget.js
15 ms
superfish.js
510 ms
common.js
749 ms
jquery.fancybox.min.js
5 ms
d
239 ms
analytics.js
54 ms
background.jpg
297 ms
gplus-16.png
48 ms
gpvanrhynminnaar_logo.png
293 ms
gpvanrhynminnaar.png
293 ms
pattern.png
291 ms
header_1_178.jpg
720 ms
transparent.png
293 ms
header_1_146.jpg
2385 ms
header_1_124.jpg
1731 ms
header_1_143.jpg
1755 ms
header_1_155.jpg
1707 ms
header_1_174.jpg
1951 ms
header_1_175.jpg
1195 ms
header_1_131.jpg
2433 ms
header_1_176.jpg
2719 ms
header_1_133.jpg
2502 ms
header_1_139.jpg
2737 ms
gradient.png
2186 ms
feature_1_shutterstock_73381195.jpg
2429 ms
feature_3_dscf54592.jpg
2637 ms
feature_2_shutterstock_2876836.jpg
2690 ms
grey_bullet.png
2676 ms
white_bullet.png
2746 ms
feg7oTtwGw+LVwAA==
38 ms
3hkidoGOKulLVMyH8UN+jGnhMQ4009rgnpEnXRFNPypAZ5vpU0Ly5bC2CgjlyPe0ZzyZ1z9fKc1pr43lttVOgvRd00FEnnb3oJYWKdNFVN9310NOHXtFLb3301c+rXtPfAAMNMtjrhnhDsRJvGmqYtwz3thFGGuUdo8OW3T9qkvv33oO6E7cBsPi1cAA=
37 ms
3hkidoGOKulLVMyH8UN+jGnhMQ4009rgnpEnXRFNPypAZ5vpU0Ly5bC2CgjlyPe0ZzyZ1z9fKc1pr43lttVOgvRd00FEnnb3oJYWKdNFVN9310NOHXtFLb3301c+rXtPfAAMNMtjrhnhDsRJvGmqYtwz3thFGGuUdo8OW3T9qkvv33oO6E7cBsPi1cAA=
37 ms
3hkidoGOKulLVMyH8UN+jGnhMQ4009rgnpEnXRFNPypAZ5vpU0Ly5bC2CgjlyPe0ZzyZ1z9fKc1pr43lttVOgvRd00FEnnb3oJYWKdNFVN9310NOHXtFLb3301c+rXtPfAAMNMtjrhnhDsRJvGmqYtwz3thFGGuUdo8OW3T9qkvv33oO6E7cBsPi1cAA=
35 ms
collect
120 ms
secureAnonymousFramework
170 ms
apL7996DuhO3AbD4tXAA
35 ms
3hkidoGOKulLVMyH8UN+jGnhMQ4009rgnpEnXRFNPypAZ5vpU0Ly5bC2CgjlyPe0ZzyZ1z9fKc1pr43lttVOgvRd00FEnnb3oJYWKdNFVN9310NOHXtFLb3301c+rXtPfAAMNMtjrhnhDsRJvGmqYtwz3thFGGuUdo8OW3T9qkvv33oO6E7cBsPi1cAA=
34 ms
3hkidoGOKulLVMyH8UN+jGnhMQ4009rgnpEnXRFNPypAZ5vpU0Ly5bC2CgjlyPe0ZzyZ1z9fKc1pr43lttVOgvRd00FEnnb3oJYWKdNFVN9310NOHXtFLb3301c+rXtPfAAMNMtjrhnhDsRJvGmqYtwz3thFGGuUdo8OW3T9qkvv33oO6E7cBsPi1cAA=
33 ms
apL7996DuhO3AbD4tXAA
32 ms
p.gif
122 ms
sprite_connect_v14.png
37 ms
common.js
30 ms
map.js
31 ms
util.js
28 ms
marker.js
29 ms
300lo.json
84 ms
StaticMapService.GetMapImage
101 ms
sh.8e5f85691f9aaa082472a194.html
77 ms
onion.js
46 ms
openhand_8_8.cur
37 ms
ViewportInfoService.GetViewportInfo
61 ms
stats.js
16 ms
controls.js
12 ms
infowindow.js
42 ms
layers.e5ea973510bf60b3db41.js
37 ms
transparent.png
25 ms
css
86 ms
spotlight-poi.png
78 ms
google4.png
39 ms
mapcnt6.png
40 ms
sv5.png
40 ms
vt
61 ms
vt
44 ms
vt
61 ms
vt
61 ms
tmapctrl.png
13 ms
cb_scout5.png
15 ms
tmapctrl4.png
12 ms
imgs8.png
16 ms
vt
39 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
5 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
9 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
23 ms
vrm.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
button, link, and menuitem elements do not have accessible names.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
vrm.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
vrm.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vrm.co.za can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Vrm.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.
vrm.co.za
Open Graph description is not detected on the main page of Vrm. 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: