10 sec in total
676 ms
8.8 sec
557 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 676 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
qcard.co.nz performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value19.8 s
0/100
25%
Value20.2 s
0/100
10%
Value330 ms
75/100
30%
Value0.141
78/100
15%
Value12.2 s
15/100
10%
676 ms
1691 ms
1186 ms
86 ms
791 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 76% of them (47 requests) were addressed to the original Qcard.co.nz, 6% (4 requests) were made to Cloud.webtype.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Qcard.co.nz.
Page size can be reduced by 465.6 kB (17%)
2.7 MB
2.2 MB
In fact, the total size of Qcard.co.nz main page is 2.7 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 48.8 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 48.8 kB or 87% of the original size.
Potential reduce by 36.3 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. Qcard images are well optimized though.
Potential reduce by 209.7 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 209.7 kB or 67% of the original size.
Potential reduce by 170.7 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 needs all CSS files to be minified and compressed as it can save up to 170.7 kB or 87% of the original size.
Number of requests can be reduced by 18 (35%)
52
34
The browser has sent 52 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 14 to 1 for JavaScripts and as a result speed up the page load time.
qcard.co.nz
676 ms
www.qcard.co.nz
1691 ms
styles.min.css
1186 ms
jquery.min.js
86 ms
modernizr.js
791 ms
30d34fa3-aa7c-4444-81f7-d4cc838e721b.css
121 ms
require.js
1205 ms
main.min.js
580 ms
analytics.js
118 ms
v.gif
189 ms
gtm.js
162 ms
logo-lg.png
1622 ms
lockup.jpg
397 ms
icon-dot-white.svg
193 ms
tile-corner.png
387 ms
768-mitre-10-bathroom.jpg
1312 ms
mitre-10-220-logo.jpg
577 ms
icon-dot-pink.svg
579 ms
walker-and-hall-220-logo.jpg
589 ms
768-walker.jpg
2148 ms
Firestone.jpg
1330 ms
firestone-220-logo.png
1141 ms
pet-doctors.jpg
1169 ms
Pet-Doctors-220-logo.jpg
1330 ms
bg-dots-pink.gif
1362 ms
Lumino-150-logo.jpg
1700 ms
Target-150-logo.jpg
1519 ms
PB-150-logo.png
1520 ms
House-of-Travel-150-logo1.jpg
1556 ms
Air-NZ-150-logo.jpg
1712 ms
JB-150-logo1.jpg
1712 ms
trade-me-150-logo.png
1749 ms
Pet-Doctors-150-logo1.jpg
2004 ms
Freedom-150-logo.jpg
2087 ms
Flight-Centre-150-logo.jpg
1901 ms
bg-dots-blue.gif
1901 ms
travel-review.png
3109 ms
footer-icon-appstore.png
2089 ms
footer-icon-androidstore.png
2090 ms
ac51eeb6-377c-41c2-88e9-c1ae9b71fb68
60 ms
8e30c93c-7b78-4444-91e4-5ae428d9d301
61 ms
icomoon.ttf
2346 ms
aa12c930-4318-4bf0-ab80-ea3f6c206cd7
87 ms
collect
13 ms
collect
59 ms
i.cid
397 ms
picturefill.min.js
2125 ms
blocks.js
2112 ms
components.js
1928 ms
pixel
35 ms
pixel
17 ms
i.match
413 ms
jquery.fitvids.js
191 ms
jquery.validate.js
199 ms
debounced.js
284 ms
collect
16 ms
flickity.pkgd.min.js
785 ms
js.cookie.js
191 ms
Travel-1600-1365x1365.jpg
1145 ms
noel-leeming-web-banner-1920.jpg
2951 ms
app.jpg
1434 ms
Kmart-1920.jpg
1769 ms
qcard.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
Links do not have a discernible name
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
qcard.co.nz 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
qcard.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 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 description is not detected on the main page of Qcard. 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: