Tools & Wizards About Us
1day.co.nz screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

1day.co.nz

Marketplace Stores | Marketplace | The Warehouse

Page Load Speed

7.2 sec in total

First Response

467 ms

Resources Loaded

6.6 sec

Page Rendered

161 ms

1day.co.nz screenshot

About Website

Visit 1day.co.nz now to see the best up-to-date 1 Day content and also check out these interesting facts you probably never knew about 1day.co.nz

At The Warehouse you can find all your favorite stores, brands and products in one place, with savings at the click of a button. Shop now!

Visit 1day.co.nz

Key Findings

We analyzed 1day.co.nz page load time and found that the first response time was 467 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

1day.co.nz performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value28.2 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value4,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.119

85/100

15%

TTI (Time to Interactive)

Value29.9 s

0/100

10%

Network Requests Diagram

1-day.co.nz

467 ms

www.1-day.co.nz

464 ms

www.1-day.co.nz

1101 ms

new_general.css

764 ms

jquery.min.js

32 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 1day.co.nz, 10% (7 requests) were made to Server.iad.liveperson.net and 6% (4 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source 1-day.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 356.3 kB (47%)

Content Size

765.9 kB

After Optimization

409.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1day.co.nz main page is 765.9 kB. 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. Javascripts take 349.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 40.6 kB

  • Original 53.1 kB
  • After minification 44.9 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 8.2 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 40.6 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 10.6 kB

  • Original 272.6 kB
  • After minification 262.0 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. 1 Day images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 231.0 kB

  • Original 349.6 kB
  • After minification 314.7 kB
  • After compression 118.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 231.0 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 74.2 kB

  • Original 90.6 kB
  • After minification 88.7 kB
  • After compression 16.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. 1day.co.nz needs all CSS files to be minified and compressed as it can save up to 74.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (61%)

Requests Now

64

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1 Day. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

1-day.co.nz

1-day.co.nz

467 ms

www.1-day.co.nz

www.1-day.co.nz

464 ms

www.1-day.co.nz

www.1-day.co.nz

1101 ms

new_general.css

new_general.css

764 ms

jquery.min.js

jquery.min.js

32 ms

cycle2.js

cycle2.js

785 ms

scratch.min.js

scratch.min.js

788 ms

google_service.js

google_service.js

43 ms

dumpymcfly.min.js

dumpymcfly.min.js

952 ms

2016-15-02-kit-out-your-flat.css

2016-15-02-kit-out-your-flat.css

964 ms

all.js

all.js

29 ms

conversion.js

conversion.js

26 ms

thickbox.js

thickbox.js

687 ms

main.js

main.js

685 ms

jquery.colorbox.js

jquery.colorbox.js

697 ms

dwr_ajax.js

dwr_ajax.js

776 ms

hello-visitor-min.js

hello-visitor-min.js

854 ms

css

css

64 ms

google_ads.js

google_ads.js

38 ms

css

css

14 ms

bg-tiled-2016-ronald.png

bg-tiled-2016-ronald.png

2519 ms

100encore200316_1day-page.jpg

100encore200316_1day-page.jpg

2519 ms

fitbitcharge200316_large.jpg

fitbitcharge200316_large.jpg

2517 ms

merino200316_large.jpg

merino200316_large.jpg

2517 ms

sports200316_large.jpg

sports200316_large.jpg

2517 ms

gtm.js

gtm.js

59 ms

1-day-sprite.png

1-day-sprite.png

357 ms

125 ms

facebook-icon-2015-small.png

facebook-icon-2015-small.png

2473 ms

xd_arbiter.php

xd_arbiter.php

51 ms

ads

ads

45 ms

analytics.js

analytics.js

32 ms

ads

ads

33 ms

collect

collect

4 ms

collect

collect

80 ms

ads

ads

193 ms

osd.js

osd.js

24 ms

m_js_controller.js

m_js_controller.js

2168 ms

abg.js

abg.js

2187 ms

footer-share-sprite.png

footer-share-sprite.png

2355 ms

footer-payment-types.png

footer-payment-types.png

2546 ms

sidetab-sprite+apparel.png

sidetab-sprite+apparel.png

2545 ms

actioncamera200316.jpg

actioncamera200316.jpg

2540 ms

wiltshire200316.jpg

wiltshire200316.jpg

2540 ms

healthsupplements200316.jpg

healthsupplements200316.jpg

2540 ms

100encore200316_tile.jpg

100encore200316_tile.jpg

2732 ms

2196 ms

fbevents.js

fbevents.js

2156 ms

tag.js

tag.js

108 ms

loadingAnimation.gif

loadingAnimation.gif

576 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

63 ms

x_button_blue2.png

x_button_blue2.png

12 ms

sf_digital_readout_heavy_oblique-webfont.woff

sf_digital_readout_heavy_oblique-webfont.woff

729 ms

s

s

32 ms

54 ms

36 ms

80 ms

xd_arbiter.php

xd_arbiter.php

29 ms

.jsonp

.jsonp

126 ms

mTag.js

mTag.js

128 ms

74 ms

97 ms

47 ms

repoffline2.gif

repoffline2.gif

194 ms

reponline2.gif

reponline2.gif

194 ms

36 ms

25 ms

26 ms

Accessibility Review

1day.co.nz accessibility score

69

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

1day.co.nz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

1day.co.nz SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1day.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 1day.co.nz main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

1day.co.nz

Open Graph description is not detected on the main page of 1 Day. 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: