6.2 sec in total
12 ms
5.7 sec
509 ms
Click here to check amazing Qcard content for New Zealand. Otherwise, check out these important facts you probably never knew about qcard.co.nz
Our Q products are your perfect shopping partners for purchases big or small, combining the benefits of a credit card with a range of interest free deals.
Visit qcard.co.nzWe analyzed Qcard.co.nz page load time and found that the first response time was 12 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
qcard.co.nz performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value16.8 s
0/100
25%
Value9.6 s
11/100
10%
Value1,330 ms
17/100
30%
Value0.832
4/100
15%
Value15.3 s
7/100
10%
12 ms
147 ms
279 ms
288 ms
299 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 66% of them (68 requests) were addressed to the original Qcard.co.nz, 27% (28 requests) were made to Cdn-nzcards.humm-group.com and 1% (1 request) were made to Bugherd.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Cdn-nzcards.humm-group.com.
Page size can be reduced by 170.2 kB (14%)
1.2 MB
1.0 MB
In fact, the total size of Qcard.co.nz main page is 1.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 598.7 kB which makes up the majority of the site volume.
Potential reduce by 167.1 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 167.1 kB or 84% of the original size.
Potential reduce by 0 B
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. Qcard images are well optimized though.
Potential reduce by 1.2 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 1.8 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. Qcard.co.nz has all CSS files already compressed.
Number of requests can be reduced by 78 (80%)
98
20
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qcard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
qcard.co.nz
12 ms
www.qcard.co.nz
147 ms
search-filter.min.css
279 ms
style.min.css
288 ms
theme.min.css
299 ms
header-footer.min.css
306 ms
custom-frontend.min.css
794 ms
post-6.css
1615 ms
elementor-icons.min.css
311 ms
swiper.min.css
326 ms
custom-pro-frontend.min.css
1748 ms
post-12.css
1730 ms
post-24.css
1566 ms
post-17.css
1879 ms
algolia-autocomplete.css
516 ms
style.css
548 ms
fontawesome.min.css
586 ms
solid.min.css
567 ms
brands.min.css
983 ms
jquery.min.js
597 ms
jquery-migrate.min.js
802 ms
sidebarv2.js
44 ms
post-111.css
1538 ms
style.min.css
864 ms
dynamic-visibility.min.css
845 ms
post-1413.css
2340 ms
fire-modal-window.min.css
867 ms
acf-repeater.min.css
847 ms
datatables.min.css
1060 ms
accordion.css
1084 ms
post-1710.css
2331 ms
post-1726.css
2332 ms
acf-relationship-old-version.min.css
906 ms
regular.min.css
1127 ms
dynamic-posts.min.css
1569 ms
dynamic-posts-skin-grid.min.css
1178 ms
dynamic-posts-skin-accordion.min.css
1264 ms
animations.min.css
1322 ms
hello-frontend.min.js
1572 ms
underscore.min.js
1386 ms
wp-util.min.js
1460 ms
algoliasearch-lite.umd.js
1530 ms
autocomplete.min.js
1605 ms
autocomplete-noconflict.js
1647 ms
jquery.smartmenus.min.js
1709 ms
velocity.min.js
1576 ms
fix-background-loop.min.js
1838 ms
settings.min.js
1850 ms
vedd3670a3b1c4e178fdfb0cc912d969e1713874337387
114 ms
fire-modal-window.min.js
1848 ms
embed.js
73 ms
visibility.min.js
1696 ms
imagesloaded.min.js
1688 ms
masonry.min.js
1771 ms
jquery.masonry.min.js
1827 ms
wow.min.js
1818 ms
acf-repeater.min.js
1797 ms
datatables.min.js
1822 ms
accordion.min.js
1632 ms
dynamic-posts-base.min.js
1735 ms
dynamic-posts-skin-grid.min.js
1849 ms
infinite-scroll.pkgd.min.js
1842 ms
isotope.pkgd.min.js
1635 ms
jquery.matchHeight-min.js
2027 ms
dynamic-posts-skin-accordion.min.js
1713 ms
webpack-pro.runtime.min.js
1726 ms
webpack.runtime.min.js
2218 ms
frontend-modules.min.js
1892 ms
wp-polyfill-inert.min.js
1691 ms
regenerator-runtime.min.js
1779 ms
wp-polyfill.min.js
1565 ms
hooks.min.js
1780 ms
i18n.min.js
1550 ms
frontend.min.js
1737 ms
waypoints.min.js
1757 ms
core.min.js
1721 ms
frontend.min.js
1452 ms
elements-handlers.min.js
1402 ms
jquery.sticky.min.js
1608 ms
gtm.js
178 ms
hotjar-3074082.js
210 ms
qmastercard-and-qcard-cards-pqrxq8phyk1lq2t1zgwfpwe9pwtsmkyxrdfbcsmhnk.png
803 ms
q-card-card.png
716 ms
q-mastercard-card.png
824 ms
QMC-QCC-Main-Logo.svg
537 ms
search.svg
1462 ms
q-mastercard-credit-card.png
1525 ms
Qcard.png
1241 ms
1.1_QMC_April-24_AQ_Rev_Internal_Web_HP_Banner_855-x-451.jpg
1756 ms
Michael-Hill-New-Image-1.jpg
1612 ms
MH-Logo-New.png
1664 ms
Farmers-12-Months-LTF-image.jpg
2047 ms
Farmers_logo.png
2514 ms
Flight-centre-01-image.jpg
2445 ms
Flight-Centre-logo.png
2369 ms
MicrosoftTeams-image-37.jpg
2726 ms
Smiths_City_Charcoal-Logo_Qdeals.png
2477 ms
QMC-QCC-Cards-Lockup-1.png
2854 ms
d4023_QMC_HP_Love-noCTA-v3-1.png
3098 ms
fa-solid-900.woff
1138 ms
fa-brands-400.woff
1405 ms
modules.404c8789d11e259a4872.js
28 ms
61 ms
qcard.co.nz accessibility score
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
ARIA IDs are not unique
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
qcard.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
qcard.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
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 Qcard.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 Qcard.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.
qcard.co.nz
Open Graph data is detected on the main page of Qcard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: