15.9 sec in total
1.9 sec
13.2 sec
804 ms
Welcome to oami.co.za homepage info - get ready to check OAMI best content for South Africa right away, or after learning these important things about oami.co.za
Home page of the Protea Metering Online Automated Metering Infrastructure
Visit oami.co.zaWe analyzed Oami.co.za page load time and found that the first response time was 1.9 sec and then it took 14 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
oami.co.za performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value6.4 s
9/100
25%
Value12.4 s
3/100
10%
Value290 ms
79/100
30%
Value0
100/100
15%
Value15.2 s
7/100
10%
1868 ms
2678 ms
2968 ms
1197 ms
1203 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 71% of them (77 requests) were addressed to the original Oami.co.za, 12% (13 requests) were made to Maps.googleapis.com and 6% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (9.5 sec) belongs to the original domain Oami.co.za.
Page size can be reduced by 360.4 kB (44%)
811.8 kB
451.3 kB
In fact, the total size of Oami.co.za main page is 811.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. 45% of websites need less resources to load. Images take 434.5 kB which makes up the majority of the site volume.
Potential reduce by 24.4 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 4.1 kB, which is 13% 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 24.4 kB or 77% of the original size.
Potential reduce by 45.0 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. OAMI images are well optimized though.
Potential reduce by 56.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 56.5 kB or 77% of the original size.
Potential reduce by 234.6 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. Oami.co.za needs all CSS files to be minified and compressed as it can save up to 234.6 kB or 86% of the original size.
Number of requests can be reduced by 41 (53%)
77
36
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OAMI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
oami.co.za
1868 ms
bootstrap.css
2678 ms
bootstrap-responsive.css
2968 ms
extension.css
1197 ms
typography.css
1203 ms
prettyPhoto.css
2372 ms
isotope.css
1245 ms
price-table.css
2646 ms
circle-hover.css
1521 ms
skill-graph.css
1563 ms
default.css
1815 ms
style.css
1865 ms
settings.css
2407 ms
captions.css
2159 ms
jquery_004.js
5252 ms
jquery_002.js
5776 ms
jquery_003.js
4644 ms
bootstrap.js
5972 ms
jquery.js
3841 ms
jquery_007.js
4331 ms
jquery_005.js
5311 ms
jquery_006.js
5619 ms
jquery_008.js
6721 ms
fake-element.js
6771 ms
form-validation.js
6815 ms
waypoints.js
7185 ms
scroll.js
7772 ms
script.js
9454 ms
raphael.js
8476 ms
skill-diagram.js
8478 ms
mob-logo.png
2364 ms
logo.png
2665 ms
transparent.png
2653 ms
img1.jpg
4678 ms
img03.jpg
2972 ms
f02.png
3218 ms
watermeter-icon.png
3624 ms
theworld.png
6103 ms
User-Clients.png
3881 ms
Factory-icon.png
3918 ms
f01.png
3911 ms
f03.png
4162 ms
property.png
4908 ms
utility.png
4203 ms
s01.png
4423 ms
s02.png
4465 ms
t04.png
4719 ms
embed
422 ms
19.jpg
4695 ms
20.jpg
5079 ms
21.jpg
5159 ms
glyphicons-halflings-white.png
4901 ms
nexa_bold-webfont.woff
4957 ms
arimo-regular-webfont.woff
5140 ms
cartogothicstd-bold-webfont.woff
5135 ms
arimo-bold-webfont.woff
5191 ms
js
242 ms
init_embed.js
274 ms
lanenar_-webfont.woff
4925 ms
oxygen-webfont.woff
4681 ms
common.js
131 ms
map.js
292 ms
google4.png
140 ms
overlay.js
203 ms
util.js
324 ms
onion.js
320 ms
search_impl.js
320 ms
StaticMapService.GetMapImage
314 ms
OpenSans-Regular-webfont.woff
4371 ms
stats.js
75 ms
openhand_8_8.cur
57 ms
ViewportInfoService.GetViewportInfo
61 ms
ViewportInfoService.GetViewportInfo
45 ms
transparent.png
179 ms
kh
383 ms
vt
238 ms
controls.js
72 ms
vt
273 ms
vt
273 ms
vt
273 ms
vt
271 ms
css
351 ms
entity11.png
175 ms
mapcnt6.png
140 ms
tmapctrl.png
201 ms
AuthenticationService.Authenticate
80 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
121 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
137 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
149 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
178 ms
loader.gif
840 ms
timer.png
957 ms
shadow2.png
999 ms
small_left.png
1038 ms
small_right.png
1049 ms
nexa_bold-webfont.ttf
746 ms
arimo-regular-webfont.ttf
684 ms
cartogothicstd-bold-webfont.ttf
672 ms
arimo-bold-webfont.ttf
720 ms
lanenar_-webfont.ttf
633 ms
oxygen-webfont.ttf
572 ms
OpenSans-Regular-webfont.ttf
646 ms
nexa_bold-webfont.svg
361 ms
arimo-regular-webfont.svg
320 ms
cartogothicstd-bold-webfont.svg
353 ms
arimo-bold-webfont.svg
266 ms
lanenar_-webfont.svg
266 ms
oxygen-webfont.svg
335 ms
OpenSans-Regular-webfont.svg
261 ms
oami.co.za accessibility score
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
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
oami.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
Browser errors were logged to the console
Page has valid source maps
oami.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oami.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 Oami.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.
oami.co.za
Open Graph description is not detected on the main page of OAMI. 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: