7.4 sec in total
799 ms
6.3 sec
267 ms
Visit bigsave.co.nz now to see the best up-to-date Big Save content for New Zealand and also check out these interesting facts you probably never knew about bigsave.co.nz
Whatever your taste, style or budget, you will find the furniture to meet your needs at Big Save Furniture. Sofas, beds, dining, bedroom and more - browse online now for great deals.
Visit bigsave.co.nzWe analyzed Bigsave.co.nz page load time and found that the first response time was 799 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
bigsave.co.nz performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value13.2 s
0/100
25%
Value13.9 s
1/100
10%
Value2,740 ms
3/100
30%
Value1.693
0/100
15%
Value26.7 s
0/100
10%
799 ms
24 ms
383 ms
572 ms
387 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 74% of them (50 requests) were addressed to the original Bigsave.co.nz, 9% (6 requests) were made to Mrdtestlab.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Bigsave.co.nz.
Page size can be reduced by 565.3 kB (23%)
2.5 MB
1.9 MB
In fact, the total size of Bigsave.co.nz main page is 2.5 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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 30.3 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 30.3 kB or 78% of the original size.
Potential reduce by 80.9 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. Big Save images are well optimized though.
Potential reduce by 211.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 211.4 kB or 62% of the original size.
Potential reduce by 242.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. Bigsave.co.nz needs all CSS files to be minified and compressed as it can save up to 242.8 kB or 79% of the original size.
Number of requests can be reduced by 29 (48%)
60
31
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Big Save. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
bigsave.co.nz
799 ms
css
24 ms
wc_email_inquiry_style.css
383 ms
dashicons.min.css
572 ms
jquery-ui-dialog.min.css
387 ms
layerslider.css
388 ms
css
35 ms
styles.css
385 ms
magnific-popup.css
388 ms
style.css
762 ms
style.css
764 ms
style.css
775 ms
layout.css
766 ms
woocommerce.css
769 ms
basic.css
1012 ms
prettyPhoto.css
1217 ms
jY9BDoMgEEUvpBCaHqO7HsBMYGpGhEEYary9xcaFiyZdzsv7-X-MnpaKeetrciCY9VROclNG3VWg2Bn9gA3zcyb3MYqAkG3imBFjYet_GnOj5aDKZwSpGQI6AvUt-SsoGWIhIY6lW1NvOQpG0TXNDO6q2lqEwyVh9GT9sDIPSyXr34RrKwgwRnq1smOIOu8-caqpvb0D.js
1970 ms
bY1bDoMgEAAvJFB6kt7A8NjAKgIuS9Xbt6b95HdmktFqcet8lDLvHd36RjjU0lRzhJXbpNWyd6BL9OoNA93uTzYM9EVCy6fUcsM8PZTFoDC71D20O-WI5EU1xNfABshAJg3MbyErAfP1ioXLIIJsbAKRMES25fwA.js
1231 ms
wc_email_inquiry_ultimate.min.css
1234 ms
default.css
1248 ms
shortcodes.css
1419 ms
custom.css
1631 ms
css
40 ms
M9QvTUotyk3NK9XPKtbPyC9LLfLMK0nNKwEA.js
1663 ms
M9QvTUotyk3NK9XPKoaz9XIz83RM9JPzc4G8Et2i1IKcSrCYIVAsryQxuUQ3Lb8oV9dcPzMvOac0JbUYpDursDS1qFIPJANSDAA.js
1664 ms
M9RPzs8rSUwu0U3LL8rVNdfPzEvOKU1JLdbPKtYvTi7KLCgpBgA.js
1679 ms
M9Qvz89Pzs_NTS1KTtVPLC5OLSnWzyrWTyvKzytJzUvRT0xJ0S3J101OLCrRy83M0zHEoSGrsDS1qFI3KSc_Obs0E8rVA3NDPUE6AQ.js
2040 ms
M9Qvz89Pzs_NTS1KTtVPLC5OLSnWzyrWTyvKzytJzUtBltbLzczTMcShIauwNLWoUjc5Pz87MxXK04PwQPoA.js
2207 ms
cart-fragments.min.js
2243 ms
ga.js
35 ms
fbds.js
21 ms
bg-pat-alt.jpg
311 ms
logo.png
677 ms
menu-bg-small.png
450 ms
ico-search.png
453 ms
home_icon.png
455 ms
facebook.png
633 ms
pinterest.png
671 ms
7days.png
903 ms
EDLP-sliders5.jpg
1545 ms
EDLP-sliders31.jpg
2084 ms
EDLP-sliders2.jpg
2077 ms
EDLP-sliders4.jpg
2116 ms
EDLP-sliders.jpg
2647 ms
15-minute-finance-web-tile.png
1744 ms
facebook-side1.gif
2111 ms
footer-haveyouseenthis.gif
2689 ms
lily.png
3210 ms
LookBook.gif
2840 ms
menu-bg-lts.png
267 ms
sub-menu-bg-alt-50.jpg
203 ms
sale.gif
266 ms
d9fijO34zQajqQvl3YHRCYnF5uFdDttMLvmWuJdhhgs.ttf
57 ms
ki3SSN5HMOO0-IOLOj069H06qf9KHRHwsVx7iw5MXmY.ttf
98 ms
funkymuskrat-webfont.woff
2664 ms
119 ms
div-pink.png
244 ms
footer-bg.png
338 ms
sketchy-webfont.woff
3452 ms
__utm.gif
21 ms
sketch-me__free-version-webfont.woff
3155 ms
F-uvpIj1hF17IDyvQvI50Q.ttf
33 ms
MViwy4K6e56oHcyeMzjbCQ.ttf
36 ms
skin.css
2835 ms
chevron-background-blogturq-1024x1024.jpg
1386 ms
blank.gif
1961 ms
skin.png
382 ms
25 ms
bigsave.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
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
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.
bigsave.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
bigsave.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 Bigsave.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 Bigsave.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.
bigsave.co.nz
Open Graph description is not detected on the main page of Big Save. 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: