Tools & Wizards About Us
readyflowers.co.nz screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

readyflowers.co.nz

Flowers From $35 | Flowers Online United States | US-USD-EN

Page Load Speed

63.3 sec in total

First Response

1.9 sec

Resources Loaded

40 sec

Page Rendered

21.4 sec

readyflowers.co.nz screenshot

About Website

Visit readyflowers.co.nz now to see the best up-to-date Ready Flowers content for New Zealand and also check out these interesting facts you probably never knew about readyflowers.co.nz

With over 1 Million happy flower customers we deliver flowers, same day across Australia. Established in 2005, we deliver online flowers to over 90 countries.

Visit readyflowers.co.nz

Key Findings

We analyzed Readyflowers.co.nz page load time and found that the first response time was 1.9 sec and then it took 61.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

readyflowers.co.nz performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value9,070 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.732

6/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

www.readyflowers.co.nz

1899 ms

311 ms

1739 ms

ga.js

6654 ms

jquery.min.js

8276 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Readyflowers.co.nz, 44% (42 requests) were made to Static.zflowers.com and 11% (11 requests) were made to Static1.zflowers.com. The less responsive or slowest element that took the longest time to load (14.2 sec) relates to the external source Static.zflowers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (63%)

Content Size

2.2 MB

After Optimization

810.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Readyflowers.co.nz main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 181.1 kB

  • Original 224.4 kB
  • After minification 221.9 kB
  • After compression 43.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 181.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 503 B

  • Original 336.6 kB
  • After minification 336.1 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. Ready Flowers images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 895.8 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 409.9 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 895.8 kB or 69% of the original size.

CSS Optimization

-93%

Potential reduce by 287.2 kB

  • Original 307.9 kB
  • After minification 123.4 kB
  • After compression 20.6 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. Readyflowers.co.nz needs all CSS files to be minified and compressed as it can save up to 287.2 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (55%)

Requests Now

87

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.readyflowers.co.nz

www.readyflowers.co.nz

1899 ms

311 ms

1739 ms

ga.js

ga.js

6654 ms

jquery.min.js

jquery.min.js

8276 ms

zbootstrap-1.1.5.min.js

zbootstrap-1.1.5.min.js

8262 ms

axd-1.0.2.min.js

axd-1.0.2.min.js

12888 ms

pnotify.custom.min.js

pnotify.custom.min.js

9596 ms

notices-1.0.8.js

notices-1.0.8.js

8250 ms

zf-digitalclock-1.1.4.js

zf-digitalclock-1.1.4.js

9596 ms

load.sumome.com

load.sumome.com

14196 ms

bat.js

bat.js

12447 ms

axd-1.0.2.min.js

axd-1.0.2.min.js

9254 ms

logo222x123.png

logo222x123.png

9253 ms

RF0002.jpg

RF0002.jpg

8941 ms

RF0334.jpg

RF0334.jpg

11929 ms

platform.js

platform.js

11896 ms

getTrackingCode

getTrackingCode

13820 ms

RF0100.jpg

RF0100.jpg

12460 ms

RF0021.jpg

RF0021.jpg

12461 ms

delivery-area-popup-pin.png

delivery-area-popup-pin.png

13848 ms

home.png

home.png

8907 ms

cart.png

cart.png

10005 ms

language.png

language.png

10005 ms

currency.png

currency.png

8907 ms

country.png

country.png

11894 ms

search.png

search.png

12099 ms

BirthdayFlowers.png

BirthdayFlowers.png

12460 ms

BestValue.png

BestValue.png

12459 ms

SameDayNoDesc.png

SameDayNoDesc.png

12459 ms

Birthday.png

Birthday.png

12459 ms

Romance.png

Romance.png

13680 ms

New%20Baby.png

New%20Baby.png

13710 ms

Get%20Well.png

Get%20Well.png

14006 ms

Sympathy.png

Sympathy.png

13987 ms

Generic.png

Generic.png

14006 ms

Most%20Popular.png

Most%20Popular.png

14005 ms

Full%20Range.png

Full%20Range.png

14224 ms

MainHero.png

MainHero.png

14225 ms

zf-scrollsign.png

zf-scrollsign.png

14223 ms

1X1.gif

1X1.gif

14133 ms

logo222x123.png

logo222x123.png

14221 ms

mobile_ico-zf.png

mobile_ico-zf.png

12319 ms

RF0017.jpg

RF0017.jpg

14005 ms

RF0097.jpg

RF0097.jpg

14005 ms

gtm.js

gtm.js

11921 ms

fbevents.js

fbevents.js

11837 ms

__utm.gif

__utm.gif

3540 ms

__utm.gif

__utm.gif

5438 ms

prum.min.js

prum.min.js

6115 ms

collect

collect

7444 ms

chat-icon.png

chat-icon.png

4359 ms

icons.png

icons.png

5223 ms

testi.jpg

testi.jpg

5222 ms

star_active.png

star_active.png

4446 ms

social-icon.png

social-icon.png

2573 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

2685 ms

825720520899508

825720520899508

1592 ms

GetNotice

GetNotice

1225 ms

zf-timeleft-nextday-delivery-1.0.1v2.png

zf-timeleft-nextday-delivery-1.0.1v2.png

454 ms

NextDay.png

NextDay.png

1488 ms

954 ms

ga-audiences

ga-audiences

1412 ms

32 ms

flw_w.png

flw_w.png

1677 ms

bootstrap.min.css

bootstrap.min.css

1808 ms

zbootstrap-1.1.10.min.css

zbootstrap-1.1.10.min.css

2443 ms

pnotify.custom.min.css

pnotify.custom.min.css

3104 ms

4116 ms

en-GB.gif

en-GB.gif

2596 ms

ja-JP.png

ja-JP.png

1609 ms

fr-FR.png

fr-FR.png

2484 ms

it-IT.png

it-IT.png

2485 ms

pl-PL.gif

pl-PL.gif

2484 ms

zh-HK.png

zh-HK.png

1607 ms

ko-KR.png

ko-KR.png

2616 ms

de-DE.png

de-DE.png

2585 ms

es-ES.png

es-ES.png

2563 ms

pt-PT.png

pt-PT.png

2584 ms

jquery.signalR-2.2.0.min.js

jquery.signalR-2.2.0.min.js

2451 ms

mobile_ico-zf.png

mobile_ico-zf.png

4423 ms

social-icon-zf.png

social-icon-zf.png

1310 ms

chat-icon.png

chat-icon.png

1310 ms

icons.png

icons.png

1308 ms

testi.jpg

testi.jpg

1358 ms

star_active.png

star_active.png

1372 ms

default

default

1546 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

1390 ms

service.js

service.js

3334 ms

service.js

service.js

3301 ms

service.js

service.js

3301 ms

service.js

service.js

3365 ms

service.js

service.js

3364 ms

service.js

service.js

3299 ms

badge

badge

1743 ms

googlelogo_color_150x54dp.png

googlelogo_color_150x54dp.png

23 ms

Accessibility Review

readyflowers.co.nz accessibility score

71

Accessibility Issues

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.

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

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

readyflowers.co.nz best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

readyflowers.co.nz SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Readyflowers.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 Readyflowers.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.

Social Sharing Optimization

readyflowers.co.nz

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