13.3 sec in total
322 ms
12.3 sec
710 ms
Click here to check amazing Kounta content for Australia. Otherwise, check out these important facts you probably never knew about kounta.com
Looking for Kounta POS? We're now a part of the Ligthspeed family. Discover our new features: delivery, free live reports & more!
Visit kounta.comWe analyzed Kounta.com page load time and found that the first response time was 322 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kounta.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value6.1 s
12/100
25%
Value8.5 s
17/100
10%
Value3,430 ms
2/100
30%
Value0.004
100/100
15%
Value21.3 s
1/100
10%
322 ms
2041 ms
59 ms
27 ms
617 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 45% of them (56 requests) were addressed to the original Kounta.com, 6% (8 requests) were made to Sumome-140a.kxcdn.com and 6% (7 requests) were made to Sumome.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Kounta.com.
Page size can be reduced by 1.9 MB (45%)
4.2 MB
2.3 MB
In fact, the total size of Kounta.com main page is 4.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.9 MB which makes up the majority of the site volume.
Potential reduce by 188.5 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 188.5 kB or 83% of the original size.
Potential reduce by 44.5 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. Kounta images are well optimized though.
Potential reduce by 853.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 853.3 kB or 70% of the original size.
Potential reduce by 809.5 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. Kounta.com needs all CSS files to be minified and compressed as it can save up to 809.5 kB or 92% of the original size.
Number of requests can be reduced by 58 (52%)
111
53
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kounta. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
kounta.com
322 ms
www.kounta.com
2041 ms
css
59 ms
font-awesome.min.css
27 ms
bootstrap.min.css
617 ms
604 ms
5376993265713152.js
191 ms
750 ms
load.sumome.com
625 ms
jquery.cookie.js
646 ms
utm.js
712 ms
233572140.js
566 ms
home.css
457 ms
flexslider.css
476 ms
jquery.flexslider-min.js
790 ms
1049 ms
init-js.php
1180 ms
wp-emoji-release.min.js
976 ms
993 ms
1131 ms
analytics.js
58 ms
gtm.js
169 ms
logo.png
496 ms
dot.png
487 ms
star.png
487 ms
header-bg.jpg
1210 ms
features-bg.jpg
959 ms
homefeature-cloud.png
495 ms
homefeature-devices.png
957 ms
imaage-applestore.png
976 ms
imaage-googleplay.png
979 ms
homefeature-online.png
978 ms
homefeature-features.png
1408 ms
homefeature-addons.png
1426 ms
homefeature-support.png
1430 ms
reference-bg.jpg
2517 ms
logos-community.png
1759 ms
logos-community-mobile.png
1999 ms
logos-community2.png
2167 ms
logos-community-mobile2.png
2032 ms
logos-community3.png
2217 ms
logos-community-mobile3.png
2387 ms
sitedesign-play.png
2443 ms
video-rubys.jpg
2931 ms
video-bruce.jpg
3199 ms
video-messina.jpg
3265 ms
video-mings.jpg
3419 ms
sitedesign-play2.png
2913 ms
image-gettingstarted-hardware2.jpg
3402 ms
image-gettingstarted-partners2.jpg
3817 ms
twitter.png
3387 ms
facebook.png
3670 ms
youtube.png
3743 ms
google.png
3848 ms
rss.png
3859 ms
collect
125 ms
fontawesome-webfont.woff
12 ms
community-panel01.jpg
4014 ms
community-panel02.jpg
4520 ms
community-panel03.jpg
4493 ms
count.js
180 ms
469 ms
collect
136 ms
roundtrip.js
97 ms
conversion_async.js
117 ms
oct.js
194 ms
fbevents.js
250 ms
bat.js
146 ms
ga-audiences
60 ms
BT5EORISXRAF5DV7JZ425C.js
117 ms
23 ms
adsct
172 ms
adsct
157 ms
55 ms
36 ms
tr
55 ms
out
33 ms
out
32 ms
out
45 ms
out
43 ms
out
44 ms
48 ms
sync
66 ms
u.php
60 ms
adsct
88 ms
pixel
74 ms
community-panel04.jpg
4086 ms
community-panel05.jpg
4105 ms
kangaroo.png
3848 ms
progress.gif
4010 ms
tap.php
10 ms
sd
4 ms
377928.gif
8 ms
in
3 ms
service.js
66 ms
service.js
53 ms
service.js
66 ms
service.js
100 ms
service.js
100 ms
sumome-scrollbox-popup.css
54 ms
sme-popup.css
57 ms
css
25 ms
sumome-share-client.css
16 ms
load
239 ms
load
418 ms
load
597 ms
status
778 ms
status
971 ms
sprite.png
3830 ms
background-06.jpg
5022 ms
186c9738a6c42e53dac79ae4ee12e616bc31a213
34 ms
jquery-ui.js
1651 ms
scroll
122 ms
intercom.c5a1eeb5.js
37 ms
ping
187 ms
echo.515e8809.js
26 ms
me.jpg
106 ms
icon-launcher-acquire.8a742481.png
18 ms
client-test
124 ms
client-test
97 ms
icon-preview-close.ec1a68fc.png
17 ms
dan_smile_%281%29.jpg
45 ms
Screen_Shot_2014-11-14_at_3.44.18_pm.png
77 ms
icon-close-white@1x.bac0a0d6.png
12 ms
kounta.com 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
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
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
kounta.com 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
Issues were logged in the Issues panel in Chrome Devtools
kounta.com SEO score
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 Kounta.com 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 Kounta.com 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.
kounta.com
Open Graph data is detected on the main page of Kounta. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: