10.4 sec in total
1.3 sec
8.3 sec
916 ms
Welcome to rocketpos.co.nz homepage info - get ready to check Rocket POS best content right away, or after learning these important things about rocketpos.co.nz
As expert POS system providers, we bring point-of-sale management solutions to thousands of small & large businesses across New Zealand. Contact us today!
Visit rocketpos.co.nzWe analyzed Rocketpos.co.nz page load time and found that the first response time was 1.3 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
rocketpos.co.nz performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value7.4 s
4/100
25%
Value9.8 s
10/100
10%
Value360 ms
72/100
30%
Value0.085
93/100
15%
Value10.8 s
22/100
10%
1258 ms
473 ms
701 ms
701 ms
705 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 64% of them (61 requests) were addressed to the original Rocketpos.co.nz, 21% (20 requests) were made to Fonts.gstatic.com and 10% (10 requests) were made to Lh3.googleusercontent.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Rocketpos.co.nz.
Page size can be reduced by 333.0 kB (25%)
1.3 MB
1.0 MB
In fact, the total size of Rocketpos.co.nz main page is 1.3 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. 60% of websites need less resources to load. Images take 678.7 kB which makes up the majority of the site volume.
Potential reduce by 319.6 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 319.6 kB or 85% of the original size.
Potential reduce by 9.6 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. Rocket POS images are well optimized though.
Potential reduce by 1.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.4 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. Rocketpos.co.nz has all CSS files already compressed.
Number of requests can be reduced by 53 (75%)
71
18
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rocket POS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
rocketpos.co.nz
1258 ms
style.min.css
473 ms
styles.css
701 ms
woocommerce-layout.css
701 ms
woocommerce.css
705 ms
header-footer-elementor.css
711 ms
elementor-icons.min.css
735 ms
frontend-lite.min.css
730 ms
swiper.min.css
933 ms
post-7.css
939 ms
frontend-lite.min.css
939 ms
global.css
956 ms
post-8.css
973 ms
fluent-forms-elementor-widget.css
975 ms
frontend.css
1170 ms
post-10.css
1173 ms
post-271.css
1174 ms
style.min.css
1190 ms
theme.min.css
1212 ms
css
33 ms
fontawesome.min.css
1218 ms
solid.min.css
1395 ms
regular.min.css
1406 ms
brands.min.css
1407 ms
jquery.min.js
1424 ms
jquery-migrate.min.js
1462 ms
jquery.blockUI.min.js
1561 ms
add-to-cart.min.js
1637 ms
js.cookie.min.js
1638 ms
woocommerce.min.js
1637 ms
widget-icon-box.min.css
1648 ms
widget-icon-list.min.css
1485 ms
trustindex-google-widget.css
1539 ms
index.js
1637 ms
index.js
1641 ms
hello-frontend.min.js
1642 ms
smush-lazy-load.min.js
1660 ms
loader.js
23 ms
frontend.js
1722 ms
dwf.js
1494 ms
forms.js
1415 ms
webpack-pro.runtime.min.js
1411 ms
webpack.runtime.min.js
1399 ms
frontend-modules.min.js
1419 ms
wp-polyfill-inert.min.js
1469 ms
regenerator-runtime.min.js
1473 ms
wp-polyfill.min.js
1413 ms
hooks.min.js
1406 ms
i18n.min.js
1400 ms
frontend.min.js
1409 ms
waypoints.min.js
1465 ms
core.min.js
1471 ms
frontend.min.js
1395 ms
elements-handlers.min.js
1404 ms
jquery.sticky.min.js
1401 ms
Group-12569.png
59 ms
AD_cMMTkUiaY5DquFXwnduvr03iVfXGJf1J6Fm7NiTJADyQSNbGe=s120-c-rp-mo-br100
277 ms
AAcHTtd90CrfG7trFWXqVO0nAgcpL1mVjTDc8Y7-uYS9-gmA=s120-c-rp-mo-br100
293 ms
AAcHTterdg0oIhO4XePgjyLczrYMtodITVG6KkVJYjvTFafZ=s120-c-rp-mo-br100
356 ms
AAcHTtfeV_-Th1tQuuXuKuDQG5_6LVU7-9LDo_mqsgu4Bbku=s120-c-rp-mo-br100
387 ms
AD_cMMQXoqTnH_gh4V8XALdk6EzltZTsZ_yZZnyKJG5PeDZOPp0=s120-c-rp-mo-br100
426 ms
AAcHTtdEQ2Or9VYo6p4gE2kaQedpJXOLzGla_ddoREQZpXc=s120-c-rp-mo-br100
487 ms
AD_cMMQCswjoV8XmEjJIti4XveU6Mgvg9cSC6H4O-kaU3ybuJtx3=s120-c-rp-mo-br100
394 ms
AD_cMMRrvDRf8nkKav3pvmp1Y7ygQ6H_Hbs0MkCmohtJIKeDT1I=s120-c-rp-mo-br100
440 ms
AAcHTtc2uAG7DdwCN0QbxPe5TplbqegL5SMyNHekJQFJPvOr=s120-c-rp-mo-br100
424 ms
AD_cMMSskLed6AbCpmo41lxAJjVJJrWv6IRK76klgzx6wPlwYfY=s120-c-rp-mo-br100
531 ms
Group-12351.svg
1092 ms
banner-home.jpg
1885 ms
as-3.png
3795 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
32 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
43 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
44 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
43 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
45 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
45 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
45 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
45 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
46 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
46 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
47 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
48 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
47 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
47 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
48 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf
49 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv58a-xw.ttf
49 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xw.ttf
61 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf
62 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xw.ttf
62 ms
fa-solid-900.woff
1455 ms
fa-regular-400.woff
1239 ms
icon.svg
27 ms
f.svg
22 ms
fa-brands-400.woff
1486 ms
main-logo-300x108.png
938 ms
woocommerce-smallscreen.css
241 ms
rocketpos.co.nz 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
rocketpos.co.nz 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
rocketpos.co.nz 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
Image elements do not have [alt] attributes
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 Rocketpos.co.nz 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 Rocketpos.co.nz 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.
rocketpos.co.nz
Open Graph data is detected on the main page of Rocket POS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: